Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC85999 Status: Closed

START HADR AS STANDBY MAY FAIL TO REPLY THE MANUAL COPIED LOGS FROM THE
PRIMARY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In some situation, due to the netwrok failure, the redo logs on 
standby necessitate the manual copies from primary database. 
However, if the copied logs from primary have some mismatched 
log control information with the local logs on standby which 
could be caused by former take over by force command on primary, 
when issuing start hadr on standby, db2 will not reply the 
copied logs from primary due to the incorrect log chain 
information. The following similar messages could be seen in 
standby db2diag.log: 
 
2012-08-15-19.13.29.629980+480 I830382529A556     LEVEL: Warning 
PID     : 3408852              TID  : 6427        PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000         DB   : 
SAMPLE 
APPHDL  : 0-56                 APPID: *LOCAL.DB2.120815111329 
EDUID   : 6427                 EDUNAME: db2agent (PR2) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, 
probe:710 
DATA #1 : <preformatted> 
Invoking database rollforward forward recovery, 
lowtranlsn 0000005D7AFB13B1 in log file number 757 
minbufflsn 0000005D7AFB13B1 in log file number 757 
 
2012-08-15-19.13.30.000479+480 I830385582A364     LEVEL: Warning 
PID     : 3408852              TID  : 6988        PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 6988                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4130 
MESSAGE : Started retrieve for log file S0000757.LOG. 
 
2012-08-15-19.13.32.152035+480 I830385947A420     LEVEL: Warning 
PID     : 3408852              TID  : 6988        PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 6988                 EDUNAME: db2logmgr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4148 
MESSAGE : Completed retrieve for log file S0000757.LOG on chain 
68 to 
          /db2/PR2/log_dir1/NODE0000/. 
 
2012-08-15-19.13.32.999043+480 I830386368A478     LEVEL: Error 
PID     : 3408852              TID  : 7759        PROC : db2sysc 
0 
INSTANCE: db2inst1               NODE : 000 
EDUID   : 7759                 EDUNAME: db2lfr (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrIsLogFromValidChain, 
probe:5150 
DATA #1 : <preformatted> 
Log file S0000757.LOG is not from the correct log chain, 
lfcbFlags 1 PId 1345026323 CId 1345026324 state 
 229457 lfrScanStartPId 1345025174 bkpExtCID 0 
 
The log control information "lfrScanStartPId 1345025174" which 
is stored in log control file does not match the information 
"PId 1345026323" in the current log file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In some situation, due to the netwrok failure, the redo logs * 
* on                                                           * 
* standby necessitate the manual copies from primary database. * 
* However, if the copied logs from primary have some           * 
* mismatched                                                   * 
* log control information with the local logs on standby which * 
* could be caused by former take over by force command on      * 
* primary,                                                     * 
* when issuing start hadr on standby, db2 will not reply the   * 
* copied logs from primary due to the incorrect log chain      * 
* information. The following similar messages could be seen in * 
* standby db2diag.log:                                         * 
*                                                              * 
* 2012-08-15-19.13.29.629980+480 I830382529A556     LEVEL:     * 
* Warning                                                      * 
* PID     : 3408852              TID  : 6427        PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: db2inst1               NODE : 000         DB   :   * 
* SAMPLE                                                       * 
* APPHDL  : 0-56                 APPID:                        * 
* *LOCAL.DB2.120815111329                                      * 
* EDUID   : 6427                 EDUNAME: db2agent (PR2) 0     * 
* FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery,    * 
* probe:710                                                    * 
* DATA #1 : <preformatted>                                     * 
* Invoking database rollforward forward recovery,              * 
* lowtranlsn 0000005D7AFB13B1 in log file number 757           * 
* minbufflsn 0000005D7AFB13B1 in log file number 757           * 
*                                                              * 
* 2012-08-15-19.13.30.000479+480 I830385582A364     LEVEL:     * 
* Warning                                                      * 
* PID     : 3408852              TID  : 6988        PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: db2inst1               NODE : 000                  * 
* EDUID   : 6988                 EDUNAME: db2logmgr (SAMPLE) 0 * 
* FUNCTION: DB2 UDB, data protection services,                 * 
* sqlpgRetrieveLogFile, probe:4130                             * 
* MESSAGE : Started retrieve for log file S0000757.LOG.        * 
*                                                              * 
* 2012-08-15-19.13.32.152035+480 I830385947A420     LEVEL:     * 
* Warning                                                      * 
* PID     : 3408852              TID  : 6988        PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: db2inst1               NODE : 000                  * 
* EDUID   : 6988                 EDUNAME: db2logmgr (SAMPLE) 0 * 
* FUNCTION: DB2 UDB, data protection services,                 * 
* sqlpgRetrieveLogFile, probe:4148                             * 
* MESSAGE : Completed retrieve for log file S0000757.LOG on    * 
* chain                                                        * 
* 68 to                                                        * 
*           /db2/PR2/log_dir1/NODE0000/.                       * 
*                                                              * 
* 2012-08-15-19.13.32.999043+480 I830386368A478     LEVEL:     * 
* Error                                                        * 
* PID     : 3408852              TID  : 7759        PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: db2inst1               NODE : 000                  * 
* EDUID   : 7759                 EDUNAME: db2lfr (SAMPLE) 0    * 
* FUNCTION: DB2 UDB, recovery manager,                         * 
* sqlplfrIsLogFromValidChain,                                  * 
* probe:5150                                                   * 
* DATA #1 : <preformatted>                                     * 
* Log file S0000757.LOG is not from the correct log chain,     * 
* lfcbFlags 1 PId 1345026323 CId 1345026324 state              * 
*  229457 lfrScanStartPId 1345025174 bkpExtCID 0               * 
*                                                              * 
* The log control information "lfrScanStartPId 1345025174"     * 
* which                                                        * 
* is stored in log control file does not match the information * 
* "PId 1345026323" in the current log file.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp8                                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The fix is included in db2_v97fp8.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91733 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.08.2012
02.04.2013
02.04.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.