Q Capture warm start might fail due to db2LogRead API return
-1273, after a restore and rollforward operation on pureScale,
even performing Q Capture Cold start, if you delete the logs in
previous log chain.
This might happen if the workload is driven on only a subset of
the members, after the rollforward followed by the cold start of
QREP.
Whenever the idle members start logging, a warm QREP scan will
always require to retrieve logs from the previous chain to avoid
-1273, but it will cause -1273 if the logs in previous log chain
are deleted.
The capture log might contain the following messages.
ASN8041D "Q Capture" : "ASN01" : "LogrdThread" : db2LogRead API
is sending us backwards in the DB2 Log: First LSN is
"0000:0000:35cb:b965:0000:0001:f4aa:ed74" while Next Start LSN
is "0000:0000:0000:0000:0000:0000:0000:0000"
ASN0552E "Q Capture" : "ASN01" : "logrd" : The program
encountered an SQL error. The server name is "SAMPLE". The SQL
request is "db2ReadLog". The table name is "". The SQLCODE is
"-1273". The SQLSTATE is " " ....
ASN0005E CAPTURE "ASN01" : "LogrdThread". The Capture program
encountered an error when reading the DB2 log. The log sequence
number is "0000:0000:35CB:B965:0000:0001:F4AA:ED74", the SQLCODE
is "-1273", and the reason code is "".
ASN7156I "Q Capture" : "ASN01" : "WorkerThread" : The Q Capture
program stopped processing log records in log file
"/db2/actlog/NODE0000/LOGSTREAM0004/S0001753.LOG".
The corresponding messages in db2diag.log are like this.
2014-12-03-00.34.56.533231+540 I343011474A1222 LEVEL: Info
PID : 22282450 TID : 37914 PROC :
db2sysc 4
INSTANCE: db2inst1 NODE : 004 DB :
SAMPLE
HOSTNAME: host01
EDUID : 37914 EDUNAME: db2lfr.4 (SAMPLE) 4
FUNCTION: DB2 UDB, data protection services, sqlpgOpenLogExtent,
probe:2164
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 : String, 19 bytes
Log is not found...
DATA #2 : Codepath, 8 bytes
18:23:25
DATA #3 : String, 99 bytes
extNum / logLocation / logStreamId / callerFlag / logFileName1 /
logFileName2 / callerSpecifiedPath
DATA #4 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
1753
DATA #5 : unsigned integer, 4 bytes
0
DATA #6 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
4
DATA #7 : Hex integer, 8 bytes
0x0000000000000401
DATA #8 : String, 0 bytes
Object not dumped: Address: 0x0A000000107FB038 Size: 0 Reason:
Zero-length data
DATA #9 : String, 0 bytes
Object not dumped: Address: 0x0A000000107FB160 Size: 0 Reason:
Zero-length data
DATA #10: String, 0 bytes
Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
Address is NULL
2014-12-03-00.34.56.536369+540 E343012697A597 LEVEL: Info
PID : 22282450 TID : 37143 PROC :
db2sysc 4
INSTANCE: db2inst1 NODE : 004 DB :
SAMPLE
HOSTNAME: host01
EDUID : 37143 EDUNAME: db2logmgr.4 (SAMPLE) 4
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4130
DATA #1 : <preformatted>
Started retrieve for log file S0001753.LOG for log stream 4 from
log chain 23.
Retrieval destination:
/db2/actlog/NODE0000/LOGSTREAM0004/LOGSTREAM0004/
Actual retrieval method: USE_METHOD1
2014-12-03-00.34.56.543735+540 I343013295A513 LEVEL: Info
PID : 22282450 TID : 37143 PROC :
db2sysc 4
INSTANCE: db2inst1 NODE : 004 DB :
SAMPLE
HOSTNAME: host01
EDUID : 37143 EDUNAME: db2logmgr.4 (SAMPLE) 4
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLogFile, probe:4148
DATA #1 : <preformatted>
Completed retrieve for log file S0001753.LOG on chain 23 to
/db2/actlog/NODE0000/LOGSTREAM0004/LOGSTREAM0004/.
2014-12-03-00.34.56.544729+540 I343013809A521 LEVEL:
Severe
PID : 22282450 TID : 37914 PROC :
db2sysc 4
INSTANCE: db2inst1 NODE : 004 DB :
SAMPLE
HOSTNAME: host01
EDUID : 37914 EDUNAME: db2lfr.4 (SAMPLE) 4
FUNCTION: DB2 UDB, data protection services,
sqlplfrGetFileHandleToReadFrom, probe:5250
DATA #1 : <preformatted>
LFR Scan Num = 10720
LFR Scan Caller's EDUID = 208328
Both log paths seem to be bad, try path1. extentNum = 1753 |
