home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC99951 Status: Closed

Database Restore Fails on pureScale cluster due to insufficient SCA memory
on the CF (SQLE_RC_INSUFFICIENT_CA_MEMORY_FOR_SCA)

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Database Restore Fails on pureScale cluster due to insufficient 
SCA memory on the CF (SQLE_RC_INSUFFICIENT_CA_MEMORY_FOR_SCA) 
 
2013-02-14-13.44.32.401865-300 I24908560A592        LEVEL: Error 
PID     : 17170518             TID  : 43945         PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000         DB   : 
TESTDB 
APPHDL  : 0-307                APPID: *N0.db2inst1.130214184328 
AUTHID  : db2inst1 
EDUID   : 43945                EDUNAME: db2agent (TESTDB) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqleReallocateCFStructuresForRestore, probe:3596 
MESSAGE : 
ZRC=0x87050175=-2029715083=SQLE_RC_INSUFFICIENT_CA_MEMORY_FOR_SC 
A 
          "Insufficient memory available in CF to satisfy 
allocation request for the SCA" 
 
2013-02-14-13.44.32.414073-300 E24909153A569        LEVEL: 
Severe 
PID     : 17170518             TID  : 43945         PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000         DB   : 
TESTDB 
APPHDL  : 0-307                APPID: *N0.db2inst1.130214184328 
AUTHID  : db2inst1 
EDUID   : 43945                EDUNAME: db2agent (TESTDB) 0 
FUNCTION: DB2 UDB, database utilities, sqludProcessSingleLFH, 
probe:1745 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-2038 
DATA #2 : Hexdump, 0 bytes 
Object not dumped: Address: 0x078000007E26A848 Size: 0 Reason: 
Zero-length data 
 
2013-02-14-13.44.32.423879-300 E24909723A917        LEVEL: 
Severe 
PID     : 17170518             TID  : 43945         PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000         DB   : 
TESTDB 
APPHDL  : 0-307                APPID: *N0.db2inst1.130214184328 
AUTHID  : db2inst1 
EDUID   : 43945                EDUNAME: db2agent (TESTDB) 0 
FUNCTION: DB2 UDB, database utilities, sqludProcessSingleLFH, 
probe:1745 
MESSAGE : SQL2038N  A database system error "" occurred during 
processing. 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2038   sqlerrml: 
10 
 sqlerrmc: 0x87050175 
 sqlerrp : sqludPro 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2013-02-14-13.44.32.452950-300 E24910641A428        LEVEL: 
Severe 
PID     : 17170518             TID  : 43945         PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000         DB   : 
TESTDB 
APPHDL  : 0-307                APPID: *N0.db2inst1.130214184328 
AUTHID  : db2inst1 
EDUID   : 43945                EDUNAME: db2agent (TESTDB) 0 
FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:798 
MESSAGE : Restore Terminated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Database Restore Fails on pureScale cluster due to           * 
* insufficient SCA memory on the CF                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgraded to  DB2 LUW version 10.5fp3                         * 
****************************************************************
Local Fix:
Decrease dbm cfg parameter MAX_COORDAGENTS to 1000 and try the 
restore again.  After restore completes return MAX_COORDAGENTS 
to the previous value.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
This issue is fixed in DB2 LUW version 10.5fp3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2014
15.09.2014
15.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList