Question

30
Replies
671
Views
Close popover
Mohamed Raffie Sheik Ameer (RAFFIE)
Trident Consulting
Lead System Architect
Trident Consulting
US
RAFFIE Member since 2012 8 posts
Trident Consulting
Posted: August 29, 2016
Last activity: April 6, 2018
Closed
Solved

While generating DDL for Pega7.2, i am unable to see rules schema in the system generated DDL file.

Hello,

I am upgrading my 6.1 SP2 application to Pega 7.2. As per our company policy, i cant use UI tool to update DB.

The DDL has to be generated and our DBA review the standards before executing this in our DB. When performing this, i see only my data schema name in the DDL. no where in the .sql file i see rules schema. Can someone help me on this?

sample migrateSystem.properties attached below.

#The system where the tables/rules will be migrated from
pega.source.jdbc.driver.jar=C:\DB2\db2jcc.jar;C:\DB2\db2jcc_license_cisuz.jar
pega.source.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver
pega.source.database.type=udb
pega.target.jdbc.url=jdbc:db2://XXXX:60005/PRPC:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;
pega.source.jdbc.username=username
pega.source.jdbc.password=password
#Custom connection properties
#pega.source.jdbc.custom.connection.properties=

pega.source.rules.schema=GQDBA
#Set the following property if the source system already contains a split schema.
pega.source.data.schema=

#The system where the tables/rules will be migrated to
pega.target.jdbc.driver.jar=C:\DB2\db2jcc.jar;C:\DB2\db2jcc_license_cisuz.jar
pega.target.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver
pega.target.database.type=udb
pega.target.jdbc.url=jdbc:db2://XXXX/PRPC:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;
pega.target.jdbc.username=username
pega.target.jdbc.password=password
#Custom connection properties
#pega.target.jdbc.custom.connection.properties=

pega.target.rules.schema=GQRULES
#Used to correctly schema qualify tables in stored procedures, views and triggers.
#This property is not required if migrating before performing an upgrade.
pega.target.data.schema=

#Set this property to bypass udf generation on the target system.
#pega.target.bypass.udf

#The location of the db2zos site specific properties file. Only used if the target system is a db2zos database.
pega.target.zos.properties=config/db2zos/DB2SiteDependent.properties

#The commit count to use when loading database tables
db.load.commit.rate=100

################### Migrate System Properties ###########################################
#The directory where output from the bulk mover will be stored. This directory will be cleared when pega.bulkmover.unload.db is run.
#This property must be set if either pega.bulkmover.unload.db or pega.bulkmover.load.db is set to true.
pega.bulkmover.directory=

#The location where a temporary directory will be created for use by the migrate system utilities.
pega.migrate.temp.directory=C:\AIG\PRPC7.2\temp

**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.

System Administration Upgrades
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.