DB2 Down
Dear Experts,
Yesterday morning we got our DB2 was shutdown itself due to database crash, after going through db2diag.log we found that the issue in on the TSP01 table (spooling file). However, after db2 was restarted the table seems to be OK, there is no issue related to the spooling job e.g. background job and printing. The table is able to be browsed either from SE16 or DB2 level.
We attach the diaglog during the problem:
2009-12-27-15.41.40.284454+420 I135105363A344 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_TCB:
DATA #1 : String, 31 bytes
Perm Table(63:9)=SAPR3 .TSP01
2009-12-27-15.41.40.284653+420 I135105708A164 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB_NAME.tcbSchemaName
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.284751+420 I135105873A163 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB_NAME.tcbTableName
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.284854+420 I135106037A145 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.284951+420 I135106183A148 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_COLUMN
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.285049+420 I135106332A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037475, itoken=2
2009-12-27-15.41.40.285258+420 I135106672A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.285357+420 I135106819A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.285456+420 I135106966A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037474, itoken=1
2009-12-27-15.41.40.285653+420 I135107306A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.285750+420 I135107453A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.285849+420 I135107600A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037473, itoken=0
2009-12-27-15.41.40.286047+420 I135107940A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286145+420 I135108087A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286242+420 I135108234A144 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLI_CB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286349+420 I135108379A157 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286447+420 I135108537A148 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLE_APP_CB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286560+420 I135108686A149 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLE_TRAN_CB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.286657+420 I135108836A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLP_LFPB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.304552+420 I135108983A145 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLP_ACB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.304669+420 I135109129A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLP_DBCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.304927+420 I135109276A158 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.306722+420 I135109435A158 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.467225+420 I135109594A366 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : locklist
DATA #1 : String, 55 bytes
Check /db2/P01/db2dump/l553191.000 for additional data.
2009-12-27-15.41.40.484287+420 I135109961A455 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:871
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program error"
DIA8575C An index manager programming error occurred.
2009-12-27-15.41.40.484590+420 I135110417A743 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:871
MESSAGE : P=63, O=9, C=0, RID=1FDCC107, numvals=47, rowLockiInfo:
DATA #1 : Hexdump, 64 bytes
0x0FFFFFFFFFFEEE98 : 0FFF FFFF FFFE EBE8 0000 0000 0000 0000 ................
0x0FFFFFFFFFFEEEA8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0FFFFFFFFFFEEEB8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0FFFFFFFFFFEEEC8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
2009-12-27-15.41.40.484800+420 I135111161A721 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:2546
DATA #1 : String, 15 bytes
BlockLockInfo:
DATA #2 : Hexdump, 64 bytes
0x0FFFFFFFFFFEEBA8 : 0780 0003 BBE2 1740 0900 1000 A0B5 1100 .......@........
0x0FFFFFFFFFFEEBB8 : 0000 0001 10AD 30A0 0FFF FFFF FFFE EC80 ......0.........
0x0FFFFFFFFFFEEBC8 : 4222 2228 0000 0000 0900 0000 01F4 AFC0 B""(............
0x0FFFFFFFFFFEEBD8 : 0000 0001 10F1 9D40 0000 0000 BAE4 C080 .......@........
2009-12-27-15.41.40.485026+420 I135111883A344 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_TCB:
DATA #1 : String, 31 bytes
Perm Table(63:9)=SAPR3 .TSP01
2009-12-27-15.41.40.485225+420 I135112228A164 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB_NAME.tcbSchemaName
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.485328+420 I135112393A163 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB_NAME.tcbTableName
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.485425+420 I135112557A145 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_TCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.485534+420 I135112703A148 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_COLUMN
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.485633+420 I135112852A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037475, itoken=2
2009-12-27-15.41.40.485830+420 I135113192A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.485928+420 I135113339A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486026+420 I135113486A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037474, itoken=1
2009-12-27-15.41.40.486224+420 I135113826A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486322+420 I135113973A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486420+420 I135114120A339 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : SQLD_IXCB:
DATA #1 : String, 26 bytes
rootPage=1037473, itoken=0
2009-12-27-15.41.40.486618+420 I135114460A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IXCB
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486716+420 I135114607A146 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_IDEF
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486823+420 I135114754A150 LEVEL: Severe
PID:184410 TID:1 NODE:000 Title: SQLD_DFM_WORK
Dump File:/db2/P01/db2dump/1844101.000
2009-12-27-15.41.40.486932+420 I135114905A455 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:871
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program error"
DIA8575C An index manager programming error occurred.
2009-12-27-15.41.40.487142+420 I135115361A325 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:871
2009-12-27-15.41.40.515601+420 I135115687A417 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:10
MESSAGE : DIA0505I Execution of a component signal handling function has begun.
2009-12-27-15.41.40.515864+420 I135116105A430 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:20
MESSAGE : DIA0506I Execution of a component signal handling function is
complete.
2009-12-27-15.41.40.516108+420 I135116536A414 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler, probe:50
MESSAGE : DIA0505I Execution of a component signal handling function has begun.
2009-12-27-15.41.40.521645+420 I135124016A2006 LEVEL: Severe
PID : 184410 TID : 1 PROC : db2agent (P01) 0
INSTANCE: db2p01 NODE : 000 DB : P01
APPHDL : 0-1623 APPID: GA020110.D359.010EF6232908
MESSAGE : section stmt
DATA #1 : Hexdump, 325 bytes
0x07800003BBBEEE40 : 494E 5345 5254 2049 4E54 4F20 2254 5350 INSERT INTO "TSP
0x07800003BBBEEE50 : 3031 2220 5641 4C55 4553 2820 3F20 2C20 01" VALUES( ? ,
0x07800003BBBEEE60 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEE70 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEE80 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEE90 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEEA0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEEB0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEEC0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEED0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEEE0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEEF0 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEF00 : 3F20 2C20 3F20 2C20 3F20 2C20 3F20 2C20 ? , ? , ? , ? ,
0x07800003BBBEEF10 : 3F20 2C20 3F20 2920 202D 2D20 4F50 544C ? , ? ) -- OPTL
0x07800003BBBEEF20 : 4556 454C 2820 3520 2920 2D2D 2051 5545 EVEL( 5 ) -- QUE
0x07800003BBBEEF30 : 5259 5F44 4547 5245 4528 2031 2029 202D RY_DEGREE( 1 ) -
0x07800003BBBEEF40 : 2D20 4C4F 4341 5449 4F4E 2820 5A53 5F43 - LOCATION( ZS_C
0x07800003BBBEEF50 : 5245 4154 455F 5155 4F54 4154 494F 4E5F REATE_QUOTATION_
0x07800003BBBEEF60 : 4232 4220 2C20 3130 3436 2029 202D 2D20 B2B , 1046 ) --
0x07800003BBBEEF70 : 5359 5354 454D 2820 5030 3120 2C20 5341 SYSTEM( P01 , SA
0x07800003BBBEEF80 : 5052 3320 29 PR3 )
1. We'd like to know the root cause so that we can avoid such thing in the future, please advise.
2. The system currently is running well, does it mean that the table is just fine? Since there is no issue and or error with the jobs related to the table.
3. We also have called IBM guy to check the system, however there's no issue with the hardware, there's no attention sign, warning or error related to hardware side.
Please advise.
Regards,
Rudi
Hello Rudi,
In order to determine root cause for the database crash you should open a SAP OSS message. This is beyond the scope of this forum as the trap files and other diagnostics should be provided and reviewed by SAP Support.
Regards,
Adam
Similar Messages
-
Can't Drop a table in DB2 UDB on Windows 2003 server Ent EDT
Previus step:
Database DB2 ibm for a sap BW production got error in log - cause: no space on disk.
system mark database as bad.
system connection with db was restored with sap and ibm support
I'm in disaster recovery situation,
we have rebuilded index and table that got problem in db2dart report.
Now Sap system go up, we have successfully dumped 29 of 30 tables with db2dart /ddel command, now there is only a table that got problem:
sapbw2.rsbatchdata
we can't drop this table.
We try with this step:
1) db2dart bw2 /ddel
(table id)1837 (tablespaceid)10 0 9000000
we obtain a SQL file
2) db2dart bw2 /mt
(table id)1837 (tablespaceid)10 (password that you provide)
3) db2 drop bw2 sapbw2.rsbatchdata after this command we got a crash database.
2008-05-29-16.33.59.148000+120 I5094483F478 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : section stmt
DATA #1 : Hexdump, 29 bytes
0x000000003806E1F4 : 6472 6F70 2074 6162 6C65 2073 6170 6277 drop table sapbw
0x000000003806E204 : 322E 5253 4241 5443 4844 4154 41 2.RSBATCHDATA
2008-05-29-16.33.59.148000+120 I5094963F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section stmt
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095124F174 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: informational text for dump
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095300F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: Unrelocation Needed
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095468F204 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: Section relocated; reltables in global cache inaccessible
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.148000+120 I5095674F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5095834F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5095995F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096155F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096316F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: shared dynamic ptr
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096483F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: shared dynamic size
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.163000+120 I5096651F169 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dynamic section header
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5096822F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: offset in section
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5096988F153 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: opcode
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097143F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: agg_mode
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097300F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: section1
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.179000+120 I5097457F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: End of dumped section
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.241000+120 I5097627F438 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
MESSAGE : Context info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for
additional data.
2008-05-29-16.33.59.273000+120 I5098067F452 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Private workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.33.59.288000+120 I5098521F451 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Shared workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.33.59.304000+120 I5098974F450 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
MESSAGE : Package Cache info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000
for additional data.
2008-05-29-16.33.59.335000+120 I5099426F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA ASCB ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099594F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099767F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5099940F169 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** SEND BUFFERS ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5100111F174 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** CONNECTION HANDLE ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.335000+120 I5100287F172 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** DRDA ATTRIBUTES ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.351000+120 I5100461F171 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: **** AS UCINTERFACE ****
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.351000+120 I5100634F468 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error detected"
DIA8501C A buffer pool logic error has occurred.
2008-05-29-16.33.59.351000+120 I5101104F331 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
2008-05-29-16.33.59.820000+120 I5101437F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.820000+120 I5101595F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5101753F400 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_AGENT_CB Pointer:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AB0 : 0001 E637 0000 0000 ...7....
2008-05-29-16.33.59.835000+120 I5102155F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5102317F398 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_TRAN_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AA0 : 8087 FD0F 0000 0000 ........
2008-05-29-16.33.59.835000+120 I5102717F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5102878F397 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_APP_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA4AA8 : 0083 FD0F 0000 0000 ........
2008-05-29-16.33.59.835000+120 I5103277F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.835000+120 I5103437F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN PERM CURSORS: >>
2008-05-29-16.33.59.851000+120 I5103787F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN PERM CURSORS: <<
2008-05-29-16.33.59.851000+120 I5104134F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN TEMP CURSORS: >>
2008-05-29-16.33.59.851000+120 I5104484F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN TEMP CURSORS: <<
2008-05-29-16.33.59.851000+120 I5104831F346 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: >>
2008-05-29-16.33.59.851000+120 I5105179F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
2008-05-29-16.33.59.851000+120 I5105545F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.851000+120 I5105702F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
2008-05-29-16.33.59.851000+120 I5106068F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106225F342 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: <<
2008-05-29-16.33.59.866000+120 I5106569F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLI_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106725F167 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5106894F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5107054F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.866000+120 I5107215F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.929000+120 I5107373F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.929000+120 I5107530F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.945000+120 I5107688F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.945000+120 I5107858F373 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : locklist
DATA #1 : String, 59 bytes
Check
t1srv5bw\db2dumpBW2\l57042.000 for additional data.
2008-05-29-16.33.59.960000+120 I5108233F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108394F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108548F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108708F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.976000+120 I5108872F412 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEA8 : 0800 ..
2008-05-29-16.33.59.976000+120 I5109286F425 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABECA : 4E55 4C4C 4944 2020 NULLID
2008-05-29-16.33.59.976000+120 I5109713F491 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbname =
DATA #1 : Hexdump, 18 bytes
0x00000000056ABEB8 : 4257 3220 2020 2020 2020 2020 2020 2020 BW2
0x00000000056ABEC8 : 2020
2008-05-29-16.33.59.976000+120 I5110206F491 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgname =
DATA #1 : Hexdump, 18 bytes
0x00000000056ABEDC : 5351 4C43 3245 3037 2020 2020 2020 2020 SQLC2E07
0x00000000056ABEEC : 2020
2008-05-29-16.33.59.976000+120 I5110699F416 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgcnstkn =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABEEE : 4141 4141 4163 4555 AAAAAcEU
2008-05-29-16.33.59.991000+120 I5111117F406 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgsn =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEF6 : CB00 ..
2008-05-29-16.33.59.991000+120 I5111525F496 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pStatementText =
DATA #1 : Hexdump, 29 bytes
0x00000000062D0CC0 : 6472 6F70 2074 6162 6C65 2073 6170 6277 drop table sapbw
0x00000000062D0CD0 : 322E 5253 4241 5443 4844 4154 41 2.RSBATCHDATA
2008-05-29-16.33.59.991000+120 I5112023F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS APPL CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112183F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED APPL CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112350F166 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS SP REGISTERS CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112518F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS TRAN CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.33.59.991000+120 I5112678F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED TRAN CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5112845F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS COORD CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113006F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS NESTED CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113168F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS INVOCATION CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113334F165 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS ACTIVE STMT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113501F164 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: NLSWA:DatabaseApp
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.007000+120 I5113667F153 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: nlsacb
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5113822F157 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: dbNLSAppCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5113981F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: UnicodeNLSAppCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.023000+120 I5114145F464 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
MESSAGE : Error -2045771763 when reading LSN 000006BDB601F7A1 from log file
S0000000.LOG tellMe 0 dpsAcbFlags 0 setSkipOutputBuf 0
2008-05-29-16.34.00.023000+120 I5114611F468 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
MESSAGE : NOTE: The log state was marked bad by another process, this message
is not an indication of an error with the logger process
2008-05-29-16.34.00.523000+120 I5115081F457 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.538000+120 I5115540F459 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptudo, probe:1010
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.538000+120 I5116001F455 LEVEL: Warning
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptudo, probe:4350
MESSAGE : LSN being undone:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA87A8 : 0000 06BD B601 F7A1 ........
2008-05-29-16.34.00.538000+120 I5116458F157 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_TENTRY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116617F166 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116785F155 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5116942F154 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.554000+120 I5117098F390 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlptud1, probe:1880
MESSAGE : Due to error during UNDO, database will be brought down.
2008-05-29-16.34.00.570000+120 I5117490F459 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, data protection, sqlpxrbk, probe:3040
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.570000+120 I5117951F155 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.570000+120 I5118108F154 LEVEL: Error
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.00.570000+120 I5118264F384 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : cr_error:
DATA #1 : Hexdump, 4 bytes
0x00000000056AF4C8 : 0100 0000 ....
2008-05-29-16.34.00.570000+120 I5118650F465 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrrbck_dps, probe:20
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.00.585000+120 I5119117F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 1
sqlerrmc: 2
sqlerrp : SQLRL281
sqlerrd : (1) 0x87020002 (2) 0x00000002 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.00.585000+120 I5119811F418 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, global services, sqlzerdm, probe:40
DATA #1 : Hexdump, 4 bytes
0x0000000005AA8B08 : 0D00 1086 ....
2008-05-29-16.34.01.070000+120 I5120231F461 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:40
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.01.070000+120 I5120694F474 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:88
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-05-29-16.34.01.070000+120 I5121170F435 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:190
DATA #1 : Hexdump, 4 bytes
0x0000000005AA8F6C : 0200 0287 ....
2008-05-29-16.34.01.070000+120 I5121607F383 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : UCstate:
DATA #1 : Hexdump, 4 bytes
0x00000000056AFA70 : 4200 0004 B...
2008-05-29-16.34.01.070000+120 I5121992F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -984 sqlerrml: 1
sqlerrmc: 2
sqlerrp : sqlrrbkd
sqlerrd : (1) 0x8610000D (2) 0xFFFFFC2C (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.070000+120 I5122686F508 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10
MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected. The
diagnostic data returned is (SRVDGN): "SQLERRP:sqlrrbkd
SQLCODE:-984".
2008-05-29-16.34.01.085000+120 I5123196F691 LEVEL: Error
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -984 sqlerrml: 1
sqlerrmc: 2
sqlerrp : sqlrrbkd
sqlerrd : (1) 0x8610000D (2) 0xFFFFFC2C (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.085000+120 I5123889F375 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
2008-05-29-16.34.01.085000+120 I5124266F692 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1034 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLRR09E
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFFE2 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
2008-05-29-16.34.01.085000+120 I5124960F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.085000+120 I5125114F385 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : CREATOR
DATA #1 : Hexdump, 8 bytes
0x0000000037E6D1AE : 4E55 4C4C 4944 2020 NULLID
2008-05-29-16.34.01.085000+120 I5125501F385 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : PACKAGE
DATA #1 : Hexdump, 8 bytes
0x0000000037E6D1CC : 5351 4C43 3245 3037 SQLC2E07
2008-05-29-16.34.01.101000+120 I5125888F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CREATOR
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126044F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: PACKAGE
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126200F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: REQUEST TYPE
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126361F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: APM COMMON INFO
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.101000+120 I5126525F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CONTEXT MCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5126685F161 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: CONTEXT MEM CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5126848F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: PACKAGE ENTRY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.116000+120 I5127010F438 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
MESSAGE : Context info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for
additional data.
2008-05-29-16.34.01.116000+120 I5127450F452 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Private workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.34.01.116000+120 I5127904F451 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
MESSAGE : Shared workspace info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
2008-05-29-16.34.01.132000+120 I5128357F450 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
MESSAGE : Package Cache info dumped! Check
t1srv5bw\db2dumpBW2\a71646016.000
for additional data.
2008-05-29-16.34.01.132000+120 I5128809F376 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
2008-05-29-16.34.01.132000+120 I5129187F331 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
2008-05-29-16.34.01.601000+120 I5129520F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.601000+120 I5129678F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.601000+120 I5129836F400 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_AGENT_CB Pointer:
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8970 : 0001 E637 0000 0000 ...7....
2008-05-29-16.34.01.601000+120 I5130238F160 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5130400F398 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_TRAN_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8960 : 8087 FD0F 0000 0000 ........
2008-05-29-16.34.01.616000+120 I5130800F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5130961F397 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_APP_CB Pointer
DATA #1 : Hexdump, 8 bytes
0x0000000005AA8968 : 0083 FD0F 0000 0000 ........
2008-05-29-16.34.01.616000+120 I5131360F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.616000+120 I5131520F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN PERM CURSORS: >>
2008-05-29-16.34.01.616000+120 I5131870F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN PERM CURSORS: <<
2008-05-29-16.34.01.632000+120 I5132217F348 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 21 bytes
OPEN TEMP CURSORS: >>
2008-05-29-16.34.01.632000+120 I5132567F345 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 22 bytes
OPEN TEMP CURSORS: <<
2008-05-29-16.34.01.632000+120 I5132914F346 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : >> Begin CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: >>
2008-05-29-16.34.01.632000+120 I5133262F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
2008-05-29-16.34.01.632000+120 I5133628F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.632000+120 I5133785F364 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : SQLD_CCB:
DATA #1 : String, 49 bytes
pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
2008-05-29-16.34.01.632000+120 I5134151F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134308F342 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : << End CURSOR dump:
DATA #1 : String, 19 bytes
CLOSED CURSORS: <<
2008-05-29-16.34.01.648000+120 I5134652F154 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLI_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134808F167 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5134977F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5135137F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.648000+120 I5135298F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135456F155 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135613F156 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.710000+120 I5135771F168 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.726000+120 I5135941F373 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : locklist
DATA #1 : String, 59 bytes
Check
t1srv5bw\db2dumpBW2\l79922.000 for additional data.
2008-05-29-16.34.01.741000+120 I5136316F159 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.741000+120 I5136477F152 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: SQLCA
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136631F158 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136791F162 LEVEL: Severe
PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
Dump File:
t1srv5bw\db2dumpBW2\71646016.000
2008-05-29-16.34.01.757000+120 I5136955F412 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
DATA #1 : Hexdump, 2 bytes
0x00000000056ABEA8 : 0800 ..
2008-05-29-16.34.01.757000+120 I5137369F425 LEVEL: Severe
PID : 7164 TID : 6016 PROC : db2syscs.exe
INSTANCE: DB2BW2 NODE : 000 DB : BW2
APPHDL : 0-11 APPID: *LOCAL.DB2BW2.080529143349
MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
DATA #1 : Hexdump, 8 bytes
0x00000000056ABECA : 4E55 4C4C 4944 2020 NULLIDI can't use db2drop because this command crash my db with this table.
So I must take another way.
============================================================
About DB2 Administration Tools Environment
============================================================
DB2 administration tools level:
Product identifier SQL08025
Level identifier 03060106
Level DB2 v8.1.12.99
Build level s060429
PTF WR21370
============================================================
Java development kit (JDK):
Level IBM Corporation 1.4.2
============================================================ -
Dashboard link in the dashboard drop down
Hi,
I had a dashboard called Demo. I need that Demo to be in Dashboard drop down list which will be in the bi page top right corner beside HOME and CATALOG.
Thanks & Regards,
Karthik RHi Karthik,
R u Looking for this feature: If a User has 2-3 Dashboards in obiee and want to display the same in drop down menu items.
Example: Subject Area: HR , Dashboard1: HR DB1, Dashboard2: HR DB2
But, You Want to show like this: HR Dashboards (Drop Downs - HR DB1, HR DB2)
This Feature is controlled by parameter in Instance config file.
<DashboardMaxBeforeMenu>2</DashboardMaxBeforeMenu>
The above code groups all the Dashboards as Menu items which are formed from Common Subject Area.
Add the above code in instance config file.
After Adding the code - Restart the Services and check for the results. It worked for me, so it should work for u if I'm Right.
Thank you.
Award Points and Close the Post as Answered to help others with same issue :) -
OBIEE 11.1.1.6 Install fails on Domain Creation ; OS -AIX-64bit DB2 UDB9.7
Hi,
We have an exisiting OBIEE 10g installed on AIX-64 bit and DB2 9.7.
We brought it down and have started a fresh install of OBIEE 11.1.1.6 under a new Filesystem.
While Installing OBIEE 11.1.1.6, the Install errors at Configuration Step when it tries to create a Domain.
Here's the extract from the log :
[2012-03-16T04:51:26.478-04:00] [as] [ERROR] [] [oracle.as.provisioning] [tid: 28] [ecid: 0000JOQXUFlEoItqwcNa6G1FOibN00000T,0] [[
java.io.IOException: Couldn't resolve initial reference: NameService
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:349)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:258)
at oracle.as.provisioning.weblogic.AdminServer.connect(AdminServer.java:98)
at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:406)
at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:360)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:411)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
at oracle.as.install.bi.biconfig.standard.ConfigTemplateTask.doExecute(ConfigTemplateTask.java:34)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:371)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:64)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:160)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:736)
Caused by: javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:52)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:644)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:594)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:235)
at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
at javax.naming.InitialContext.internalInit(InitialContext.java:286)
at javax.naming.InitialContext.<init>(InitialContext.java:211)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
... 22 more
Caused by: org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:221)
at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4228)
at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:680)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3219)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:631)
... 32 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.rmi.transport.TCPTransport.getConnection(TCPTransport.java:157)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3751)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:179)
... 36 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:245)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:539)
at com.ibm.rmi.transport.TCPTransportConnection.createSocket(TCPTransportConnection.java:155)
at com.ibm.rmi.transport.TCPTransportConnection.createSocket(TCPTransportConnection.java:167)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 46 more
[2012-03-16T04:51:26.482-04:00] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 28] [ecid: 0000JOQXUFlEoItqwcNa6G1FOibN00000T,0] RETURN: _connectToAdminServer
[2012-03-16T04:51:26.484-04:00] [as] [ERROR] [] [oracle.as.provisioning] [tid: 28] [ecid: 0000JOQXUFlEoItqwcNa6G1FOibN00000T,0] [[
oracle.as.provisioning.engine.CfgWorkflowException
at oracle.as.provisioning.engine.Engine.processEventResponse(Engine.java:596)
at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:370)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:411)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
at oracle.as.install.bi.biconfig.standard.ConfigTemplateTask.doExecute(ConfigTemplateTask.java:34)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:371)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:64)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:160)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:736)
Caused by: oracle.as.provisioning.util.ConfigException:
Unable to connect to the AdminServer.
Cause:
An internal operation has failed:Couldn't resolve initial reference: NameService
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:439)
at oracle.as.provisioning.weblogic.ASDomain.connectToAdminServer(ASDomain.java:360)
... 16 more
Caused by: java.io.IOException: Couldn't resolve initial reference: NameService
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:349)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:258)
at oracle.as.provisioning.weblogic.AdminServer.connect(AdminServer.java:98)
at oracle.as.provisioning.weblogic.ASDomain._connectToAdminServer(ASDomain.java:406)
... 17 more
Caused by: javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:52)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:644)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:594)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:235)
at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
at javax.naming.InitialContext.internalInit(InitialContext.java:286)
at javax.naming.InitialContext.<init>(InitialContext.java:211)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
... 22 more
Caused by: org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:221)
at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4228)
at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:680)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3219)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:631)
... 32 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=cor089ya50,port=7001 vmcid: IBM minor code: E02 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.rmi.transport.TCPTransport.getConnection(TCPTransport.java:157)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3751)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:179)
... 36 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:245)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:539)
at com.ibm.rmi.transport.TCPTransportConnection.createSocket(TCPTransportConnection.java:155)
at com.ibm.rmi.transport.TCPTransportConnection.createSocket(TCPTransportConnection.java:167)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 46 more
]]Add this - cor089ya50 to your hosts file as well as IP and alias..so
cor089ya50.mydomain.com 192.168.2.3 cor089ya50 -
Error executing DB2 stored proc
Hi,
We are trying to execute a Stored Proc in Mainframe DB2. We've prepared a PreparedStatement. The problem the stored proc works fine in some cases, but in some it fails even thouhg the data passed is same. Even the whole JVM crashes and there is no log in error.log file.
Do you have any idea as to what might be the problem. We are using IBM WebSpehere5.0 and DB2v7.0
Regards,
RohitFor starters you should be using CallableStatement and not PreparedStatement.
And if the VM goes down and no errors are thrown anywhere than it's time to talk to the vendor or consult the docs because that is beyond the scope of help you could be given here. -
AIX6.1+HACMP+DB2 9.1+SAP ECC 6.0 High Availablity Installation
Dear All,
This is to request you that anyone having a sure shot Installation guide /Solution to Install SAP in High Availablity using following platform.
1. AIX 6.1
2. DB2 9.1
3. HACMP
4. ECC 6.0 SR 2
Note: Not Failover by scripting. High Availablity like Microsoft MCSC. Complete installation on Virtual host, IP and Shared File system/stirage.
Please....................................................
Regards
DharmendraInstalling SAP NW07 SR3 with DB2 on AIX HACMP
Scenario:-
DB will run on Node A
SAP CI will run on Node B
If node A fails DB will failover to Node B
If node B fails CI will failover to Node A
Shared SAP and DB filesystem are in SAN
Filesystems will failover accordingly
Requirements:-
SAP NW07 SR3 DVDs
AIX Node A
AIX Node B
HACMP supports node failures. We are not using HACMP to probe Application (SAP/DB) failures. i.e. if SAP or DB process crashes HACMP will not failover the resource groups.
/etc/hosts should have IPs of both nodes
Assumptions:-
PRD = PRD
Node A hostname: dbserver
Node B hostname: ciserver
Shared filesystems
These filesystems can be moved/ failed over (unmounted /mounted) from one node to another.
/usr/sap/PRD
/sapmnt/PRD
/db2/PRD
/db2/db2prd
/db2/PRD/sapdata1
/db2/PRD/sapdata2
/db2/PRD/sapdata3
/db2/PRD/sapdata4
/db2/PRD/log_dir
/db2/PRD/db2dump
Users and Groups will be created by SAPINST.
Please make a note of the UIDs as we have to use the same UIDs and GIDs on other node as well.
User Home directory:- For prdadm please use a home directory on shared disk
For e.g. /usr/sap/PRD/home/prdadm
Use Distributed Installation option in SAPINST
Installation steps:-
Node A:
Mount SAP filesystems
Mount DB2 filesystems
Check /etc/hosts that IP of both nodes are available
Ping both nodes and check the IP address
Check output of command ifconfig u2013a and confirm that both IPs are available
Start SAPINST with SAPINST_USE_HOSTNAME option.
For e.f. ./sapinst SAPINST_USE_HOSTNAME=dbserver
Step 1: Global host preparation (this should be easy to finish)
Step 2: Database instance installation
During this step note down UIDs and GIDs created by sapinst.
During this step please choose /usr/sap/PRD/home/prdadm as user home for prdadm user.
With SR3 DVDs db2 software will be installed in /db2/PRD/db2_software
Step 3: Install SAP Central Instance with SAPINST_USE_HOSTNAME=ciserver
Stop / Start SAP -> Login and confirm SAP instance is running fine.
Shutdown SAP and DB2
Add entries in .rhosts in home directory on user prdadm and db2prd
For example in /usr/sap/PRD/home/prdadm/.rhots
<IP Address of Node A> prdadm
<IP Address of Node B> prdadm
<all possible IP address> prdadm
Similarly for /db2/db2prd/.rhosts
<IP Address of Node A> db2prd
<IP Address of Node B> db2prd
<all possible IP address> db2prd
Node B:
Move SAP resources from Node A to B (i.e. SAP filesystems should become available on Node B)
DO NOT MODE DB RESOURCES, Let it stay on Node A alone.
Create /db2/PRD and /db2/db2prd directories (this should have some free space, 10 GB is good to go)
Start SAP installation under Distributed installation option
Step 1: Global host preparation
Temporarily change /etc/hosts and make the IP of dbserver same as ciserver.
dbserver line should be written above ciserver line
i.e. u2018ping dbserveru2019 and u2018ping ciserveru2019 should return same IP address on Node B (NOT NODE A)
Step 2: Database instance installation with option SAPINST_USE_HOSTNAME=dbserver
During this installation, make sure UIDs and GIDs are given same as in Node A.
You can confirm the UIDs from /etc/passwd and GID from /etc/group
Also, make sure you specify user home for prdadm as /usr/sap/PRD/home/prdadm
Once installation starts ABAP Load and one or two jobs are completed, please cancel the installation.
as db2prd
db2stop force
db2start
db2 connect to PRD
It should be successful. This confirms the DB2 is setup properly.
db2stop terminate
db2stop force
rm u2013r /db2/db2prd/*
rm u2013r /db2/PRD/sapdata1
rm u2013r /db2/PRD/sapdata2
rm u2013r /db2/PRD/sapdata3
rm u2013r /db2/PRD/sapdata4
rm u2013r /db2/PRD/log_dir
rm u2013r /db2/PRD/db2dump
Retain these directories so that you can mount the shared filesystems from Node A to Node B during failover.
Change and correct IP address in /etc/hosts of host dbserver, which we changed temporarily earlier.
Failover DB resources to Node B
Check if all DB2 filesystems are correctly available.
On Node A, check and double confirm that there are no files/directories under /db2 and its subdirectories. i.e. all filesystems have come to Node B.
In our case there was one filesystem /db2/PRD/db2prd which did not come to node B and we had to struggle a lot to find the same.
CONTINUED BELOW !!! -
SAP ECC 6.0 SR3 Cluster failover not working in AIX with DB2 UDB V9.1 FP6
Hi Gurus,
We have installed the SAP ECC 6.0 SR3 High Availability with DB2 UDB V9.1 FP6 in AIX cluster environment.
After installation we are doing the cluster fail test.
Node A
Application Server
Mount Points:
/sapmnt/<SID>
/usr/sap/<SID>
/usr/sap/trans
Node B
Database Server
Mount Points:
/db2//<SID>
The procedure followed to do the cluster failover:
We have down the cluster on Node A and all the resources of the Node A has been moved to Node B.
On Node B when we issued a command to start the SAP. It says u201Cno start profiles foundu201D
WE have down the cluster on Node B and moved the Resource from Node B to Node A . There the db2 User IDu2019s are not available. We have crated the user Idu2019s manually on Node A. however it did not work.
Please suggest the procedure to start the sap in cluster failover.
Best Regards
SijaHi Sija,
Can i have detailed scenario in your cluster configuration.
Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
Regards
Nick Loy -
Messages are in to be delivered state and slows down the message processing
Hello,
Messages are in to be delivered state and slows down the message processing.
this happenens in case of DB2 on some machine where the issue about high load on DB2 is caused by standard programming in SAP XI that executes a statement, where it uses the condition 'where 1<0' prio to the original SQL statement configured in the channel configuration,
Can you please help me out in solving this issue?
Thanks,
SooryaStatus: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords -
JDBC Sender Adapter for AS/400 DB2 (V5R1) Error
Hi,
I'm trying to create a connection to an DB2 database on an AS/400 (V5R1) server. First does anyone know what JDBC driver I should use for this... I am trying to use the DB2 Universal type 4 JDBC driver... But have a suspicion I should be using the Legacy type 2 which I'm trying to track down with the client. If anyone can give me details as to where exactly I can find this driver it would be very useful???
Currently my settings are as follows:
JDBC Driver: com.ibm.db2.jcc.DB2Driver
Connection: jdbc:db2://10.101.10.9:446/PROTST01
I have verified my user is correct etc... I get the following response in the RWB.
- 2006-01-13 10:54:40 GMT: Error: Accessing database connection 'jdbc:db2://10.101.10.9:446/PROTST01' failed: com.ibm.db2.jcc.b.SqlException: Connection authorization failure occurred. Reason: local security service non-retryable error.
Can this error be resolved or should I concentrate on installing the legacy type 2 driver and trying that???
Thanks in advance,
PeteHi Peter,
Check if these links are useful to you.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/34a1e590-0201-0010-2c82-9b6229cf4a41
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7bf6e190-0201-0010-83b7-cc557eb76abe
Hope this helps.
Regards,
Chandra -
Status metric for the OEM plugin for DB2 Databases
Hi,
I am doing some testing of the OEM system monitoring plug-in for an IBM DB2 Database. I am starting with some very basic alerts such as when an instance is down. However, it is not working as I would expect. When the instance is stopped using the command db2stop I would expect OEM to determine that the database is down. However, OEM reports a metric collection error and not the database being down.
Does anybody have any experience with DB2 databases and OEM?
Thanks,
ChristineBy creating Groups for specific targets and authoriizing access to these groups you can have users only "seeing" databases or certain databases and other users only being able to see certain Middleware components etc.
Check
Oracle® Enterprise Manager Administration
11g Release 1 (11.1.0.1)
http://download.oracle.com/docs/cd/E11857_01/em.111/e16790/group_management.htm#DAFFHDCJ
for this
Regards
Rob
http://oemgc.wordpress.com -
SQL*Loader -- loading EBCDIC-DB2[as400] packed decimals
Hi,
We have a flat file that we are trying to load into Oracle [tried version 8.1.7.0.0 and 9.2.0.1.0]. The flat file is a direct physical ftp from an AS400/DB2 and has a number of packed decimal fields and comes down in EBCDIC.
LOAD DATA
CHARACTERSET 'WE8EBCDIC500'
INTO TABLE asciitest
COL1 position (01:03) DECIMAL(4,0),
COL2 position (04:12) CHAR,
COL3 position (13:21) CHAR,
COL4 position (22:26) DECIMAL (9,2),
COL5 position (27:29) CHAR
with this script i am able to parse the CHAR data successfully however the packed decimal never work. They do get inserted into the fields but the when u select * from asciitest you get non-sensical results (ie characters instead of digits)
I've read some documents on SQL_Loader and it lead to me to beleive that it would be able to handle these numbers. Am I wrong? Is there anyway this can be done (with out 3rd party software)??Thanks damorgan but I have tried some of these before. The logic of converting the packed fields to zoned decimals and then further is not implemented using oracle which I am looking out for.
RR -
Unable to start DB2 9.5 in Solaris due to SQL1042C
Hi Seniors, Seeking assistance or clue on the below issue we facing recently. My QAS ERP is completely down for sometime due to this issue.
Error message when starting DB2:-
bash-3.00$ db2start
02/24/2011 17:21:57 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
bash-3.00$ db2 connect to QAS
SQL1042C An unexpected system error occurred. SQLSTATE=58004
bash-3.00$ db2 get db cfg
SQL1024N A database connection does not exist. SQLSTATE=08003
db2diag.log:- - Not full logs, need to deleted due to maximum length constrain.
2011-02-24-17.02.15.689455+480 I1A1233 LEVEL: Event
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2qas" uses "64" bits and DB2 code release "SQL09054"
with level identifier "06050107".
Informational tokens are "DB2 v9.5.0.4", "special_21925", "U825479_21925", Fix Pack "4".
DATA #2 : System Info, 1592 bytes
System: SunOS CSQT5ERP 5.10 Generic_142900-05 sun4v
CPU: total:128 online:128 Cores per socket:8 Threading degree per core:1
Physical Memory(MB): total:32544 free:28992
Virtual Memory(MB): total:177962 free:174410
Swap Memory(MB): total:145418 free:145418
Cur data size (bytes) = 0xFFFFFFFFFFFFFFFD
Cur stack size (bytes) = 0x0000000000800000
Cur core size (bytes) = 0x00000000FFFFFFFF
nofiles (descriptors) = 0x0000000000010000
2011-02-24-17.02.18.543076+480 I1700A429 LEVEL: Warning
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30
MESSAGE : Crash Recovery is needed.
2011-02-24-17.02.20.992821+480 I3036A492 LEVEL: Warning
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : Crash recovery started. LowtranLSN 00000174E561AA75 MinbuffLSN
00000174E561AA75
2011-02-24-17.02.20.993782+480 E3529A446 LEVEL: Warning
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410
MESSAGE : ADM1530E Crash recovery has been initiated.
2011-02-24-17.02.21.530927+480 E4469A486 LEVEL: Warning
PID : 23743 TID : 293 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 293 EDUNAME: db2redom (QAS) 0
FUNCTION: DB2 UDB, recovery manager, sqlpParallelRecovery, probe:880
DATA #1 : <preformatted>
Resetting max shredder memory to 100045238 from 468172800
2011-02-24-17.02.21.574941+480 I4956A625 LEVEL: Severe
PID : 23743 TID : 174 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 174 EDUNAME: db2redow (QAS) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbFixDataEMP, probe:830
MESSAGE : ZRC=0x84020019=-2080243687=SQLB_EMP_INDIRECT_NOT_FOUND
"EMP INDIRECT NOT FOUND"
DATA #1 : <preformatted>
emp->n_entries = 3
emAddr[lvl].slot = 5
emp->allocations[emAddr[lvl].slot] = 0
emp->unFmtChild = 0.
2011-02-24-17.02.21.577057+480 I6088A522 LEVEL: Error
PID : 23743 TID : 174 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 174 EDUNAME: db2redow (QAS) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMScheckObjAlloc, probe:820
DATA #1 : String, 89 bytes
Obj= State=x27 Parent={30;9032}, EM=51452, PP0=51454 Page=51453
2011-02-24-17.02.21.577899+480 I6611A969 LEVEL: Error
PID : 23743 TID : 174 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 174 EDUNAME: db2redow (QAS) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMScheckObjAlloc, probe:0
DATA #1 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 72 bytes
Obj: Parent={30;9032}
lifeLSN: 00002CC0415B
tid: 0 0 0
extentAnchor: 51452
initEmpPages: 0
poolPage0: 51454
poolflags: 3122
objectState: 27
lastSMP: 0
pageSize: 16384
extentSize: 2
bufferPoolID: 1
partialHash: 591921182
bufferPool: 0x0000010001ebb280
2011-02-24-17.02.21.579571+480 I8710A504 LEVEL: Error
PID : 23743 TID : 174 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 174 EDUNAME: db2redow (QAS) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbCheckAllocation, probe:800
MESSAGE : ZRC=0x84020019=-2080243687=SQLB_EMP_INDIRECT_NOT_FOUND
"EMP INDIRECT NOT FOUND"
2011-02-24-17.02.23.605521+480 I27354A552 LEVEL: Severe
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::RestartDatabase, probe:202
MESSAGE : If 'DATALINK: file server not registered' appears above and
DATALINKS=NO, set DATALINKS=YES and try RESTART again
2011-02-24-17.02.23.607663+480 I28352A477 LEVEL: Warning
PID : 23743 TID : 25 PROC : db2sysc 0
INSTANCE: db2qas NODE : 000 DB : QAS
APPHDL : 0-7 APPID: *LOCAL.db2qas.110224090215
AUTHID : DB2QAS
EDUID : 25 EDUNAME: db2agent (QAS) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbCleanupBeforeTerm, probe:826
DATA #1 : String, 41 bytes
Recovery failed, dirty pages not flushed.
Thanks in advance.
Devan
Edited by: Mdevan on Feb 24, 2011 10:41 AM Sorry the messages was not in a good format to read.
Edited by: Mdevan on Feb 24, 2011 10:43 AM
Edited by: Mdevan on Feb 24, 2011 10:44 AMHi Patrick,
Thanks for your reply.
We've done a restore, but its a file system restore of db2 of /db2/db2qas/sapdata1...6.
Hence after the restore, im able to db2start but not "db2 connect to QAS"
If you have any restoration experience, pls do share with me the necessary path of /db2 need to be restored? Pls find my server's file system structure below:-
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
/dev/vx/dsk/bootdg/rootvol
30G 19G 9.9G 67% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 167G 1.7M 167G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/platform/SUNW,T5240/lib/libc_psr/libc_psr_hwcap2.so.1
30G 19G 9.9G 67% /platform/sun4v/lib/libc_psr.so.1
/platform/SUNW,T5240/lib/sparcv9/libc_psr/libc_psr_hwcap2.so.1
30G 19G 9.9G 67% /platform/sun4v/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
swap 167G 48K 167G 1% /var/run
swap 167G 0K 167G 0% /dev/vx/dmp
swap 167G 0K 167G 0% /dev/vx/rdmp
/dev/dsk/c1t7d0s0 135G 77G 57G 58% /tempcd
/dev/vx/dsk/bootdg/opt
15G 6.2G 8.4G 43% /opt
/dev/vx/dsk/bootdg/tmp
6.4G 6.5M 6.3G 1% /temp
/dev/vx/dsk/bootdg/home
15G 351M 14G 3% /home
/dev/vx/dsk/sapnfsdg/nfsvol
98G 88G 9.2G 91% /erp_nfs
/dev/vx/dsk/erpqasdb2dg/IBMvol
19G 70M 18G 1% /opt/IBM
/dev/vx/dsk/erpqasdb2dg/db2qasvol
19G 1011M 17G 6% /db2/db2qas
/dev/vx/dsk/erpqassapdg/sapmntvol
29G 1.8G 26G 7% /sapmnt/QAS
/dev/vx/dsk/erpqasdb2dg/sapdatavol5
98G 43G 51G 47% /db2/QAS/sapdata5
/dev/vx/dsk/erpqassapdg/qasvol
29G 6.1G 22G 22% /usr/sap/QAS
/dev/vx/dsk/erpqasdb2dg/sapdatavol3
98G 43G 51G 47% /db2/QAS/sapdata3
/dev/vx/dsk/erpqasdb2dg/db2dumpvol
9.7G 953M 8.2G 11% /db2/QAS/db2dump
/dev/vx/dsk/erpqassapdg/transvol
68G 32G 34G 49% /usr/sap/trans
/dev/vx/dsk/erpqasdb2dg/saptemp1vol
9.7G 20M 9.1G 1% /db2/QAS/saptemp1
/dev/vx/dsk/erpqasdb2dg/sapdatavol2
98G 43G 51G 47% /db2/QAS/sapdata2
/dev/vx/dsk/erpqasdb2dg/sapdatavol1
98G 43G 51G 47% /db2/QAS/sapdata1
/dev/vx/dsk/erpqasdb2dg/sapdatavol6
98G 43G 51G 47% /db2/QAS/sapdata6
/dev/vx/dsk/erpqasdb2dg/sapdatavol4
98G 54G 41G 57% /db2/QAS/sapdata4
/dev/vx/dsk/erpqasdb2dg/logarchvol
293G 186G 100G 65% /db2/QAS/log_archive
/dev/vx/dsk/erpqasdb2dg/logdirvol
19G 745M 18G 4% /db2/QAS/log_dir
Pls share if you have any clue. -
Release Space at file system level in DB2
Dear Gurus,
We have ECC 6.0 system on AIX with DB2 9.1 . We want to release space at file system level , I have idea regarding Oracle that it can be done in 2 ways 1: Offline DB reorg 2 : Dtafile resize.I am new to DB2 so can you please let me know whether it is feasible with DB2 as well or not.
In case yes what steps we need to perform in db2 in order to release space
Regards
Kuldeep singhYou can reduce the size of your tablespaces down to their current high water mark with the ALTER TABLESPACE REDUCE command. Reducing the high water mark requires much more work and on DB2 V9.1 there is no relyable way to do this.
DB2 V9.7 provides a new tablespace type with "reclaimable storage" attribute that allows to reclaim space much easier.
If you have a lot of trapped free space in your V9.1 tablespaces below the current high watermark you may want to consider a homogenous system copy with R3load into new tablespaces. This should be combined with an upgrade to V9.7 to get the new tablespace types. Another way to reorganize tablespaces is to move all tables into new tablespaces using DB6CONV.
Regards
Frank -
How do I make embedded OC4J use IBM Db2 schema mapping
I am using JDeveloper 903 with a datasource which happens to be of type IBM DB2. Whenever, I try to deploy and test an entity bean from withinn JDeveloper, the embedded OC4J seems to be using a different database schema mapping scheme than what is required by IBM DB2. As a result of this OC4J tries to autocreate tables with wrong syntax and obviously fails. Can somebody tell me how do I get things setup correctly.
TIA
VimalMagnus,
The optimizations related to efficiently supporting overflow-style caching are not included in Coherence 3.5. I created COH-2338 and COH-2339 to track the progress of the related issues.
There are four different implementations of the PartitionAwareBackingMap for Coherence 3.5:
* PartitionSplittingBackingMap is the simplest implementation that simply partitions data across a number of backing maps; it is not observable.
* ObservableSplittingBackingMap is the observable implementation; it extends WrapperObservableMap and delegates to (wraps) a PartitionSplittingBackingMap.
* ObservableSplittingBackingCache is an extension to the ObservableSplittingBackingMap that knows how to manage ConfigurableCacheMap instances as the underlying per-partition backing maps; in other words, it can spread out and coalesce a configured amount of memory (etc.) across all the actual backing maps.
* ReadWriteSplittingBackingMap is an extension of the ReadWriteBackingMap that is partition-aware.
The DefaultConfigurableCacheFactory currently only uses the ObservableSplittingBackingCache and the ReadWriteSplittingBackingMap; COH-2338 relates to the request for improvement to add support for the other two implementations as well. Additionally, optimizations to load balancing (where overflow caching tends to get bogged down by many small I/O operations) will be important; those are tracked by COH-2339.
Peace,
Cameron Purdy
Oracle Coherence -
Path for db2 library 'libdb2.so' could not be determined
Any ideal why i would get this error, working on upgrading a system, it was working, then SUM shut it down and now it won't restart. i have tried lots of things and no luck. R3trans works fine.
CLASSPATH=:/db2/db2lxd/sqllib/java/db2java.zip:/db2/db2lxd/sqllib/java/runtime.zip:.:/db2/db2lxd/sqllib/java/db2java.zip:/db2/db2lxd/sqllib/java/runtime.zip:.
LD_LIBRARY_PATH=/usr/sap/LXD/SYS/exe/run:/usr/sap/LXD/SYS/exe/uc/linuxppc64
dev_w0
..retrieving configuration parameters
C ..done
C *** ERROR => path for db2 library 'libdb2.so' could not be determined
[dbdb6.c 11762]
C *** ERROR in getConfigurationAndEnvironmentHandle[/bas/741_REL/src/dbs/db6/dbdb6.c, 13610] CON = -1 (BEGIN)
C &+ DbSlConnectDB6: Unable to load DB2 libraries. Connect failed.
C &+
C &+
C *** ERROR in getConfigurationAndEnvironmentHandle[/bas/741_REL/src/dbs/db6/dbdb6.c, 13610] (END)
M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 75]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2280]
MHi David ,
Please check in Instance Kernel Directory /usr/sap/<SID>/<INSTANCE>/exe .
there should be db6_clidriver exists and where all lib files related to Db2 exists. if not then copy in from global/db6/<LINUX> .and try .
Thanks
Manas Behra
Maybe you are looking for
-
Hi, Please help on the Select Join query. I want to compare code_stat_system1/code_stat_system2 and code_date_system1 /code_date_system2 column from table #system1 and #system2 but there is 2 rule to get correct row from table #system1 and #system2.
-
Why does my Ipod display a syncing message then eject itself without syncing?
I tried reseting my Ipod and reinstalling Itunes, neither of these fixed the problem
-
Problem in Resource moving Oracle Fail safe
Hi , I have Os clustering Oracle Fail Safe configured here(10g enterprise Edition) While Performin test ... cluster resources are not moving to another server due to which oracle database are not getting start on another cluster node ... Plz help mee
-
Some people asked at this forum: "How to write Java Threadpool?" Here is an example, which I have tested on the computer with two CPU. This example also runs well with J#. TPTest.java package demo.test; import java.io.File; import java.io.FileWriter;
-
Weird Excel File appearing on my desktop
Hey guys, twice now this week an excel file appears on my desktop. This is what it looks like: It won't open in MS Excel. When I tried to trash it, I get the following message: What is this? And how do I get rid of it? Thanks.