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 IC67126 Status: Closed

A DATABASE WITH CIRCULAR LOGGING CAN FAIL IN CRASH RECOVERY TRYING TO
OPEN LOG FILES THAT DO NOT EXIST ON DISK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Crash recovery can incorrectly fail on a database with Circular 
logging if the Log Control File ( SQLOGCTL.LFH.1/2 ) 
has more pre-allocated, but unused, log files registered than 
what physically exists in the Active Log Directory. 
 
 
 
The db2diag.log may show the following messages during Crash 
Recovery : 
 
2010-03-04-22.46.39.425929+060 I59656006E429       LEVEL: Error 
PID     : 7918                 TID  : 47211861764416PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 44                   EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgicl, 
probe:2130 
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "S0000058.LOG" could not be found. 
 
2010-03-04-22.46.39.426554+060 I59656436E423       LEVEL: Error 
PID     : 7918                 TID  : 47211861764416PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 44                   EDUNAME: db2loggr (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInit, 
probe:1150 
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
 
Local Fix : Upgrade to a version that fixes this problem in 
order to let crash recovery complete, or contact DB2 Support in 
order to manually patch the Log Control File to circumvent the 
problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Crash recovery can incorrectly fail on a database            * 
* withCircularlogging if the Log Control File (                * 
* SQLOGCTL.LFH.1/2 )has more pre-allocated, but unused, log    * 
* files registeredthanwhat physically exists in the Active Log * 
* Directory.The db2diag.log may show the following messages    * 
* during CrashRecovery :2010-03-04-22.46.39.425929+060         * 
* I59656006E429      LEVEL:ErrorPID    : 7918                  * 
* TID  : 47211861764416PROC :db2sysc 0INSTANCE: db2inst1       * 
*      NODE : 000EDUID  : 44                  EDUNAME:         * 
* db2loggr (SAMPLE) 0FUNCTION: DB2 UDB, data protection        * 
* services, sqlpgicl,probe:2130RETCODE :                       * 
* ZRC=0x860F000A=-2045837302=SQLO_FNEX "File                   * 
* notfound."DIA8411C A file "S0000058.LOG" could not be        * 
* found.2010-03-04-22.46.39.426554+060 I59656436E423           * 
* LEVEL:ErrorPID    : 7918                TID  :               * 
* 47211861764416PROC :db2sysc 0INSTANCE: db2inst1              * 
* NODE : 000EDUID  : 44                  EDUNAME: db2loggr     * 
* (SAMPLE) 0FUNCTION: DB2 UDB, data protection services,       * 
* sqlpgLoggrInit,probe:1150RETCODE :                           * 
* ZRC=0x860F000A=-2045837302=SQLO_FNEX "File                   * 
* notfound."DIA8411C A file "" could not be found.Local Fix :  * 
* Upgrade to a version that fixes this problem inorder to let  * 
* crash recovery complete, or contact DB2 Supportinorder to    * 
* manually patch the Log Control File to circumventtheproblem. * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Look to Upgrade to a Version 9.7 Fix Pack 3 or later         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2010
27.09.2010
27.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 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.