Skip to main content

Patching the data schema

Suggest edit
Updated on April 12, 2022

Run the script to patch the data schema.

  1. If encryption is enabled on the cluster, enable encryption on the update script by adding the following line to the prconfig.xml file:
    <env name="cluster/encryption/enabled" "value=true" />
    You must enable encryption so that nodes that are created during the update can join the existing encrypted cluster.
  2. If you have not already done so, configure the connection properties. Use your existing data schema name for Use the new rules schema name for If you have an optional customer data schema separate from the Pega data schema, enter the
    # Connection Information
    pega.jdbc.driver.class=database driver class
    pega.database.type=database vendor type
    pega.jdbc.url=URL of the database
    pega.jdbc.username=Deployment user name
    pega.jdbc.password=password rules schema data schema
  3. Open a command prompt, and navigate to the scripts directory.
  4. Run either patch.bat (for Windows) or Linux), passing in the --dataOnly argument and true parameter, for example:
    patch.bat --dataOnly true
Result: Pega Platform writes command-line output to a file in the Pega-image\scripts\logs directory.What to do next: After you patch the data schema, review the post-patch tasks sections to complete the patch. At a minimum, you must reconfigure the application to run using the new rules as described in Reconfiguring the application server and enable rule creation, as described in .
  • Previous topic For Oracle databases only: Granting access to the new rules schema tables
  • Next topic Applying a patch in-place
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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