Generated DDLs shows all tables related to Rules Schema as well as Data Schema. Is this correct?
Hi,
We're upgrading our application from PRPC 6.2 SP2 to 7.2.2. and following Appendix:C Optional Generating and Applying DDL from Command Line. As part of Step 2 a. Created DDL of changes of Rules Schema.
We've edited setupDatabase.properties file to set the rules and data schema names:
One database:
pega.rules.schema=new rules schema name
pega.data.schema=new rules schema name
However after running of generateddl.sh, Build was successful and DDLs generated into /opt/prpc/pega_software/pega722/schema/generated/oracledate/upgrade directory. While reviewing the statements, found that this script has created all tables related to Rules and Data Schema. Is this correct? Or we need to change pega.data.schema=new Data Schema name? We just followed as per the Pega 7.2.2. Upgrade Guide page no.135.
We need to apply DDLs as per next step, but before that would like to know is it correct to have all tables in new Rules Schema, may be later steps like 3 a would take care of migrating the tables created related to data to new Data schema.
Would appreciate quick response on this. Thanks.
Accepted Solution
Pegasystems Inc.
IN
If you are running the generateDDL script after migration is completed then it should generate delta schema changes for all the rule tables and for all the data tables it should generated create statements.
These generated data tables will be cleanedup using optimize schema wizard after Data Upgrade is completed.