Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DB exception in logs when starting JVM

SA-9111

Summary



You are using DB2. When you start the application, you get the below error in the application server logs.

Error Messages



There was a problem getting a list -904 57011 DB2 SQL Error: SQLCODE=-904, SQLSTATE=57011, SQLERRMC=00C90096;00000302;D3643PPC.PGTSP084.X'00419D', DRIVER=3.64.133

Caused by SQL Problems.
Problem #1, SQLState 57011, Error code -904: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-904, SQLSTATE=57011, SQLERRMC=00C90096;00000302;D3643PPC.PGTSP084.X'00419D', DRIVER=3.64.133

Caused by:
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-904, SQLSTATE=57011, SQLERRMC=00C90096;00000302;D3643PPC.PGTSP084.X'00419D', DRIVER=3.64.133


Steps to Reproduce



1) Start the JVM.

Root Cause



The root cause of this problem is defect/misconfiguration in the DB2/zOS. The root cause is environmental (DB2/zOS). The following is a detailed explanation of the ERROR code from IBM knowledge center (http://www-01.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/com.ibm.db2z10.doc.codes/src/tpc/n904.dita )
 

Resolution




Please contact your DB2 for z/OS system programmer and ensure that the following ZPARM values have been evaluated:
 
Pegasystems recommends the following ZPARM settings for any DB2 subsystem
  • NUMLKTS=5000 (Minimum)
  • NUMLKUS=30000 (Minimum)

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us