DB2 FOR LUW / DB2FORLUW / B10 - DB2

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.

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

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

not known / see Local fix

forerunner  : 
follow-up : IT27291 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

07.12.2018
16.01.2020
16.01.2020