SQL2171N may be recorded incorrectly in db2diag.log on HADR
standby.
Some kind of operations on HADR Primary may record SQL2171N in
the db2diag.log on HADR Standby incorrectly.
An example of operations causing SQL2171N is dropping a table
after LOAD utility and its db2diag.log is as;
2013-03-06-17.37.27.620453+540 I262756A466 LEVEL: Warning
PID : 25297400 TID : 8973 PROC : db2sysc
0
INSTANCE: e97q7d NODE : 000 DB : T37525E
APPHDL : 0-306 APPID: *LOCAL.DB2.130306083527
EDUID : 8973 EDUNAME: db2agent (T37525E) 0
FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:553
DATA #1 : String, 59 bytes
Starting to restore a load copy.
COMMON .T4.20130306173656
2013-03-06-17.37.37.672306+540 I263223A432 LEVEL: Warning
PID : 25297400 TID : 8973 PROC : db2sysc
0
INSTANCE: e97q7d NODE : 000 DB : T37525E
APPHDL : 0-306 APPID: *LOCAL.DB2.130306083527
EDUID : 8973 EDUNAME: db2agent (T37525E) 0
FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:1136
MESSAGE : Load copy restore completed successfully.
2013-03-06-17.38.55.764963+540 I263656A528 LEVEL: Warning
PID : 25297400 TID : 8320 PROC : db2sysc
0
INSTANCE: e97q7d NODE : 000 DB : T37525E
APPHDL : 0-306 APPID: *LOCAL.DB2.130306083527
EDUID : 8320 EDUNAME: db2redom (T37525E) 0
FUNCTION: DB2 UDB, database utilities, sqluhUpdateSingle,
probe:657
MESSAGE : SQL2171N The update of the recovery history file
failed because the
specified object part does not exist in the file.
2013-03-06-17.38.55.765231+540 E264185A570 LEVEL: Warning
PID : 25297400 TID : 8320 PROC : db2sysc
0
INSTANCE: e97q7d NODE : 000 DB : T37525E
APPHDL : 0-306 APPID: *LOCAL.DB2.130306083527
EDUID : 8320 EDUNAME: db2redom (T37525E) 0
FUNCTION: DB2 UDB, recovery manager,
sqlpProcessDroppedTablePendingRec, probe:3
DATA #1 : <preformatted>
Dropped table history record missing. Tables dropped at or
after History File Index
4 are no longer recoverable through dropped table recovery. |
