SA-32375

Summary

Upgraded to Pega 7.2 split schema.  

​Trying to start the system and it is failing because the column PYCLUSTERADDRESS is not available in the data schema table pr_sys_statusnodes.

The table is also missing some additional columns that should have been added as part of the upgrade.

Error Messages

Caused by SQL Problems.
Problem #1, SQLState 42703, Error code -206: com.ibm.db2.jcc.am.SqlSyntaxErrorException: "PYCLUSTERADDRESS" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.19.56
Problem #2, SQLState 56098, Error code -727: com.ibm.db2.jcc.am.SqlException: An error occurred during implicit system action type "2". Information returned for the error includes SQLCODE "-206", SQLSTATE "42703" and message tokens "PYCLUSTERADDRESS".. SQLCODE=-727, SQLSTATE=56098, DRIVER=4.19.56
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:262)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6519)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6932)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6885)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6865)
at com.pega.pegarules.cluster.internal.PRClusterImpl.getPRSysStatusNodesInformation(PRClusterImpl.java:485)
... 68 more

Steps to Reproduce

Use command line upgrade scripts to perform the upgrade from PRPC 6.3 to Pega 7.2.

Root Cause

Refer to the product documentation:  https://pdn.pega.com/documents/pega-722-platform-upgrade-guide

In the sections that refer to upgrading the rules and data schemas from the command line the property names in the guide incorrectly list the properties to identify the rules and data schema names in the setupDatabase.properties file as pega.rules.schema and pega.data.schema instead of rules.schema.name and data.schema.name.  
For the rules schema upgrade the correct property names, as specified in the setupDatabase.properties file were used.  

​For the data schema upgrade the rules.schema.name property was specified correctly but the data.schema.name property was not.  

​As a result the data schema was not updated correctly.

Resolution

Perform the following local-change: 

Rerun the upgrade of the data schema specifying both the rules.schema.name and data.schema.name properties in the setupDatabase.properties file.