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

PRPC 7.1.6 prweb.war won't deploy in JBoss

SA-2311

Summary



Errors deploying PRPC 7.1.6 prweb.war on JBoss

Error Messages


 
 
15:42:21,750 19830421 [com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource] (ServerService Thread Pool -- 79) Bootstrap datatables schema: pegadata
15:42:21,757 SEVERE [com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource] (ServerService Thread Pool -- 79) Unable to connect to database.  Will only use properties from file.: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
 

Root Cause



The root cause of this problem is software use/operation error.
Specification of the default schema names in the standalone.xml file should match the schema names in the schema.


Resolution



The root cause of this problem is defect/misconfiguration in the PRPC operating environment.  To correct the problem update the standalone.xml file to specify the actual rules and data schema names in use on this system.

From OOTB settings:
<simple name="java:/prconfig/database/databases/PegaRULES/defaultSchema" value="pegarules"/>
<simple name="java:/prconfig/database/databases/PegaDATA/defaultSchema" value="pegadata"/>

To:


<simple name="java:/prconfig/database/databases/PegaRULES/defaultSchema" value="MyRulesSchemaName"/>
<simple name="java:/prconfig/database/databases/PegaDATA/defaultSchema" value="MyDataSchemaName"/>
 

Published January 31, 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