IBM Support

IC91378: SQLCODE -1229 RECEIVED ON DB2LUSED CONTINUOSLY EVEN AFTER A LOT OF TIME HAS PASSED AFTER THE LAST NODE RECOVERY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In DPF systems, users may observe that the db2lused continues to
    get the below error messages continuously even after a node
    recovery has completed successfully much in the past:
    ----------------------------------------------------------------
    -------------
    
    AUTHID  : XXXXX               HOSTNAME: XXXXXX
    EDUID   : 11053                EDUNAME: db2lused (DATABASE_NAME)
    0
    FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
    DATA #1 : String, 92 bytes
    Due to node failure at node 0 received sqlcode -1229 for request
    80000004 from node number 0
    DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1229   sqlerrml:
    49
     sqlerrmc: X SRC_CODEPAGE DATABASE_NAME OS_DETAILS
    DESTINATION_CODEPAGE
     sqlerrp : SQLRR06A
     sqlerrd : (1) 0x81580016      (2) 0x00000016      (3)
    0x00000000
               (4) 0x00000003      (5) 0xFFFFFB50      (6)
    0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
     sqlstate:
    
    ----------------------------------------------------------------
    -----------
    
    After a node failure the sqlca is set with -1229. When the node
    recovery completes and returns from the corresponding functions,
    the sqlca is not reset. So this -1229 from a previous node
    failure gets dumped in sqleMergeSqlca and thus logged
    continuously as seen above.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Problem Description Above.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix pack 9.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in Version 9.7 Fix pack 9.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC91378

  • 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

    2013-04-05

  • Closed date

    2014-03-10

  • Last modified date

    2014-03-10

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

    IC91361

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC91378

Modified date: 10 March 2014