Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8
Valid from Pega Version 4.1
When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.
- Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the page.
- Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
- Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
--action preupgrade
--dataschema
<data schema name>--oldrulesschema
<old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>--newrulesschema
<new rules schema name>--automaticddl
<Optional. Set to true to automatically apply the disable trigger SQL scripts.>For example:
fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false
- If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
- Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.
Rule revalidation after updating properties without restarting nodes
Valid from Pega Version 8.2
When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.
For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.
For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.
Changes in JSON results when checking the health of your system
Valid from Pega Version 8.2
Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.
JSON results for pre-Pega Platform 8.2:
{ "duration":"3954.448601", "count":"0" }
JSON results for Pega Platform 8.2 and later:
{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.