IBM Support

IC98747: TRAP OR HANG WHEN LDAP DIRECTORY ENTRIES FOR A DB2 DATABASE ARE INCONSISTENT.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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.
    

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.
    

Problem summary

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

Problem conclusion

  • 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.
    

Temporary fix

  • 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.
    

Comments

APAR Information

  • APAR number

    IC98747

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-15

  • Closed date

    2014-11-27

  • Last modified date

    2014-11-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC98913 IC98914

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

  • RA10 PSN

       UP

  • RA50 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC98747

Modified date: 27 November 2014