Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC93744 Status: Geschlossen

During First Connect, this entry appears in the db2diag.log: "SQL5005:
sqloclose rc = -2045837302"

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When a database is activating, DB2 may automatically update 
certain database configuration parameters. In some  cases, these 
updates will try to close a file that is already closed. When 
this occurs, sqloclose will fail and the following entry will 
appear in the db2diag.log: 
 
2013-11-13-12.37.45.069405-300 E285739E625           LEVEL: 
Error 
PID     : 22443                TID : 46913210542400  KTID : 
24657 
PROC    : db2sysc 0 
INSTANCE: db2inst1              NODE : 000            DB   : DB1 
APPHDL  : 1-97                 APPID: *N1.db2inst1.131113173625 
AUTHID  : db2inst1              HOSTNAME: host1 
EDUID   : 88                   EDUNAME: db2agntp (M1) 0 
FUNCTION: DB2 UDB, config/install, sqlfIntUpdateDbCfg, 
probe:3715 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
DATA #1 : <preformatted> 
SQL5005: sqloclose rc = -2045837302 
 
 
2013-11-13-12.37.49.468782-300 I287324E672           LEVEL: 
Severe 
PID     : 22443                TID : 46913210542400  KTID : 
24657 
PROC    : db2sysc 0 
INSTANCE: db2inst1              NODE : 000            DB   : DB1 
APPHDL  : 1-97                 APPID: *N1.db2inst1.131113173625 
AUTHID  : db2inst1              HOSTNAME: host1 
EDUID   : 88                   EDUNAME: db2agntp (M1) 0 
FUNCTION: DB2 UDB, config/install, sqlfIntUpdateDbCfg, probe:6 
RETCODE : ZRC=0xFFFFEC73=-5005 
          SQL5005C  The operation failed because the database 
manager failed to 
          access either the database manager configuration file 
or the database 
          configuration file.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When a database is activating, DB2 may automatically update  * 
* certain database configuration parameters. In some cases,    * 
* these updates will try to close a file that is already       * 
* closed. When this occurs, sqloclose will fail and the        * 
* following entry will appear in the db2diag.log:              * 
*                                                              * 
* 2013-11-13-12.37.45.069405-300 E285739E625           LEVEL:  * 
* Error                                                        * 
* PID     : 22443                TID : 46913210542400  KTID :  * 
* 24657                                                        * 
* PROC    : db2sysc 0                                          * 
* INSTANCE: db2inst1              NODE : 000            DB   : * 
* DB1                                                          * 
* APPHDL  : 1-97                 APPID:                        * 
* *N1.db2inst1.131113173625                                    * 
* AUTHID  : db2inst1              HOSTNAME: host1              * 
* EDUID   : 88                   EDUNAME: db2agntp (M1) 0      * 
* FUNCTION: DB2 UDB, config/install, sqlfIntUpdateDbCfg,       * 
* probe:3715                                                   * 
* MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not     * 
* found."                                                      * 
*           DIA8411C A file "" could not be found.             * 
* DATA #1 : <preformatted>                                     * 
* SQL5005: sqloclose rc = -2045837302                          * 
*                                                              * 
*                                                              * 
* 2013-11-13-12.37.49.468782-300 I287324E672           LEVEL:  * 
* Severe                                                       * 
* PID     : 22443                TID : 46913210542400  KTID :  * 
* 24657                                                        * 
* PROC    : db2sysc 0                                          * 
* INSTANCE: db2inst1              NODE : 000            DB   : * 
* DB1                                                          * 
* APPHDL  : 1-97                 APPID:                        * 
* *N1.db2inst1.131113173625                                    * 
* AUTHID  : db2inst1              HOSTNAME: host1              * 
* EDUID   : 88                   EDUNAME: db2agntp (M1) 0      * 
* FUNCTION: DB2 UDB, config/install, sqlfIntUpdateDbCfg,       * 
* probe:6                                                      * 
* RETCODE : ZRC=0xFFFFEC73=-5005                               * 
*           SQL5005C  The operation failed because the         * 
* database manager failed to                                   * 
*           access either the database manager configuration   * 
* file or the database                                         * 
*           configuration file.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 Fix Pack 3.                          * 
****************************************************************
Local-Fix:
Update the database configuration parameters NUM_IOCLEANERS and 
NUM_IOSERVERS 
to a fixed value before database activation.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 10.1 Fix Pack 3
Workaround
See LOCAL FIX
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.06.2013
20.11.2013
20.11.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList