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

Application does not boot post WebLogic upgrade



Post WebLogic upgrade, on restarting the Pega application after deployment, unable to access the application and an error occurs on booting the Application server.

Error Messages

[fault (self-tuning)'] [ ] [ ] [ ] ( ERROR   - Unable to obtain DataSource for pegadata; javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AdminPegaRules'. Resolved 'jdbc'; remaining name 'AdminPegaRules'
[fault (self-tuning)'] [ ] [ ] [ ] (dbms.JdbcConnectionManagerImpl) ERROR   - Failed to read Data-Admin-DB-Name Definitions: Database-BadDBDef-Missing    Unable to obtain DataSource object
[fault (self-tuning)'] [ ] [ ] [ ] (ervlet.WebAppLifeCycleListener) ERROR   - Exception during startup processing Error determining the mode of PRPC install from database.

Steps to Reproduce

  1. Upgrade WebLogic to WebLogic
  2. Deploy the application.
  3. Restart the application.

Root Cause

When WebLogic was upgraded, the JNDI name associated with the data source changed. The plan.xml displayed the JNDI name incorrectly.


Edit the plan.xml to have the correct data source JNDI name associated with the PegaRULES and PegaDATA data sources.

Published April 14, 2020 - Updated December 2, 2021

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