Migration failed : records explicitly mapped to schema
Migration failed with the following error :
The following Data-Admin-DB-Table records are explicitly mapped to a schema
What can be the resolution ?
**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.
Pegasystems Inc.
IN
This error is because declare indexes in rule tables were mapped in a different schema. This is currently not supported during split schema upgrade. PRPC migration script expects all the rule table related indexes to be in the same schema as that of rules.Hence this error can be fixed by moving the table mapped to the index into the rule schema and remapping the Data-Admin-DB-Table record to remove hardcoded schema name