Skip to main content


For Oracle databases only running Pega Platform versions earlier than 8.4: Granting access to the new rules schema tables

Suggest edit Updated on September 29, 2021

Grant access to link the data and new patch schema required for Oracle databases running Pega Platform version prior to 8.4.

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 or script again for this process, using different, appropriate property settings in the file. To minimize the time required, run the migration scripts from the same data center as the database server.

Note: Pega strongly recommends that you use the Pega-provided migration script. The use of vendor tools to manage this step is not recommended, since there are additional manual steps required to migrate the schema, not documented here, if you do not use the migrate script.
  1. Use a text editor to edit the file in the scripts directory:
  2. Configure the target properties: path/DRIVER.JAR driver class vendor type URL user name rules schema name data schema name
    Note: If is blank, the rules schema is used by default.
  3. Configure a temporary directory: path to temporary directory
  4. Configure the operations to be performed by the utility as shown below:
  5. Save the properties file.
  6. Open a command prompt, and navigate to the scripts directory.
  7. Type migrate.bat or ./ to run the script.

Pega Platform writes command-line output to a file in the Pega-image\scripts\logs directory.

Did you find this content helpful? YesNo

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us