Discussion
Rule upgrade is failing saying object is already existing
Hi,
Customer is doing an upgrade from 6.2 SP1 to Pega 7.1.8 in Oracle environment.
This was an in-place upgrade, considering it as a Oracle DB having synonyms so proceeding with the in-place upgrade.
When the schema change scripts were being generated during the upgrade process, in the initial rules upgrade run itself, it failed stating the DB Index object is already existing.
The customer application has renamed the Pga shipped DB objects to different names / suffixes.
A synonym user is created and this synonym user / schema is configured in the application server.
Please suggest how to proceed further.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Renaming Pega shipped DB objects is not a best practice.
Can you revert the changes so that indexes have original names ?
If customer is renamed the OOTB shipped DB indexes then while generating the DDL for upgrades generateDDL utility identifies that index does not exists and generated the respective create index statement.
So this will cause the index alredy exists issue while applying the generated schema. Plese ask customer to rename the indexes to OOTB index names and proceed with the upgrade.