IY97033: AUTOMATIC STATS PROFILING CAN FAIL TO EXECUTE IF THE DB DIR CONTAINS REMOTE ENTRIES OF THE SAME DB NAME

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• Automatic statistics profiling can fail to execute if the
  database directory contains remote entries of the same database
  name.
  
  For example,
  - INFOM11 is a local database with auto_stats_profile enabled
  - INFOM11 is also the database name of 8 other database
  directory entries
  dbname   alias     type
  INFOM11  TINFOM11  Remote   node:IFMUDB1T
  INFOM11  INFOM11T  Remote   node:INFUDB1T
  INFOM11  INFOMIT   Remote   node:IFMUDBIT
  INFOM11  INFOM11C  Remote   node:DB2CAP01
  INFOM11  INFOM11E  Remote   node:NODEE
  INFOM11  INFOM11   Indirect dbdir:/export/home/db2fap01
  INFOM11  INFOM11P  Remote   node:IFMUDBP
  INFOM11  INFOM11Q  Remote   node:IFMUDB1Q
  
  Symptom is db2diag.log entry with following funcion,probe,
  DATA#2, DATA#3:
     FUNCTION: DB2 UDB, Health Monitor,
  DumpFileHelper::getDatabasePath, probe:30
     DATA #2 : signed integer, 4 bytes
     1
     DATA #3 : unsigned integer, 1 bytes
     49
  

Local fix

• A workaround is to ensure that no other entry in the system
  database directory has the same database name, as shown in
  "Database name" from the "list database directory" command.
  This can occur if a remote database of the same name is
  cataloged as in this example:
  
  Database 1 entry:
   Database alias                       = REALDBA
   Database name                        = REALDB
   Node name                            = MACHINEA
   Database release level               = a.00
   Comment                              =
   Directory entry type                 = Remote
   Catalog database partition number    = -1
   Alternate server hostname            =
   Alternate server port number         =
  
  Database 2 entry:
   Database alias                       = REALDB
   Database name                        = REALDB
   Local database directory             = /notnfs/kwai2
   Database release level               = a.00
   Comment                              =
   Directory entry type                 = Indirect
   Catalog database partition number    = 0
   Alternate server hostname            =
   Alternate server port number         =
  
  Here:
  - REALDB (entry 2) is a local database where automatic
  statistics profiling is enabled
  - REALDB (entry 1) is also a remote database at node MACHINEA,
  catalogued locally as REALDBA
  
  To avoid the problem, one can:
  1. uncatalog the remote database
  2. if access to the remote database is required, then
     - at the remote node, catalog the database with an alias name
     - at the local node,
      - uncatalog the remote database with the same name
      - re-catalog the remote database using its alias name
  

Problem summary

• Automatic statistics profiling can fail to execute if the
  database directory contains remote entries of the same database
  name.
  

Problem conclusion

• To avoid the problem, one can:
  1. uncatalog the remote database
  2. if access to the remote database is required, then
     - at the remote node, catalog the database with an alias name
     - at the local node,
      - uncatalog the remote database with the same name
      - re-catalog the remote database using its alias name
  

Temporary fix

Comments

APAR Information

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

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

  IY97034 IY97035

Fix information

• Fixed component name

  DB2 UDB ESE SOL

• Fixed component ID

  5765F4102

Applicable component levels

• R820 PSY

     UP