IBM Support

IC74802: IF TABLESPACE IS NOT AVAILABLE ON STANDBY, AFTER TAKEOVER, THE T ABLESPACE ON NEW PRIMARY IS NOT IN ROLLFORWARD PENDING STATE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The problem can be reproduced in the following steps:
    
    1. setup HADR environment. We can assume the two instances as
    "Instance_Prim" and "Instance_Standby"
    
    2. Instance_Prim:
    db2 create db hadrtest
    db2 "create tablespace tbtest managed by database using (file
    'tbtest' 1M)"
    db2 backup db hadrtest to /TMP
    
    3. Instance_Standby:
    db2 restore db hadrtest from /TMP
    db2 start hadr on db hadrtest as standby
    
    4. Instance_Prim:
    db2 start hadr on db hadrtest as primary
    db2 connect to hadrtest
    db2 "create table hadr_prim.test (c1 int) in tbtest"
    
    5. Instance_Standby: .
    db2 deactivate db hadrtest
    db2 stop hadr on db hadrtest
    chmod 000 $HOME/$DB2INSTANCE/NODE0000/SQL00001/tbtest
    db2 start hadr on db hadrtest as standby
    
    6. Instance_Standby:
    db2 takeover hadr on db hadrtest
    db2 connect to hadrtest
    db2 list tablespaces
    
    After takeover, in step 6, the tablespace , tbtest state is
    offline. The correct tablespace state should be 'Rollforward
    Pending'.
    NOTE: To avoid the incorrect tablespace state, in step 5, avoid
    the command - "db2 stop hadr on db hadrtest".
    

Local fix

  • Do not run "stop hadr" in step 5
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The problem can be reproduced in the following steps:        *
    *                                                              *
    * 1. setup HADR environment. We can assume the two instances   *
    * as  "Instance_Prim" and "Instance_Standby"                   *
    *                                                              *
    * 2. Instance_Prim:                                            *
    * db2 create db hadrtest                                       *
    * db2 "create tablespace tbtest managed by database using      *
    * (file                                                        *
    * 'tbtest' 1M)"                                                *
    * db2 backup db hadrtest to /TMP                               *
    *                                                              *
    * 3. Instance_Standby:                                         *
    * db2 restore db hadrtest from /TMP                            *
    * db2 start hadr on db hadrtest as standby                     *
    *                                                              *
    * 4. Instance_Prim:                                            *
    * db2 start hadr on db hadrtest as primary                     *
    * db2 connect to hadrtest                                      *
    * db2 "create table hadr_prim.test (c1 int) in tbtest"         *
    *                                                              *
    * 5.  Instance_Standby:  .                                     *
    * db2 deactivate db hadrtest                                   *
    * db2 stop hadr on db hadrtest                                 *
    * chmod 000 $HOME/$DB2INSTANCE/NODE0000/SQL00001/tbtest        *
    *                                                              *
    * db2 start hadr on db hadrtest as standby                     *
    *                                                              *
    * 6. Instance_Standby:                                         *
    * db2 takeover hadr on db hadrtest                             *
    * db2 connect to hadrtest                                      *
    *                                                              *
    * After takeover, in step 6, the tablespace, tbtest state is   *
    * offline.  The correct tablespace state should be             *
    * 'Rollforward Pending'.                                       *
    * NOTE: To avoid the incorrect tablespace state, in step 5,    *
    * avoid the command - "db2 stop hadr on db hadrtest".          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to db2 version 9.7 fix pack 4.                       *
    ****************************************************************
    

Problem conclusion

  • The fix will be included in db2 version 9.7 fix pack 4.
    

Temporary fix

  • Do not run "stop hadr" in step 5
    

Comments

APAR Information

  • APAR number

    IC74802

  • 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-03-02

  • Closed date

    2011-05-09

  • Last modified date

    2011-05-09

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

    IC74635

  • 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 #: IC74802

Modified date: 09 May 2011