When DB2 attempts to update dbm cfg version to current level, if
it fails to open database manager configuration file, the
previous dbm cfg version was output in db2diag.log, it
mistakenly output current level.
The value of ptr->dbm_cfg_version shown in below db2daig.log is
not previous dbm cfg version, but current level (v10.1 in
following example). DB2 should restore and output previous value
instead:
2015-01-20-07.01.00.526124+000 I110470A402 LEVEL: Error
PID : 29819206 TID : 1 PROC :
db2gcf
INSTANCE: db2edwp1 NODE : 089
HOSTNAME: sa73edwdsp12
EDUID : 1
FUNCTION: DB2 UDB, config/install, sqlf_fix_dbm_cfg, probe:2804
MESSAGE : SQL5005: sqloopen rc =
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF6584 : 870F 0016
....
2015-01-20-07.01.00.527647+000 I110873A492 LEVEL: Error
PID : 29819206 TID : 1 PROC :
db2gcf
INSTANCE: db2edwp1 NODE : 089
HOSTNAME: sa73edwdsp12
EDUID : 1
FUNCTION: DB2 UDB, config/install, sqlfGetDbmCfg, probe:110
RETCODE : ZRC=0xFFFFEC73=-5005
SQL5005C The operation failed because the database
manager failed to
access either the database manager configuration file
or the database
configuration file.
...........
2015-01-20-07.01.00.539434+000 I112618A424 LEVEL: Error
PID : 29819206 TID : 1 PROC :
db2gcf
INSTANCE: db2edwp1 NODE : 089
HOSTNAME: sa73edwdsp12
EDUID : 1
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging function), probe:50
MESSAGE : ptr->dbm_cfg_version
DATA #1 : Hexdump, 2 bytes
0x0FFFFFFFFFFF6BA4 : 2774
't |
