IBM Support

IC74810: DB2 INSTANCE MAY CRASH IN SQLODB2NAMESPACE()

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If you have an environment with multiple DB2 instances
    databases and catalogued your databases with local
    node, the DB2 instance can crash in  the function
    sqloDB2Namespace() during some database operations.
    
    Basically, the affected scenario includes any cross-copy local
    connect, when extended security is on.
    
    This is an example of the stack that you can get :
    
    <StackTrace>
    <sqloDB2Namespace> <NotFound:-1>
    <sqlccipcconnr> <sqlccipc.C:1554>
    <sqlccconnr> <sqlcccmn.C:1799>
    <sqljcCommConnect> <sqljcmn.C:2341>
    <sqljcCmnMgrInit> <sqljcmn.C:298>
    <sqljrCreateTransport> <sqljrcomm.C:2052>
    <sqljrAssociateTransport> <sqljrclient.C:2419>
    <sqljrInternalConnect> <sqljrcomm.C:996>
    <sqljrFindBestAddressAndConnect> <sqljrcomm.C:1998>
    <sqljrDrdaArAuthenticate> <sqljrsec.C:169>
    <sqlexAppAuthenticate> <sqlexsmc.C:1414>
    <sqljrDrdaArConnect> <sqljrintrfc.C:340>
    <sqleUCdrdaARinit> <sqleu_common.C:446>
    <sqleUCappConnect> <sqleu_client.C:3840>
    <sqlxaConnect> <sqlxapi.C:5121>
    <sqlxa_open> <sqlxapi.C:2842>
    <sqlxa_open2> <sqlxapi.C:2563>
    <DRDA_Connection::xa_open>
    </StackTrace>
    

Local fix

  • catalog the node as TCPIP instead of LOCAL
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 LUW with federated databases                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 9.7 FP5 or above                              *
    ****************************************************************
    

Problem conclusion

  • The problem was first fixed in DB2 9.7 FP5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC74810

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-03

  • Closed date

    2012-01-02

  • Last modified date

    2012-05-17

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

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

Fix information

  • Fixed component name

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC74810

Modified date: 17 May 2012