|
Problem IC78853
|
Status: Closed |
RESTORE/CREATE DATABASE FAILS DUE TO LOCK STRUCTURE ALLOCATION TIMEOUT WITH LARGE CF |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
CREATE DATABASE or RESTORE DATABASE may fail due to a timeout
when allocating a lock structure in the CF (Cluster Caching
Facility). This only affects
systems with a large CF (in terms of memory). The following
Severe log message will be written to the log:
2011-09-05-19.45.56.794678+000 E179926A3586 LEVEL:
Severe
PID : 11272286 TID : 21076 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-52 APPID: *N0.db2inst1.110905194532
AUTHID : DB2INST1
EDUID : 21076 EDUNAME: db2agntp 0
FUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for
Cluste, SAL_MANAGEMENT_PORT_HANDLE::SAL_ManagementAllocate,
probe:5595
MESSAGE : CA RC= 2147876878
DATA #1 : String, 43 bytes
CALockAllocate failed with unexpected error
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 9.8 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.8 FixPack 5. *
**************************************************************** |
| Local Fix: |
A workaround is to lower the value for DB2_DATABASE_CF_MEMORY so
that the size of the lock structure is smaller and can be
allocated more quickly. The default value is 100%. Example:
db2set DB2_DATABASE_CF_MEMORY=75 |
| Solution |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.09.2011
15.06.2012
15.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.5
|
 |
