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

WHEN USING LDAP AS DIRECTORY ENTRY TYPE ON WINDOWS, THERE CAN BE SOME
SPORADIC SQL5005C ERRORS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When using LDAP as directory entry type on Windows, there can be 
some sporadic SQL5005C errors. 
 
For example "db2 get db cfg for <dbname>" fails, but works, when 
you connect to db first. 
 
dbdiag.log shows: 
 
2015-01-16-17.28.03.918000+060 I16208F1597          LEVEL: Error 
PID     : 3476                 TID : 8836           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
APPHDL  : 0-4650               APPID: *LOCAL.DB2.150116150109 
AUTHID  : Y002578S             HOSTNAME: AT010000SAD21 
EDUID   : 8836                 EDUNAME: db2agent (instance) 0 
FUNCTION: DB2 UDB, config/install, sqlfGetGDBPath, probe:1668 
MESSAGE : 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. 
 
DATA #1 : String, 25 bytes 
Error with dbDir commands 
DATA #2 : String, 6 bytes 
DWHBAP 
DATA #3 : Pointer, 8 bytes 
0x0000000b3649c998 
DATA #4 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
0x0000000B36494500 : 0000 0000 0000 0000 0000 0000 16FC FFFF 
................ 
0x0000000B36494510 : 0400 5C44 4232 0000 0000 0000 0000 0000 
..\DB2.......... 
0x0000000B36494520 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0000000B36494530 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0000000B36494540 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0000000B36494550 : 0000 0000 0000 0000 7371 6C65 646F 7364 
........sqledosd 
0x0000000B36494560 : 0282 001F 0000 0000 0000 0000 0000 0000 
................ 
0x0000000B36494570 : 0000 0000 0000 0000 2020 2020 2020 2020 
........ 
0x0000000B36494580 : 2020 2000 0000 0000 
..... 
 
2015-01-16-17.28.03.949000+060 I17807F762           LEVEL: Error 
PID     : 3476                 TID : 8836           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
APPHDL  : 0-4650               APPID: *LOCAL.DB2.150116150109 
AUTHID  : Y002578S             HOSTNAME: AT010000SAD21 
EDUID   : 8836                 EDUNAME: db2agent (instance) 0 
FUNCTION: DB2 UDB, config/install, sqlfGetDbCfg, probe:8395 
MESSAGE : 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:                                              * 
* WINDOWS                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fixpack 7                        * 
****************************************************************
Local-Fix:
Lösung
Problem was first fixed in DB2 version 10.5 fixpack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.02.2015
22.01.2016
22.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList