For Oracle databases only: Granting access to the new rules schema tables
Grant access to link the data and new patch schema.
- With the new rule tables in the patched schema, you must grant access privileges to the user by generating and applying the necessary rules objects DDL (GRANT statements) which are required to link the data and the patch schema. Deployment users use the
migrate.bat
ormigrate.sh
script again for this process, using different, appropriate property settings in themigrateSystem.properties
file. To minimize the time required, run the migration scripts from the same data center as the database server.
-
Use a text editor to edit the
migrateSystem.properties
file in the scripts directory:Pega-image\scripts\migrateSystem.properties
-
Configure the target properties:
pega.target.jdbc.driver.jar=full path/DRIVER.JAR pega.target.jdbc.driver.class=database driver class pega.target.database.type=database vendor type pega.target.jdbc.url=database URL pega.target.jdbc.username=Deployment user name pega.target.jdbc.password=password pega.target.rules.schema=new rules schema name pega.target.data.schema=existing data schema name
-
Configure a temporary directory:
pega.migrate.temp.directory=full path to temporary directory
-
Configure the operations to be performed by the utility as shown below:
pega.clone.generate.xml=false pega.clone.create.ddl=false pega.clone.apply.ddl=false pega.bulkmover.unload.db=false pega.bulkmover.load.db=false pega.rules.objects.generate=true pega.rules.objects.apply=true
-
Save the properties file.
-
Open a command prompt, and navigate to the scripts directory.
-
Type
migrate.bat
or./migrate.sh
to run the script.
Pega Platform writes command-line output to a file in the Pega-image\scripts\logs
directory.