Patching the data schema
Run the script to patch the data schema.
- If encryption is enabled on the cluster, enable encryption on the update script by
adding the following line to the
prconfig.xmlfile:<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. - If you have not already done so, configure the connection properties. Use your existing
data schema name for data.schema.name. Use the new rules schema
name for rules.schema.name. If you have an optional customer data
schema separate from the Pega data schema, enter the
customerdata.schema.name.
# Connection Information pega.jdbc.driver.jar=/path-to-the-database-JAR-file/DRIVER.jar 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.name=new rules schema data.schema.name=existing data schema customerdata.schema.name=optional-customer-data-schema - Open a command prompt, and navigate to the scripts directory.
-
Run either
patch.bat(for Windows) orpatch.sh(for Linux), passing in the --dataOnly argument and true parameter, for example:patch.bat --dataOnly true
Pega-image\scripts\logs
directory.Previous topic For Oracle databases only: Granting access to the new rules schema tables Next topic Applying a patch in-place