During log file size change, when customer runs deactivate db(or
db2stop) twice on HADR Primary, A log file on HADR Standby never
gets updated/resized when new log file size introduces in its
previous extent. that's because, If there's an empty extent with
incorrect log file size in standby active log path, Standby
doesn't check the log file size, so it blindly thinks the log
file is good. if customer issues db2stop/reactivate db on HADR
Standby while meeting this issue, Standby will mistakenly
truncate the log file, and will fail to connect to Primary due
to pair validation errors.
you might see below messages in db2diag.log of Standby, when we
hit this APAR, Note:NextFormatExtNum 136867 is missed.
i.e
2014-07-27-02.05.35.233516-300 I11101A431 LEVEL: Info
PID : 11927608 TID : 10282 PROC : db2sysc
0
INSTANCE: db2sm1 NODE : 000 DB : SM1
EDUID : 10282 EDUNAME: db2hadrs (SM1) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSPrepareLogWrite, probe:10330
DATA #1 : <preformatted>
NextFormatExtNum 136866, create log file with firstlso
28649961820385
2014-07-27-02.15.10.521227-300 I62104A431 LEVEL: Info
PID : 10616928 TID : 10282 PROC : db2sysc
0
INSTANCE: db2sm1 NODE : 000 DB : SM1
EDUID : 10282 EDUNAME: db2hadrs (SM1) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSPrepareLogWrite, probe:10330
DATA #1 : <preformatted>
NextFormatExtNum 136868, create log file with firstlso
28650496069857 |
