DB2 FOR LUW / DB2FORLUW / A10 - DB2

After a restore the database will be in rollforward pending. 
Now, if we consider the current settings for LOGARCHMETHx: 
 
First log archive method (LOGARCHMETH1) = TSM:DB2_LOG 
 
Second log archive method (LOGARCHMETH2) = DISK:<path> 
 
for handling reason the DBA might want to update LOGARCHMETH1 to 
USEREXIT and LOGARCHMETH2 to OFF. Right now this can not be done 
as it ends with error: 
 
db2 update db cfg for <dbname> using LOGARCHMETH2 OFF 
SQL5099N  The value "OFF" indicated by the database 
configuration parameter 
"LOGARCHMETH2" is not valid, reason code "17".  SQLSTATE=08004 
db2 update db cfg for <dbname> using LOGARCHMETH1 USEREXIT 
SQL5099N  The value "USEREXIT" indicated by the database 
configuration 
parameter "LOGARCHMETH1" is not valid, reason code "13". 
SQLSTATE=08004 
 
Currently it is not possible to update LOGARCHMETH2 to OFF 
despite LOGARCHMETH1 conatains a valid setting like USEREXIT and 
you end up a deadlock situation for this special scenario. 
We should allow LOGARCHMETH2 to be turned OFF, while 
LOGARCHMETH1 is not OFF.

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

First fixed in DB2 10.1 Fix Pack 6

not known / see Local fix

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

01.07.2016
02.03.2017
02.03.2017