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

Production Nodes Cant Connect to Database

SA-27070

Summary



Environment has 54 Nodes, and 8 Nodes are currently down/non-startable. NOTE that existing environment is fine as long as they dont shutdown anything.


Error Messages



The WebSphere stdout log contains the following message:


============ PegaRULES Bootstrap Configuration ============
Date: Mon Aug 08 01:36:05 BST 2016
Java Version: IBM Corporation 1.6.0
Configuration: wsjar:file:<filepath>
Pega-EngineCode: <none specified>
JNDI Reference: java:comp/env/jdbc/PegaRULES
Database: DB2 DSN10015
Driver: IBM DB2 JDBC Universal Driver Architecture 3.62.73

(!) Unable to use given database configuration
(!) Unable to locate classes on filesystem
=============== End Bootstrap Configuration ===============

[8/8/16 1:36:05:920 BST] 0000000a PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Error initializing PRAppLoader
java.lang.ClassNotFoundException: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
at com.pega.pegarules.internal.bootstrap.PRMiniLoader.loadClass(PRMiniLoader.java:365)
at java.lang.ClassLoader.loadClass(ClassLoader.java:626)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:589)
...


Steps to Reproduce



To reproduce, just shutdown a node. The node will not restart.


Root Cause



The JDBC configuration, custom property setting was missing

Resolution



The following custom property as per the installation guide was missing in the environment:

Name: currentSchema Value: <user schema name>

Name: currentFunctionPath Value: SYSIBM, SYSFUN,<user schema name>
Name: fullyMaterializeLobData Value: true
Name: fullyMaterializeInputStreams Value: true
Name: progressiveStreaming Value: 2
Name: progressiveLocators Value: 2
Name: webSphereDefaultIsolationLevel Value: 2

Once the details were entered the system became responsive and was able to be restarted.

 

Published September 9, 2016 - 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