|
Problem IC98914
|
Status: Closed |
TRAP OR HANG WHEN LDAP DIRECTORY ENTRIES FOR A DB2 DATABASE ARE INCONSISTENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When there is inconsistency in the LDAP directory entries for a
DB2 database, various trap or hang symptoms might occur.
An example of such an inconsistency is if the the value of
db2nodeName in the db2db2nodePtr attribute of a db2databaseAlias
entry is different from the db2nodeName that is the parent of
the db2databaseAlias entry.
Possible symptoms are that Command Line Processor traps when you
run LIST DATABASE DIRECTORY or REFRESH LDAP commands, or that
the LIST DATABASE DIRECTORY command does not output all
cataloged databases, or that attempts to connect to the database
return error SQL0902N or cause the application to hang or trap. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 for Linux, UNIX and Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
Such inconsistencies in LDAP directory entries for a database
can come about if you edit LDAP directory entries directly using
a third-party tool. To avoid such inconsistencies use DB2
commands to update DB2 node and database information that is
cataloged in LDAP rather than edit the LDAP directory entries
directly. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.5 Fix Pack 3.
At a minimum, this fix should be applied on the database client
and if there is a separate DB2 Connect database gateway then on
the gateway too. |
| Workaround |
To avoid inconsistencies in LDAP entries for a database, use DB2
commands to update DB2 node and database information that is
cataloged in LDAP rather than edit the LDAP directory entries
directly. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.01.2014
28.02.2014
28.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
