JR32131: SQL2025N WHEN STATISTICS PROFILE FEATURE IS ENABLED

DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• When statistics profile is enabled, you might see the following
  error intermittently:
  
  SQL2025 : An IO error occured "accessing a file used for
  collecting the
  explain snapshot information occured on" on media "".
  
  Please be aware that:
  
  Statistics profile generation is best suited to environments
  running large complex queries that apply many predicates, often
  having correlations in the data of the predicate columns, and
  joining and grouping over several tables. It is less suitable to
  environments with a primarily transactional workload.
  
  The fix is to ignore the error, let query continue and complete
  normally and have a warning psted into db2diag.log saying that
  that auto stats profile was ignored for this query.
  

Local fix

• Disable AUTO_STATS_PROF and AUTO_PROF_UPD.
  

Problem summary

• USERS AFFECTED: All using statistics profile
  
  PROBLEM DESCRIPTION:
  
  When statistics profile is enabled, you might see the following
  error intermittently:
  
  SQL2025 : An IO error occured "accessing a file used for
  collecting the
  explain snapshot information occured on" on media "".
  
  Please be aware that:
  
  Statistics profile generation is best suited to environments
  running large complex queries that apply many predicates, often
  having correlations in the data of the predicate columns, and
  joining and grouping over several tables. It is less suitable to
  environments with a primarily transactional workload.
  
  The fix is to ignore the error, let query continue and complete
  normally and have a warning psted into db2diag.log saying that
  that auto stats profile was ignored for this query.
  
  PROBLEM SUMMARY:
  
  see problem description.
  

Problem conclusion

• The complete fix for this problem first appears in DB2 UDB
  Version 9.1 FixPak 8.
  

Temporary fix

• Disable AUTO_STATS_PROF and AUTO_PROF_UPD.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR32132 IC63440

Fix information

• Fixed component name

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP

• R910 PSN

     UP

• R950 PSN

     UP