Support Article

Pega 7.2.2.application fails after upgrade

SA-34271

Summary



Pega application fails after Pega 7.2.2 new installation with .ear with Pega 7.2.2 plan.xml


Error Messages

com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource
SEVERE: Unable to connect to database. Will only use properties from file.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr_data_admin'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)


Steps to Reproduce



Install .ear with Pega 7.2.2 plan.xml.


Root Cause



An issue in the custom application code or rules.

On verifying the user's plan.xml with Out-of-the-box (OOTB) plan.xml, it is found that schema name and rules name value was not provided in proper syntax.

Resolution



Perform the following local-change step:

Updating plan.xml with “defaultDataSchema” and “defaultRulesSchema” name resolves the issue.


Published February 27, 2017 - Updated March 14, 2017

Have a question? Get answers now.

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