DB2 FOR LUW / DB2FORLUW / 970 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fixpack 10                        * 
****************************************************************

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

Problem was first fixed in DB2 version 9.7 fixpack 10

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

11.03.2014
14.11.2014
14.11.2014

9.7.FP10