IBM Support

IC78186: HADR STANDBY MAY TRY TO RETRIEVE LOG FILES EVEN WHEN LOG ARCHIVE METHOD IS SET TO LOGRETAIN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • HADR standby database may still try to retrieve log files from
    archive device even after userexit is turned off.
    
    
    When hitting the problem, database configuration looks like
    this:
     Log retain for recovery enabled             (LOGRETAIN) =
    RECOVERY
     First log archive method                 (LOGARCHMETH1) =
    LOGRETAIN
     User exit for logging enabled                (USEREXIT) = OFF
    
    Normally, with the above configuration, HADR standby should not
    retrieve log files for local catchup. However, when hitting this
    problem, similar messages could be found in db2diag.log:
    
    2011-05-21-20.37.50.736389-300 I71697A360         LEVEL: Warning
    PID     : 25165998             TID  : 5792        PROC : db2sysc
    0
    INSTANCE: db2inst1               NODE : 000
    EDUID   : 5792                 EDUNAME: db2lfr (SAMPLE) 0
    FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600
    MESSAGE : Extent 249204 in log path may be stale. Trying
    archive.
    
    2011-05-21-20.37.50.736576-300 I72058A364         LEVEL: Warning
    PID     : 25165998             TID  : 5021        PROC : db2sysc
    0
    INSTANCE: db2inst1               NODE : 000
    EDUID   : 5021                 EDUNAME: db2logmgr (SAMPLE) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4130
    MESSAGE : Started retrieve for log file S0249204.LOG.
    
    2011-05-21-20.37.50.736675-300 I72423A418         LEVEL: Warning
    PID     : 25165998             TID  : 5021        PROC : db2sysc
    0
    INSTANCE: db2inst1               NODE : 000
    EDUID   : 5021                 EDUNAME: db2logmgr (HADRDB) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetrieveLogFile, probe:4148
    MESSAGE : Completed retrieve for log file S0249204.LOG on chain
    0 to
              /db2/P21/log_dir/NODE0000/.
    
    Please also take db2pd -db dbname -dpsdbcb and send the output
    to
    IBM or further investigation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to  DB2 Version 9.7 Fix Pack 6                       *
    ****************************************************************
    

Problem conclusion

  • Problem first fixed in DB2 Version 9.7 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC78186

  • 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-08-17

  • Closed date

    2012-10-20

  • Last modified date

    2012-10-20

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

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

    IC84230

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
20 October 2012