IBM Support

IC79601: DATABASE COULD BECOME OFFLINE WHEN STOPPING HADR ON PRIMARY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When stopping HADR on an active primary database  with command
    "stop hadr on db dbname", the database is expected to become a
    standard  database and continue to function normally.
    However, in some situation, the  database could be brought
    offline after the same  command.
    
    Messages similar to the following might  appear in the
    db2diag.log:
    
    2011-10-07-17.20.57.326550-240 I63744A399         LEVEL: Error
    PID     : 10158182             TID  : 20625       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 20625                EDUNAME: db2hadrp (HADRDB) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrBindAndListen, probe:20320
    RETCODE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE "Address
    already in use"
    ......
    2011-10-07-17.20.57.326961-240 I64883A376         LEVEL: Severe
    PID     : 10158182             TID  : 20625       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 20625                EDUNAME: db2hadrp (HADRDB) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrEduEntry, probe:21100
    MESSAGE : HADR marking logs bad; database should shut down.
    ......
    2011-10-07-17.20.57.328665-240 I66131A459         LEVEL: Error
    PID     : 10158182             TID  : 14457       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000         DB   : HADRDB
    EDUID   : 14457                EDUNAME: db2loggr (HADRDB) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgsck, probe:430
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
    cannot be used"
              DIA8414C Logging can not continue due to an error.
    

Local fix

  • Once this problem is experienced issue restart  database to
    bring the database online again.  If the standby side HADR was
    stopped already it needs to be restarted before issuing restart
    database in the primary side.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users using HADR                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A stop hadr command in active primary HADR database can      *
    * result into a  database down situation marking a transaction *
    * log file temporarily bad.                                    *
    * A restart database command will bring the database on-line   *
    * again.                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 6 or higher to avoid     *
    * experiencing this issue.                                     *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.7 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC79601

  • 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

    2011-11-03

  • Closed date

    2012-06-18

  • Last modified date

    2012-06-18

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

    IC79341

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

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC79601

Modified date: 18 June 2012