Severe messages indicating 'ContainerTagIsValid' appear in
db2diag.log during redirected restore when a target database
name is different than source database name.
These messages appear during set tablespace containers for SMS
tablespace.
Here are the sample messages
2012-08-01-11.11.45.543563+120 I11503A4052 LEVEL: Severe
PID : 14483602 TID : 2572 PROC : db2sysc
0
INSTANCE: db2inst2 NODE : 000 DB : SAMPLE
APPHDL : 0-1194 APPID:
*LOCAL.db2inst2.120801090939
AUTHID : DB2INST2
EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbContainerTagIsValid, probe:100
DATA #1 : String, 20 bytes
*pTag(CONTAINER_TAG)
DATA #2 : Hexdump, 512 bytes
0x000000011A4E2EA0 : 4442 3243 4F4E 5400 0000 0214 82A2 7E0A
DB2CONT.......~.
0x000000011A4E2EB0 : 0000 001B 0000 0000 0000 0001 0000 0001
................
0x000000011A4E2EC0 : 0000 0139 BB59 4442 5432 3454 2020 0064
...9.YTEST .d
0x000000011A4E2ED0 : 6232 696E 7374 3200 0000 0000 0000 0000
b2inst2.........
0x000000011A4E2EE0 : 0000 2F64 622F 7465 7374 3937 2F64 6270
../db/test97/dbp
0x000000011A4E2EF0 : 6174 682F 4442 5432 3454 2F64 6232 696E
ath/TEST/db2in
0x000000011A4E2F00 : 7374 322F 4E4F 4445 3030 3030 2F53 514C
st2/NODE0000/SQL
0x000000011A4E2F10 : 3030 3030 312F 0000 0000 0000 0000 0000
00001/..........
0x000000011A4E2F20 : 0000 0000 0000 0000 0000 0000 0000 0000
................
....
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000013394FA0 pdLog + 0xE0
[1] 0x0900000013617BC8 pdLog@glue42C + 0xD0
[2] 0x090000001396990C
sqlbContainerTagIsValid__FP13CONTAINER_TAGiPC9SQLP_LSN8T2P12SQLB
_GLOBALSbT6Ui + 0x54
[3] 0x090000001344C884
sqlbSMSScanTagFile__FUiiPC9SQLP_LSN8T1P16SQLB_POOLCONT_CBP12SQLO
_FHANDLEPUiPP13CONTAINER_TAGP12SQLB_GLOBALS + 0x20C
[4] 0x090000001344C0AC
sqlbSMSDoContainerOp__FiPC9SQLP_LSN8T1P16SQLB_POOLCONT_CB12SQLB_
CONT_OPUiP12SQLB_GLOBALSb + 0x1F4
[5] 0x090000001344B1CC
sqlbSMSFreePoolContainers__FP12SQLB_POOL_CBiT2UiP12SQLB_GLOBALS
+ 0x15C
[6] 0x090000001403B10C
sqlbSetPoolCont__FP12SQLB_GLOBALSUiUsiP20SQLB_TBSCONTQRY_DATAT2b
+ 0xDB4
[7] 0x090000001405DED4
sqlbstsc_route_in__FP12SQLE_DB2RA_TP8sqeAgent + 0xE8
[8] 0x090000001401FDF8 sqlesrvr__FP14db2UCinterface + 0xAC
[9] 0x0900000013373C40 sqleMappingFnServer__FP5sqldaP5sqlca +
0x24
2012-08-01-11.11.45.546704+120 I15556A3136 LEVEL: Severe
PID : 14483602 TID : 2572 PROC : db2sysc
0
INSTANCE: db2inst2 NODE : 000 DB : SAMPLE
APPHDL : 0-1194 APPID:
*LOCAL.db2inst2.120801090939
AUTHID : DB2INST2
EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbContainerTagIsValid, probe:200
DATA #1 : Codepath, 8 bytes
2:4:9:11:12:14:15:16
DATA #2 : String, 19 bytes
iTag(CONTAINER_TAG)
DATA #3 : Hexdump, 512 bytes
0x070000000DBEA540 : 4442 3243 4F4E 5400 0000 0214 82A2 7E0A
DB2CONT.......~.
0x070000000DBEA550 : 0000 001B 0000 0000 0000 0001 0000 0001
................
0x070000000DBEA560 : 0000 0000 0000 4442 5432 3454 3220 0064
......SAMPLE .d
0x070000000DBEA570 : 6232 696E 7374 3200 0000 0000 0000 0000
b2inst2.........
0x070000000DBEA580 : 0000 2F64 622F 7465 7374 3937 2F64 6270
../db/test97/dbp
0x070000000DBEA590 : 6174 682F 4442 5432 3454 322F 6462 3269
ath/SAMPLE/db2i
0x070000000DBEA5A0 : 6E73 7432 2F4E 4F44 4530 3030 302F 5351
nst2/NODE0000/SQ
0x070000000DBEA5B0 : 4C30 3030 3031 2F00 0000 0000 0000 0000
L00001/.........
....
2012-08-01-11.11.45.547215+120 I18693A478 LEVEL: Severe
PID : 14483602 TID : 2572 PROC : db2sysc
0
INSTANCE: db2inst2 NODE : 000 DB : SAMPLE
APPHDL : 0-1194 APPID:
*LOCAL.db2inst2.120801090939
AUTHID : DB2INST2
EDUID : 2572 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbContainerTagIsValid, probe:900
DATA #1 : String, 31 bytes
sqloHasSameVnode returned false
These severe messages appear due to discrepancy between expected
and actual database path in SQLTAG.NAM file located in the SMS
container path. These severe messages can be ignored as they do
not impact redirected restore. Indeed these severe messages are
misleading. |
