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

INCORRECT MAPPING OF RC=2 I.E. ENOENT (FILE DOESN'T EXIST), TO ZRC=2
(WHICH MEANS DEADLOCK), INSIDE LOAD()

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
While trying to load a library using load(), if it  fails 
because the file doesn't exist, we try to print out errno 2, 
which is ENONET. (file doesn't exist.)  However, instead of 
calling pdLogSysRC() to print out errno, we call pdLog, which 
treats errno as zrc.  errno 2 means ENONENT.  zrc 2 means 
deadlock.  So, in db2diag.log, we have a deadlock message... 
 
2009-08-05-08.42.06.816763+060 I1406224C400       LEVEL: Severe 
PID     : 1090040              TID  : 1           PROC : 
db2fmp32 (3086) 
INSTANCE: db2uat               NODE : 000 
EDUID   : 1                    EDUNAME: db2fmp32 (3086) 
FUNCTION: DB2 UDB, oper system services, sqloLoadModuleEP, 
probe:40 
MESSAGE : ZRC=0x00000002=2 
          DIA8002C A deadlock has occurred, rolling back 
transaction.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* V97Fp2                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* While trying to load a library using load(), if it  fails    * 
*                                                              * 
* because the file doesn't exist, we try to print out errno 2, * 
*                                                              * 
* which is ENONET. (file doesn't exist.)  However, instead of  * 
*                                                              * 
* calling pdLogSysRC() to print out errno, we call pdLog,      * 
* which                                                        * 
* treats errno as zrc.  errno 2 means ENONENT.  zrc 2 means    * 
*                                                              * 
* deadlock.  So, in db2diag.log, we have a deadlock message... * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2009-08-05-08.42.06.816763+060 I1406224C400      LEVEL:      * 
* Severe                                                       * 
* PID    : 1090040              TID  : 1          PROC :       * 
*                                                              * 
* db2fmp32 (3086)                                              * 
*                                                              * 
* INSTANCE: db2uat              NODE : 000                     * 
*                                                              * 
* EDUID  : 1                    EDUNAME: db2fmp32 (3086)       * 
*                                                              * 
* FUNCTION: DB2 UDB, oper system services, sqloLoadModuleEP,   * 
*                                                              * 
* probe:40                                                     * 
*                                                              * 
* MESSAGE : ZRC=0x00000002=2                                   * 
*                                                              * 
*           DIA8002C A deadlock has occurred, rolling back     * 
*                                                              * 
* transaction.                                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V97Fp3                                            * 
****************************************************************
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
fixed in v97fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.04.2010
24.09.2010
24.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