DB2 - Problembeschreibung
Problem IC99930 | Status: Geschlossen |
Database Restore Fails on pureScale cluster due to insufficient SCA memory on the CF (SQLE_RC_INSUFFICIENT_CA_MEMORY_FOR_SCA) | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users performing a Database Restore on pureScale who have * * large MAX_COORDAGENTS values set. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Decrease dbm cfg parameter MAX_COORDAGENTS to 1000 and try * * the * * restore again. After restore completes return * * MAX_COORDAGENTS * * to the previous value. * * Or * * Upgrade to the latest release. * **************************************************************** | |
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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.03.2014 07.07.2014 07.07.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |