DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************

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.

Problem was first fixed in Version 9.7 Fix Pack 10. 
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.

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.

Vorgänger  : APAR is sysrouted TO one or more of the following: IC98913 IC98914 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

15.01.2014
27.11.2014
27.11.2014

9.7.FP10