Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Splitting single schema to split schema

SA-3626

Summary



Developer has PRPC 7.1.5 and wants to know how to split the single schema to a new split Schema for data and rules.

Please note that it is not upgrade from lower version, it is a 7.1.5 single schema to split schema conversion.



Resolution



The explanation for this behavior is as follows:


Splitting the schema can be done during an upgrade or after, so you can apply the same steps to your 7.1.5 system.

You do use the upgrade instructions with the following details:

1. Run the migrateSystem script to migrate your updated rules objects from v71update (combined data and rules) to new v71rules schema. The source and target user running the migration should be the deployment user (as outlined in Installation Guide) who has privileges to both schemas. The source and target connection properties (driver, URL, etc.) should be filled in appropriately. The remaining migrateSystem.properties should be set this way:

pega.source.jdbc.username=DeploymentUser
pega.source.rules.schema=v71update
pega.target.jdbc.username=DeploymentUser

pega.target.rules.schema=v71rules
pega.target.data.schema=v71update

pega.move.admin.table=false
pega.clone.generate.xml=true
pega.clone.create.ddl=true
pega.clone.apply.ddl=true
pega.bulkmover.unload.db=true
pega.bulkmover.load.db=true
pega.rules.objects.generate=true
pega.rules.objects.apply=true

2. Post upgrade, follow the instructions in the upgrade guide to cleanup the unused rules tables from your v71update schema.

3. Further details are in the PRPC guides:

https://pdn.pega.com/resources/deployment-guides
 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

50% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us