Troubleshooting
Problem
Log Reader Program might stop unexpectedly due to SQLCODE "-2657" from DB2LOGREAD
Symptom
Log Reader Program(Q Capture/Replication etc.) stopped abnormally, let's put Q Capture program as example here , the capture log might contain the following messages.
2016-06-08-10.38.15.972701 <logrdDB2LUW::readTheLog> ASN8041D "Q Capture" : "ASN" : "txrdThread" : db2LogRead API is sending us backwards in theDB2 Log: First LSN is "0000:0000:143d:00dc:47d2" while Next Start LSN is "0000:0000:0000:0000:0000"
2016-06-08-10.38.15.972877 <logrdDB2LUW::readTheLog> ASN0005E CAPTURE "ASN" : "txrdThread"。在读取 DB2 日志时，Capture 程序遇到了错误。日志序号为 "0000:0000:143D:00DC:47D2"，SQLCODE 为 "-2657"，原因码为 ""。
2016-06-08-10.38.15.980326 <logrdDB2LUW::readTheLog> ASN8999D SQL2657N “异步日志阅读器”需要日志文件 "S0082895.LOG"，而该文件当前未驻留在数据库日志目录中。
2016-06-08-10.38.15.980524 <asnqwk> ASN7109I "Q Capture" : "ASN" : "WorkerThread"：在程序终止时，仍然要落实的事务的最低日志序号 (LSN) 为 "0000:0000:143D:0045:3683"，而已成功处理的事务的最高日志序号 (MAXCMTSEQ) 为 "5757:845E:0000:0083:0000"。
2016-06-08-10.38.16.720554 <asnqwk> ASN7156I "Q Capture" : "ASN" : "WorkerThread"：Q Capture 程序已停止处理日志文件 "/tcbs/odblog/S0082895.LOG" 中的日志记录。
2016-06-08-10.38.16.720804 <stopLogrdThread> ASN8999D Waiting for log reader thread to stop
2016-06-08-10.38.16.722539 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "WorkerThread"：线程 "WorkerThread" 从现有线程 "txrdThread" 接收到返回码 "0"。
2016-06-08-10.38.18.723615 <asnThread::stop> ASN0589I "Q Capture" : "ASN" : "WorkerThread"：程序从例程 "pthread_kill" 接收到返回码 "3"。
2016-06-08-10.38.19.027999 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "WorkerThread" 接收到返回码 "910"。
2016-06-08-10.38.20.047991 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "AdminThread" 接收到返回码 "2001"。
2016-06-08-10.38.20.048072 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "PruneThread" 接收到返回码 "2011"。
2016-06-08-10.38.20.055657 <Asnenv:delEnvIpcQRcvHdl> ASN0595I "Q Capture" : "ASN" : "Initial"：程序除去了具有键 "(0x3000006f)" 的 IPC 队列。
2016-06-08-10.38.20.055705 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "HoldLThread" 接收到返回码 "0"。
2016-06-08-10.38.20.055831 <erWhatSignal> ASN0591I "Q Capture" : "ASN" : "HoldLThread"：线程 "HoldLThread" 接收到 "Handled" 信号 "SIGUSR2"。
2016-06-08-10.38.21.056773 <asnqcap::main> ASN0573I "Q Capture" : "ASN" : "Initial"：程序已停止。
The corresponding messages in db2diag.log are like this.
2016-05-23-21.14.55.144250+480 E146299801A378 LEVEL: Info
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
DATA #1 : <preformatted>
Started archive for log file S0082405.LOG.
2016-05-23-21.14.57.242541+480 E146300180A453 LEVEL: Info
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
DATA #1 : <preformatted>
Completed archive for log file S0082405.LOG to /tcbs/odbarchlog/db2odb/MYDB1/NODE0000/C0000008/ from /tcbs/odblog/.
2016-05-23-21.17.11.796844+480 I146303828A368 LEVEL: Warning
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0082405.LOG.
2016-05-23-21.17.29.322472+480 I146304197A409 LEVEL: Warning
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0082405.LOG on chain 8 to
/tcbs/odblog/.
2016-05-23-21.17.29.686034+480 I146304607A10750 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : Bad extent header:
DATA #1 : Hexdump, 2048 bytes
0x070000104745A570 : 029B 000A 0001 8011 4942 4D4C 4F47 0000 ........IBMLOG..
0x070000104745A580 : 0000 0000 0001 41E5 0001 0000 0001 0000 ......A......... --->>>0x141E5=82405
0x070000104745A590 : 573A B3C0 483D 10EB 573A B4AA 0000 0000 W:..H=..W:......
0x070000104745A5A0 : 0000 0000 0000 0000 0002 12D8 0000 0000 ................
0x070000104745A5B0 : 0000 0008 0000 0000 0000 1405 2B14 C781 ............+...
.....
2016-05-23-21.17.29.686712+480 I146315358A439 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : ExtNum =
DATA #1 : Hexdump, 4 bytes
0x0700000011BFDAB8 : 0001 42AD ..B. ---->> 0x142AD=82605
2016-05-23-21.17.29.686845+480 I146315798A384 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : Error 118489300 opening database log extent 82605:
2016-05-23-21.17.29.687407+480 I146316183A559 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgAddActiveLogByRename, probe:1480
MESSAGE : ZRC=0x071000D4=118489300=SQLP_EXT_BAD_FORMAT
"Invalid format in Extent header. filenumber, format or signature IDs."
DATA #1 : String, 54 bytes
Not able to create active log by renaming old log file
2016-05-23-21.17.29.687574+480 I146316743A406 LEVEL: Info
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRenameArchivedLog, probe:850
DATA #1 : <preformatted>
Ignore error 118489300 when renaming log 82405
2016-05-23-21.17.29.693922+480 E146317150A484 LEVEL: Warning
PID : 250322 TID : 62711 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
APPHDL : 0-146 APPID: *LOCAL.db2odb.160427150118
AUTHID : DB2INST1
EDUID : 62711 EDUNAME: db2agent (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpALR_OpenExtent, probe:0
MESSAGE : ADM1500W DB2 is unable to locate log file "S0082405.LOG".
2016-05-23-21.17.29.694368+480 I146317635A178 LEVEL: Warning
PID:250322 TID:62711 NODE:000 Title: SQLP_ALRCB
Dump File: /home/db2odb/sqllib/db2dump/250322.62711.000.dump.bin
2016-05-23-21.17.29.723330+480 I146317814A176 LEVEL: Error
PID:250322 TID:62711 NODE:000 Title: SQLP_ALRCB
Dump File: /home/db2odb/sqllib/db2dump/250322.62711.000.dump.bin
2016-05-23-21.17.29.723436+480 I146317991A578 LEVEL: Error
PID : 250322 TID : 62711 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
APPHDL : 0-146 APPID: *LOCAL.db2odb.160427150118
AUTHID : DB2INST1
EDUID : 62711 EDUNAME: db2agent (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlp_AsyncLogReadAPI, probe:210
DATA #1 : String, 132 bytes
Error: sqlcode -2657, rc 262144, hflag2LsnReuse 0
action 1, startLSN 0000141E5FA306AB, endLSN 0000141E7A3233F8, logBufferSize 262144
2016-06-08-10.38.15.972701 <logrdDB2LUW::readTheLog> ASN8041D "Q Capture" : "ASN" : "txrdThread" : db2LogRead API is sending us backwards in theDB2 Log: First LSN is "0000:0000:143d:00dc:47d2" while Next Start LSN is "0000:0000:0000:0000:0000"
2016-06-08-10.38.15.972877 <logrdDB2LUW::readTheLog> ASN0005E CAPTURE "ASN" : "txrdThread"。在读取 DB2 日志时，Capture 程序遇到了错误。日志序号为 "0000:0000:143D:00DC:47D2"，SQLCODE 为 "-2657"，原因码为 ""。
2016-06-08-10.38.15.980326 <logrdDB2LUW::readTheLog> ASN8999D SQL2657N “异步日志阅读器”需要日志文件 "S0082895.LOG"，而该文件当前未驻留在数据库日志目录中。
2016-06-08-10.38.15.980524 <asnqwk> ASN7109I "Q Capture" : "ASN" : "WorkerThread"：在程序终止时，仍然要落实的事务的最低日志序号 (LSN) 为 "0000:0000:143D:0045:3683"，而已成功处理的事务的最高日志序号 (MAXCMTSEQ) 为 "5757:845E:0000:0083:0000"。
2016-06-08-10.38.16.720554 <asnqwk> ASN7156I "Q Capture" : "ASN" : "WorkerThread"：Q Capture 程序已停止处理日志文件 "/tcbs/odblog/S0082895.LOG" 中的日志记录。
2016-06-08-10.38.16.720804 <stopLogrdThread> ASN8999D Waiting for log reader thread to stop
2016-06-08-10.38.16.722539 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "WorkerThread"：线程 "WorkerThread" 从现有线程 "txrdThread" 接收到返回码 "0"。
2016-06-08-10.38.18.723615 <asnThread::stop> ASN0589I "Q Capture" : "ASN" : "WorkerThread"：程序从例程 "pthread_kill" 接收到返回码 "3"。
2016-06-08-10.38.19.027999 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "WorkerThread" 接收到返回码 "910"。
2016-06-08-10.38.20.047991 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "AdminThread" 接收到返回码 "2001"。
2016-06-08-10.38.20.048072 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "PruneThread" 接收到返回码 "2011"。
2016-06-08-10.38.20.055657 <Asnenv:delEnvIpcQRcvHdl> ASN0595I "Q Capture" : "ASN" : "Initial"：程序除去了具有键 "(0x3000006f)" 的 IPC 队列。
2016-06-08-10.38.20.055705 <asnThread::stop> ASN0590I "Q Capture" : "ASN" : "Initial"：线程 "Initial" 从现有线程 "HoldLThread" 接收到返回码 "0"。
2016-06-08-10.38.20.055831 <erWhatSignal> ASN0591I "Q Capture" : "ASN" : "HoldLThread"：线程 "HoldLThread" 接收到 "Handled" 信号 "SIGUSR2"。
2016-06-08-10.38.21.056773 <asnqcap::main> ASN0573I "Q Capture" : "ASN" : "Initial"：程序已停止。
The corresponding messages in db2diag.log are like this.
2016-05-23-21.14.55.144250+480 E146299801A378 LEVEL: Info
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
DATA #1 : <preformatted>
Started archive for log file S0082405.LOG.
2016-05-23-21.14.57.242541+480 E146300180A453 LEVEL: Info
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
DATA #1 : <preformatted>
Completed archive for log file S0082405.LOG to /tcbs/odbarchlog/db2odb/MYDB1/NODE0000/C0000008/ from /tcbs/odblog/.
2016-05-23-21.17.11.796844+480 I146303828A368 LEVEL: Warning
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0082405.LOG.
2016-05-23-21.17.29.322472+480 I146304197A409 LEVEL: Warning
PID : 250322 TID : 31099 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 31099 EDUNAME: db2logmgr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0082405.LOG on chain 8 to
/tcbs/odblog/.
2016-05-23-21.17.29.686034+480 I146304607A10750 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : Bad extent header:
DATA #1 : Hexdump, 2048 bytes
0x070000104745A570 : 029B 000A 0001 8011 4942 4D4C 4F47 0000 ........IBMLOG..
0x070000104745A580 : 0000 0000 0001 41E5 0001 0000 0001 0000 ......A......... --->>>0x141E5=82405
0x070000104745A590 : 573A B3C0 483D 10EB 573A B4AA 0000 0000 W:..H=..W:......
0x070000104745A5A0 : 0000 0000 0000 0000 0002 12D8 0000 0000 ................
0x070000104745A5B0 : 0000 0008 0000 0000 0000 1405 2B14 C781 ............+...
.....
2016-05-23-21.17.29.686712+480 I146315358A439 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : ExtNum =
DATA #1 : Hexdump, 4 bytes
0x0700000011BFDAB8 : 0001 42AD ..B. ---->> 0x142AD=82605
2016-05-23-21.17.29.686845+480 I146315798A384 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:2880
MESSAGE : Error 118489300 opening database log extent 82605:
2016-05-23-21.17.29.687407+480 I146316183A559 LEVEL: Error
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgAddActiveLogByRename, probe:1480
MESSAGE : ZRC=0x071000D4=118489300=SQLP_EXT_BAD_FORMAT
"Invalid format in Extent header. filenumber, format or signature IDs."
DATA #1 : String, 54 bytes
Not able to create active log by renaming old log file
2016-05-23-21.17.29.687574+480 I146316743A406 LEVEL: Info
PID : 250322 TID : 31356 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
EDUID : 31356 EDUNAME: db2loggr (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRenameArchivedLog, probe:850
DATA #1 : <preformatted>
Ignore error 118489300 when renaming log 82405
2016-05-23-21.17.29.693922+480 E146317150A484 LEVEL: Warning
PID : 250322 TID : 62711 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
APPHDL : 0-146 APPID: *LOCAL.db2odb.160427150118
AUTHID : DB2INST1
EDUID : 62711 EDUNAME: db2agent (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpALR_OpenExtent, probe:0
MESSAGE : ADM1500W DB2 is unable to locate log file "S0082405.LOG".
2016-05-23-21.17.29.694368+480 I146317635A178 LEVEL: Warning
PID:250322 TID:62711 NODE:000 Title: SQLP_ALRCB
Dump File: /home/db2odb/sqllib/db2dump/250322.62711.000.dump.bin
2016-05-23-21.17.29.723330+480 I146317814A176 LEVEL: Error
PID:250322 TID:62711 NODE:000 Title: SQLP_ALRCB
Dump File: /home/db2odb/sqllib/db2dump/250322.62711.000.dump.bin
2016-05-23-21.17.29.723436+480 I146317991A578 LEVEL: Error
PID : 250322 TID : 62711 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : MYDB1
APPHDL : 0-146 APPID: *LOCAL.db2odb.160427150118
AUTHID : DB2INST1
EDUID : 62711 EDUNAME: db2agent (MYDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlp_AsyncLogReadAPI, probe:210
DATA #1 : String, 132 bytes
Error: sqlcode -2657, rc 262144, hflag2LsnReuse 0
action 1, startLSN 0000141E5FA306AB, endLSN 0000141E7A3233F8, logBufferSize 262144
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Recovery - Logging","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7","Edition":"Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21985178