Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Dec 1, 2017
Last activity: Dec 5, 2017
Posted: 1 Dec 2017 8:12 EST
Last activity: 5 Dec 2017 8:18 EST
Closed
Solved

Upgrade from 718 to 731,Database-NonexistentTable error followed by upgrade failure.

Hi Team,

While trying to upgrade from 718 to 731,we are observing the below mentioned error and the upgrade is getting failed.

We dont have a table by name PEGA_RULES.pr4_rule_service_rest in any of our environments but not sure why the upgrade script has been trying to upgrade a non-existent table and getting failed.

[java] Nov 29, 2017 11:08:57 AM com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable PEGA_RULES.pr4_rule_service_rest PegaRULES
[java] From: (unknown)

***Edited by Moderator Marissa to add SR Details***

To see attachments, please log in.
Installation and Deployment
Support Case Exists

Accepted Solution

Posted: 7 years ago
Posted: 5 Dec 2017 8:05 EST
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

 The bypass.pega.schema property has been set to true but the schema changes needed for the upgrade have not been generated and manually applied.

Show More

 The bypass.pega.schema property has been set to true but the schema changes needed for the upgrade have not been generated and manually applied.

To have the upgrade generate and apply the schema changes needed remove the =true from the bypass.pega.schema property in the setupDatabase.properties file and then resume the upgrade.
# Generate schema will be skipped if this property is set to true
# Note: Leave this property blank if you need to generate the schema
bypass.pega.schema


Show Less
To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 5 Dec 2017 8:05 EST
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

 The bypass.pega.schema property has been set to true but the schema changes needed for the upgrade have not been generated and manually applied.

Show More

 The bypass.pega.schema property has been set to true but the schema changes needed for the upgrade have not been generated and manually applied.

To have the upgrade generate and apply the schema changes needed remove the =true from the bypass.pega.schema property in the setupDatabase.properties file and then resume the upgrade.
# Generate schema will be skipped if this property is set to true
# Note: Leave this property blank if you need to generate the schema
bypass.pega.schema


Show Less
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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