Support Article
Pega 7.2 update to Pega 7.3.1 fails with an invalid object error
SA-56397
Summary
Pega 7.2 update to Pega 7.3.1 fails with an invalid object error.
Error Messages
_callDDLUtilityUpgrade:
[echo] Call DDL Generation Upgrade Utility...
[echo] your_media_path\Extracted\scripts/lib/xercesImpl.jar;your_media_path\Extracted\scripts/lib/xml-apis.jar;your_media_path\Extracted\scripts/lib/resolver.jar;
[echo] archive_dir: your_media_path\Extracted\scripts/lib
[java] (install) INFO - Initializing properties with default values
[java] (install) INFO - Setting default Entity Value for pega_enable_nologging = true
[java] (install) INFO - Getting database metadata
[java] (install) INFO - Reading views from schema "dbo"
[java] Exception in thread "main" java.lang.RuntimeException: Error during execution of upgrade on platform mssql using schemas Rules, dbo
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1654)
[java] Caused by: com.pega.pegarules.data.ddl.DatabaseException: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr4_rule_vw'.
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:437)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:477)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.saveCurrentSchemaState(SchemaGenerator.java:571)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1476)
[java] Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr4_rule_vw'.
[java] at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216
Steps to Reproduce
Update Pega 7.2 to 7.3.1 using the update bundle.
Root Cause
A defect or configuration issue in the operating environment.
Data schema (that is, DBO in this case) has Views that belong to the Rule schema. These views reference the pr4_rule_vw and pr4_base tables that are not present in the Data schema since they are in Rule schema. Thus, when the engine tries to getTablesDependentonViews, it does not find them in the Data schema. These lingering schema objects are from a prior upgrade from single to split schema where schema clean-up was not implemented correctly.
Resolution
Make the following change to the operating environment:
Drop the views that do not belong to a split schema Pega 7.2 system. The correct set of views are listed below (also displayed in the screenshot).
- dbo.pcv4_assignment_summary
- dbo.pcv4_assignmentwb_summary
- dbo.pcv4_work_history
- Rules.pwbv4_circumstance_duplicates
- Rules.pwbv4_rule_locking
- Rules.pwbv4_rule_overrides
Published July 23, 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.