Skip to main content

Support Article

How can you generate ddl for migrate script?

SA-13405

Summary



When rules are migrated from PRPC 6.3 SP1 to Pega 7.1.8 split schema, the new database using migrate.sh, the tables are mapped to an incorrect tablespace.

Resolution



Perform the following local-change: 

Migrate steps are done in two steps:
 
  1. Run migrate.sh with the following in migrateSystem.properties to generate the DDL to clone the tables in the new rules schema.
 
######## The operations to be run by the utility, they will only be run if the property is set to true.
#Set to true if migrating before an upgrade. If true admin table(s) required
#for an upgrade will be migrated with the rules tables.
pega.move.admin.table=true
#Generate an xml document containing the definitions of tables in the source system. It will be found in the schema directory of the
#distribution image.
pega.clone.generate.xml=true
#Create ddl from the generated xml document. This ddl can be used to create copies of rule tables found on the source system.
pega.clone.create.ddl=true
#Apply the generated clone ddl to the target system.
pega.clone.apply.ddl=false
#Unload the rows from the rules tables on the source system into the pega.bulkmover.directory.
pega.bulkmover.unload.db=false
#Load the rows onto the target system from the pega.bulkmover.directory.
pega.bulkmover.load.db=false
 
  1. Once the DBA applies the DDL, run migrate.sh again with the following in migrateSystem.properties to populate the cloned tables.
 
######## The operations to be run by the utility, they will only be run if the property is set to true.
#Set to true if migrating before an upgrade. If true admin table(s) required
#for an upgrade will be migrated with the rules tables.
pega.move.admin.table=true
#Generate an xml document containing the definitions of tables in the source system. It will be found in the schema directory of the
#distribution image.
pega.clone.generate.xml=false
#Create ddl from the generated xml document. This ddl can be used to create copies of rule tables found on the source system.
pega.clone.create.ddl=false
#Apply the generated clone ddl to the target system.
pega.clone.apply.ddl=false
#Unload the rows from the rules tables on the source system into the pega.bulkmover.directory.
pega.bulkmover.unload.db=true
#Load the rows onto the target system from the pega.bulkmover.directory.
pega.bulkmover.load.db=true

 



 
Suggest Edit

Published August 27, 2015 - Updated October 8, 2020

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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