Issue with CMOD 9.0 with DB2 V10

[ali.arsiwala]

Hi Everyone,
We are trying to install CMOD9.0 with DB2V10 and we hit a brick wall and believe that CMOD9.0 has a bug where it tries to use DB2 configuration parameter that has been discontinued in DB2V10.
This is the error we get when running arsdb:
ARS4070E Unable to update the ARCHIVE database configuration.  SQLCODE = -1597

Here's what I found for the SQLCODE 1597:
SQL1597N Configuring the DB2 environment failed
because the specified DB2 configuration
parameter is discontinued.
Explanation: The LOGRETAIN and USEREXIT
database configuration parameters have been
discontinued.
Log retention and the use of user exit programs to
archive and retrieve the files are still supported. To
configure a database to use log retention and user exit
programs, you should use the LOGARCHMETH1
database configuration parameter.
User response: To enable log retention, set the
LOGARCHMETH1 database configuration parameter to
LOGRETAIN.
To enable log retention and identify that a user exit
program should be used to archive and retrieve the log
files, set the LOGARCHMETH1 database configuration
parameter to USEREXIT.


Has anyone else encountered this issue yet? I am going to raise a PMR with IBM. We had to do a work around for the above by installing CMOD9.0 on DB2V9.7 first and then upgrading DB2 to V10.

Thanks
Ali.

[ali.arsiwala]

FYI, IBM have recognised this as a bug in CMOD V9.0. Here's what they have said:

"yes this looks like a bug.

The LOGRETAIN and USEREXIT database configuration parameters have been discontinued.
This parameter has been replaced with logarchmeth1, the primary log archive method configuration parameter. To retain active log files for rollforward recovery, set logarchmeth1 to LOGRETAIN by issuing the command UPDATE DB CFG USING logarchmeth1 LOGRETAIN. logarchmeth2 must be set to OFF.

This will be escalated to product management."

[Justin Derrick]

Thanks for keeping up updated Ali!

-JD.

[ali.arsiwala]

No problems at all.

IBM have finally tested a work around in their labs and have provided the following steps until a fix pack is released for CMOD 9.0 to work with DB2 V10.

1. Installed DB2 V10 (64bit) and CMOD V9.
2. Created instance and got DB2 error in db2diag:
2012-12-06-01.31.53.166000+480 I98083F658           LEVEL: Error
PID     : 348                  TID : 7768           PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-7                  APPID: *LOCAL.DB2.121205172630
AUTHID  : ADMINISTRATOR        HOSTNAME: p85x
EDUID   : 7768                 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, config/install, sqlfUpdateDbCfg, probe:90
MESSAGE : ZRC=0xFFFFF9C3=-1597
         SQL1597N  Configuring the DB2 environment failed because the specified DB2 configuration parameter is discontinued.

3. Create empty ARCHIVE database, run ARSDB command manually: arsdb ?rtv.
4. Manually initialized CMOD system functions (http://pic.dhe.ibm.com/infocenter/cmod/v9r0m0/topic/com.ibm.ondemand.installingmp.doc/ars1i071673.htm?path=2_0_7_7_9#prnodb_dbcrintwin):
4.1 Initializing the system log: arssyscr -I archive -l
4.2 Initializing the system load:  arssyscr -I archive -a
4.3 Initializing the system migration:  arssyscr -I archive -m
5. Start CMOD instance. Test all the function are working properly.
6. Backup DB2 database, configure the archive logging manually with DB2?s method.