Support Article
Not able to start the server/application after upgrade
SA-45035
Summary
After upgrade from PRPC 6.1 to Pega 7.2.2 split schema on Websphere application server startup of the system fails.
Error Messages
2017-09-25 17:11:13,764 [ server.startup : 2] [ ] [ ] [ ] ( basic.config.SettingsImpl) ERROR - Unable to connect to database. Will only use properties from file.
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:225)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:53)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:774)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:925)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1111)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:4845)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1501)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuery(WSJdbcPreparedStatement.java:1112)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:714)
at com.pega.pegarules.internal.bootstrap.SettingReaderDB.getAllClassificationSettingsDB(SettingReaderDB.java:87)
at com.pega.pegarules.internal.bootstrap.SettingReaderDB.getSettingsDB(SettingReaderDB.java:154)
at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.getConfigSettingsFromDB(SettingsImpl.java:492)
at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.initialize(SettingsImpl.java:309)
at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.<init>(SettingsImpl.java:232)
at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.<clinit>(SettingsImpl.java:235)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at com.pega.pegarules.exec.internal.PRExecProviderImpl.getSettings(PRExecProviderImpl.java:628)
at com.pega.pegarules.exec.internal.PRExecProviderImpl.initialize(PRExecProviderImpl.java:366)
at com.pega.pegarules.common.PREngineProvider.<clinit>(PREngineProvider.java:172)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
Steps to Reproduce
Upgrade to split schema on Pega 7.2.2
Root Cause
A defect or configuration issue in the operating environment:
The namespace bindings which specify the default PegaRULES and PegaDATA schemas are not getting picked up by the startup.
Resolution
Make the following change to the operating environment:
Change the scope of the namespace bindings to be server as specified in the deployment guide.
See the "Creating binding identifiers" section of the Platform Installation Guide for IBM WebSphere and Oracle
https://pdn.pega.com/documents/pega-722-platform-installation-guide-ibm-websphere-and-oracle
Published February 20, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.