Related content:

Question Migrate.sh stuck for the last 2 hours Discussion Caught exception "PegaBulkMover:: SQLException loading database" while running migrate.sh Question Unable to load driver class while executing migrate.sh Question Generating Rule schema objects migrate.sh failing from 5.5 to 7.1.9 Discussion Generating Rules Schema Objects Stalled (migrate.sh) Question Does ML for PRPC7.1 from 5 to 9 update data schema? Question Is PR_ASSEMBLEDCLASSES expected to be migrated when migrate.sh is executed (pre-upgrade)? Question java.lang.IllegalArgumentException: Unable to load the connection properties file while running migrate.sh file Question can we run containers hitting a split schema? Question Getting error while running migrate.sh file - part of upgrade from 6.2 version to 7.3
Contact a Moderator

Question

3
Replies
117
Views
BrettAllen Member since 2015 7 posts
PEGA
Posted: 3 years ago
Last activity: 3 years 4 months ago
Closed
Solved

Is there a way to use migrate.sh for the data schema?

We did an upgrade from Pega 5.5 to 7.2, which involved splitting the schema. We'd like to migrate the tables associated with the data schema from our old single schema name "pega" to a more standard name "data", for consistency with higher level environments that will be installed from scratch.

Is there any way to use migrate.sh on the data schema for a 7.x DB rather than having a DBA do it?

Thanks

***Moderator Edit: Vidyaranjan | Updated Categories***

Data Integration System Administration
Close popover
Moderation Team has archived post
Posted: 3 years ago

Is the data schema (as you mentioned) is of your previous 5.5 or latest 7.2?

Accepted Solution
Posted: 3 years ago

The migrate.sh script only migrates rules tables to the new schema.  If you want to change the name of what will be your data schema in 7.x I would have DBA migrate the schema to the new name before you begin the upgrade to a split schema.

Posted: 3 years ago

Thanks...we ultimately just went with a standard export/import.  The schema references in the stored procedures, views, and the custom type needed an update but that was simple.
Share this page LinkedIn
Copied!