Close popover

Table of Contents

Patching systems without downtime (Pega 8.3 and earlier)

The Pega patch process is zero-downtime when you use the out-of-place process so you can continue working in your application while you patch your system.

For releases 8.2.x and 8.3.x, patches rely on the following three schemas:

  • Data schema – your existing data schema. This will be your data schema after the patch as well.
  • Rules schema – your existing rules schema. This schema will be replaced after the patch.
  • New rules schema – a schema on the same database you create for staging the patch. This will become the new rules schema.

Clients apply patches by completing the following steps:

  1. Prepare the cluster for the patch by configuring the high availability cluster settings.
  2. Create a new blank rules schema in your existing database.

  3. Migrate only the rules from the existing rules schema to the new rules schema.

  4. Patch the new rules schema.

  5. For Oracle databases, you must grant access to the new rules schema tables by using migrate.sh again to generate the necessary rules objects (GRANT statements) which will link the data schema to the new rules schema after you patch the new rules schema.
  6. Patch the data schema.

  7. Using a database editing tool, delete the old rules schema from your database and clean up unused temporary data tables in your new rules schemas.

Suggest Edit

Have a question? Get answers now.

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