(ZOS) Fixing storage allocation error caused by DB2 Universal JDBC Driver on z/OS

When using DB2 Universal JDBC type 2 driver on z/OS, the messaging engine fails to start. This is a known issue and can be solved by tuning the JDBC driver.

In the address space of Control Region Adjunct (CRA), we might see text "Storage Allocation Error", for example, in

BBOO0220E: [SB6NLA1:SB6NLA1.server1-SB6NLA1] CWSIP0002E: An internal messaging 
error occurred in com.ibm.ws.sib.processor.impl.MessageProcessor, 1:1469:1.365, 
com.ibm.ws.sib.msgstore.MessageStoreRuntimeException: com.ibm.ws.sib.msgstore.
PersistenceException: CWSIS1501E: The data source has produced an unexpected 
exception: com.ibm.db2.jcc.t2zos.y: [IBM/DB2][T2zos/2.5.48]T2zosPreparedStatement.
readPrepareDescribeOutput_:processDescribeOutput:1563:Storage Allocation Error 
at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.readDataFromPersistence
(AbstractItemLink.java:2487) at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink._
restoreItem(AbstractItemLink.java:639) 

Tasks

1. We can avoid this error by performing one of the following steps:

   1. Set the JDBC driver customer property fullyMaterializeLobData to false. We can do this in the administrative console: Resources > JDBC Providers > Your JDBC provider -> Data sources -> Your data source > Custom properties > fullyMaterializeLobData.

   2. Use the Universal JDBC provider of type 4 driver.

2. Restart the application server.