IBM Support

IT27242: LOGARCHMETH2 OFF NOT UPDATED ON HADR STANDBY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Setting DB CFG parameter LOGARCHMETH2 to OFF in an HADR Standby
    database will not take effect even after a restart of the
    Standby database.
    Once this Standby takes over the Primary role, it will still try
    archiving to archive method 2.
    
    In db2diag.log it might show references to LOGARCHMETH2, .e.g:
    EDUID : 2222 EDUNAME: db2logmgr (DB) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpgRetryFailedArchive, probe:4780
    MESSAGE : Still unable to archive log file 129821 due to rc
    -2045771739 for
    LOGARCHMETH2 using ...
    
    Using "ps -elf | grep meth" it shows db2vend process
    db2logmgr.meth2 - (database_name), which is not expected when
    LOGARCHMETH2 is OFF.
    
    A side effect could be a disk full situation for the active log
    directory.
    This may happen, when archive method 1 works, but the archive
    method 2  target does not do any more work (e.g. a vendor
    product was switched off) and no failarchpath has been
    defined.
    

Local fix

  • LOGARCHMETH2 OFF only takes effect when the database is
    restarted while being in the new Primary role.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT27242

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-07

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

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

    IT27291

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020