Users may see some DEBUG LOGIC errors in the db2diag.log. It may
revolve around the archival of a log and then less than a second
later another process is trying to open or read the log file.
Similar errors will be reported in the db2diag.log:
2011-09-13-23.32.21.141501-240 E3747622A381 LEVEL: Info
PID : 558020 TID : 3600 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 3600 EDUNAME: db2logmgr (TEST)
FUNCTION: DB2 UDB, data protection services,
sqlpgArchiveLogFile, probe:3108
DATA #1 : <preformatted>
Started archive for log file S0012024.LOG.
<break>
2011-09-13-23.32.21.386943-240 E3753872A1024 LEVEL: Error
(OS)
PID : 558020 TID : 17993 PROC : db2sysc
37
INSTANCE: db2inst1 NODE : 037 DB : TEST
APPHDL : xx-xxx APPID: *xxx.db2inst1.xxxxxxxxxx
AUTHID : HDW1PRD1
EDUID : 17993 EDUNAME: db2agent (TEST)
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:70
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
error detected"
DIA8501C A buffer pool logic error has occurred.
CALLED : OS, -, open
OSERR : EINVAL (22) "Invalid argument"
DATA #1 : Codepath, 8 bytes
4:9:18:20:31:33
DATA #2 : signed integer, 4 bytes
1
DATA #3 : File name, 57 bytes
/db2path/db2inst1/NODE0000/SQL00001/SQLOGDIR/S0012024.LOG
DATA #4 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS,
4 bytes
SQLO_REVISE, SQLO_READONLY, SQLO_SHAREWRITE,
SQLO_SECTOR_ALIGNED, SQLO_NO_THREAD_LEVEL_FILE_LOCK
DATA #5 : Hex integer, 4 bytes
0x00000180
DATA #6 : signed integer, 4 bytes
0
2011-09-13-23.32.21.403739-240 I3754897A545 LEVEL: Error
PID : 558020 TID : 17993 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : TEST
APPHDL : xx-xxx APPID:
*xxx.db2inst1.xxxxxxxxxxxxx
AUTHID : DB2INST1
EDUID : 17993 EDUNAME: db2agent (TEST)
FUNCTION: DB2 UDB, data protection services, sqlpgolf, probe:220
RETCODE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
error detected"
DIA8501C A buffer pool logic error has occurred. |
