DB2 - Problem description
Problem IC99990 | Status: Closed |
FIRST DATABASE ACTIVATION AFTER FIXPACK UPGRADE ON DPF ENVIRONMENT MAY RESULT IN SQL1497W | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The problem occurs on DPF databases that have been upgraded from down level fixpack, and the first action after upgrade is database activation. Once you hit this problem, the ACTIVATE DB <db_name> statement returns warning: SQL1497W Activate/Deactivate database was successful, however, an error occurred on some nodes. After first failing activation, subsequent attempts are successful. Once you hit this problem, you might find in db2diag.log at DIAGLEVEL 4 following entries: 2013-12-05-10.36.02.886855-300 E4608A496 LEVEL: Info PID : 41615610 TID : 2829 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : SAMPLE APPHDL : 0-51 APPID: *N0.db2inst1.131205153551 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agntp (SAMPLE) 1 FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:4550 DATA #1 : <preformatted> Catalog Node cannot perform log sync. SQLCODE -952, sqlerrp SQLEKPDB 2013-12-05-10.36.02.889642-300 I6088A544 LEVEL: Warning PID : 41615610 TID : 2829 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : SAMPLE APPHDL : 0-51 APPID: *N0.db2inst1.131205153551 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (idle) 1 FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppSecondaryStartUsing, probe:611 DATA #1 : <preformatted> Agent executing rqst type = 0x8000001e; acbInfo = 0x10042; app_status = 0x8a; sqlcode = -952 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DPF * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7 fixpack 10 * **************************************************************** | |
Local Fix: | |
To workaround the problem you might consider: - execute ACTIVATE DB <db_name> statement once more - execute CONNECT TO <db_name> statement instead of ACTIVATE DB statement - execute db2updv97 command before ACTIVATE DB <db_name> statement | |
Solution | |
Problem was first fixed in DB2 version 9.7 fixpack 10 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.03.2014 14.11.2014 14.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |