DSNB306I csect-name THE REQUESTED LENGTH OF THE LOCAL CACHE VECTOR COULD NOT BE ALLOCATED FOR GROUP BUFFER POOL gbpname REQUESTED LENGTH = length1 ALLOCATED LENGTH = length2

Explanation

Db2 connected to the group buffer pool indicated by gbpname, but the MVS Cross-system Extended Services (XES) component could not allocate the requested size of the local cache vector (LCV) in the hardware system area (HSA). Db2 requires an LCV size that is large enough to handle all pages in the member's buffer pool.

length1 indicates the LCV size (in number of bits) that Db2 requested. length2 indicates the LCV size (in number of bits) that XES was able to allocate.

To prevent flooding the operator console, this message is only issued once per Db2 member per group buffer pool until the condition is corrected.

System action

Db2 disconnects from the GBP and issues message DSNB301E with reason code 00C20208, if it has not yet been issued.

SQLCODE -904 is returned to the user with a reason code of 00C20208.

System programmer response

There is not enough HSA storage on the processor to support the size of the local cache vector. The details of HSA allocation are machine-dependent and are defined by the hardware. To correct this problem, take one or both of the following actions:
  • Consult the documentation for your processor hardware to determine if the HSA storage allocation can be increased, and if so, how to do it.
  • Modify the software configuration in your parallel sysplex to reduce the number or size of the vectors that are in use by other coupling facility structure users. Consider the following possible solutions:
    • Use the Db2 ALTER BUFFERPOOL command to reduce the size of this local buffer pool. This means that you might have to reduce the size of the virtual pool.
    • Use the Db2 ALTER BUFFERPOOL command to reduce the size of another local buffer pool that is already connected to a group buffer pool. This means that you might have to reduce the size of the virtual pool. If you make a connected buffer pool smaller, Db2 can usually contract the size of the corresponding LCV dynamically, making HSA storage available. However, Db2 cannot always do the dynamic LCV contraction. In cases where Db2 cannot dynamically contract the LCV size, you can use the Db2 ALTER BUFFERPOOL command to either force a deallocation of the LCV or to force a contraction of the LCV as follows:
      1. Redefine the virtual pool to be smaller than the original size.
      2. Take one of the following actions:
        1. Make the virtual pool very small (perhaps 50 pages or less). Making the virtual pool sufficiently small should let Db2 dynamically contract the LCV, or
        2. Delete the virtual pool to let Db2 disconnect from the group buffer pool. This frees the entire LCV associated with that member's connection to that group buffer pool.
    • Consolidate your group buffer pool-dependent page sets into fewer buffer pools to reduce the number of group buffer pool connections.
    • Consult the documentation for the other software components that might be using a coupling facility cache or list structure with an associated LCV to determine whether it is possible to either delete the connection or to reduce the size of the LCV associated with the connection.