home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC66579 Status: Closed

HADR STANDBY (DB2HADRS) MIGHT PANIC IF IT CANNOT CLOSE SQLOGMIR.LFH DURING
SHUTDOWN.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
A HADR standby EDU (db2hadrs) might invoke a panic to bring 
instance down if the EDU cannot close mirror log control file 
(SQLOGMIR.LFH) while it is being shutdown. 
The following db2diag.log entries show the problem. The 
sqloclose() indicates the file has already been closed by the 
other EDU. So HADR standby do not need to close it, and  should 
not panic. 
 
20010-01-22-18.08.42.843837+540 E36716560A735      LEVEL: Error 
(OS) 
PID     : 156072               TID  : 12500       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 12500                EDUNAME: db2hadrs (SAMPLE) 0 
FUNCTION: DB2 UDB, oper system services, sqloclose, probe:20 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
CALLED  : OS, -, close 
OSERR   : EBADF (9) "Bad file number" 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
0x0700000004BFDCE0 : FFFF FFFF 0000 0100 
........ 
DATA #2 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
2010-01-22-18.08.42.859223+540 I36717710A434      LEVEL: Error 
PID     : 156072               TID  : 12500       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 12500                EDUNAME: db2hadrs (SAMPLE) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrCloseLogFiles, probe:31920 
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
 
2010-01-22-18.08.42.871074+540 E36718961A832      LEVEL: 
Critical 
PID     : 156072               TID  : 12500       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 12500                EDUNAME: db2hadrs (SAMPLE) 0 
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: "Panic".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use HADR.                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A HADR standby EDU (db2hadrs) might invoke a panic to bring  * 
* instance down if the EDU cannot close mirror log control     * 
* file (SQLOGMIR.LFH) while it is being shutdown.              * 
* The following db2diag.log entries show the problem. The      * 
* sqloclose() indicates the file has already been closed by    * 
* the other EDU. So HADR standby do not need to close it, and  * 
* should not panic.                                            * 
*                                                              * 
* 20010-01-22-18.08.42.843837+540 E36716560A735  LEVEL:        * 
* Error(OS)                                                    * 
* PID     : 156072             TID  : 12500      PROC :        * 
* db2sysc                                                      * 
* INSTANCE: db2inst1           NODE : 000                      * 
* EDUID   : 12500              EDUNAME: db2hadrs (SAMPLE) 0    * 
* FUNCTION: DB2 UDB, oper system services, sqloclose, probe:20 * 
*                                                              * 
* MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not     * 
* found."                                                      * 
* DIA8411C A file "" could not be found.                       * 
* CALLED  : OS, -, close                                       * 
* OSERR  : EBADF (9) "Bad file number"                         * 
* DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes         * 
* 0x0700000004BFDCE0 : FFFF FFFF 0000 0100                     * 
* DATA #2 : String, 105 bytes                                  * 
* Search for ossError*Analysis probe point after this log      * 
* entry for further self-diagnosis of this problem.            * 
*                                                              * 
*                                                              * 
* 2010-01-22-18.08.42.859223+540 I36717710A434   LEVEL: Error  * 
* PID     : 156072             TID  : 12500      PROC :        * 
* db2sysc                                                      * 
* INSTANCE: db2inst1           NODE : 000                      * 
* EDUID   : 12500              EDUNAME: db2hadrs (SAMPLE) 0    * 
* FUNCTION: DB2 UDB, High Availability Disaster Recovery,      * 
* hdrCloseLogFiles, probe:31920                                * 
* RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not     * 
* found."                                                      * 
* DIA8411C A file "" could not be found.                       * 
*                                                              * 
* 2010-01-22-18.08.42.871074+540 E36718961A832   LEVEL:        * 
* Critical                                                     * 
* PID     : 156072             TID  : 12500      PROC :        * 
* db2sysc                                                      * 
* INSTANCE: db2inst1           NODE : 000                      * 
* EDUID   : 12500              EDUNAME: db2hadrs (SAMPLE) 0    * 
* FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10  * 
* MESSAGE : ADM14001C  An unexpected and critical error has    * 
*                                                              * 
* occurred: "Panic"                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to version 9.8 fixpack 3 or later.            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in Version 9.8 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.02.2010
08.08.2011
08.08.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList