Published Release Notes

Column Populator utility documentation out of date for prior versions

The documentation for using the Column Populator utility to populate newly exposed database columns is out of date for Pega 7 Platform versions prior to 7.2. For all Pega 7 versions, refer to the Pega 7.2 help documentation for instructions about how to use this utility.

Work attachment indexing fails with IBM SDK Java 6

Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.

Child case queries performance can be slow

Some customers have reported that performance is slow when they execute queries on child cases. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.

See Performance improvements for child case queries.

High number of busy waits when using Oracle SecureFiles

You might experience a high number of buffer busy waits when using Oracle SecureFiles for BLOB storage. An Oracle buffer busy wait occurs when a session cannot access a database block in the buffer cache, because another session is either reading the block into the buffer or changing the buffer. As a best practice, use Oracle 11.2.0.4 or later, because earlier versions have more problems with SecureFiles. In addition, to minimize the number of busy waits, set the hidden Oracle parameter _securefiles_concurrency_estimate to 50, and partition the table by using a composite range hash partition that is based on the pxCreateDateTime and pzInskey columns.

For more information, see Troubleshooting: High number of busy waits when using Oracle SecureFiles.

Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules

Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:

• The upgrade fails with the following error message:
  Verify ML Readiness
• The upgrade succeeds, but you might be unable to open changed rule forms.

If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.

This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.

Extract marker file not created at startup

The extract marker file (PegaRULES_Extract_Marker.txt) is not created at startup, because the rule utility libraries no longer need it. If you used to use the extract marker file to clear the static content file-based cache, to look up lists, or to control starting activities with web nodes, you can delete the contents of the PegaRULES temporary directory instead.

System starts slowly after upgrade or update on IBM DB2 for z/OS

Additional tables are added to upgraded and updated systems. If your system starts up very slowly after an upgrade or update, the database statistics on these new tables might not have generated correctly. To correct this issue and improve performance, your database administrator needs to manually rebuild the statistics for all tables in the rules schema.

Clustering equal to none might cause errors

Some Pega 7 Platform features might not work when theidentification/cluster/protocolsetting in the prconfig.xml file is set to none. Some features that might not work are remote tracing and management actions on the node from the Requestor Management and Agent Management landing pages. Setting the clustering protocol to none is not recommended and will not be supported in a future Pega 7 Platform release.

Excessive service invocation count

Apply a hotfix to eliminate excessive service invocations. After upgrades, the service invocation count for Lucene search results might be up to four times greater than before the upgrade. The Pega 7 Platform moved from Lucene to Elasticsearch in Pega 7.1.7.

If any of the following situations apply to your installation, you must apply a hotfix:

• You installed any version prior to Pega 7.1.7 and you do not plan to upgrade at this time.
• You upgraded from any version prior to PRPC 6.3 to any version prior to Pega 7.1.7.
• You upgraded from 7.1.6 or earlier to Pega 7.1.7 or Pega 7.1.8 and you did not change your indexing to Elasticsearch.

The workaround depends on your version:

• For PRPC 6.3 SP1, apply HFix-27840 and HFix-28856.
• For other versions of the Pega 7 Platform, use My Support Portal to request the hotfixes for your system.

Beginning with Pega 7.1.9, the issue has been resolved.

Disregard this startup error for Oracle Weblogic deployments

If you install, upgrade, or update your Oracle Weblogic application server to Pega 7.2.2, disregard the error stack that begins with text similar to the following:

ERROR - WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Oracle WebLogic Server Module Dependencies 12.1 Tue Mar 11 15:35:15 MDT 2014 WebLogic Jersey Server Integration 3.0 Fri Feb 21 10:55:11 UTC 2014 must use JDK 1.8+ with WebSocket
2016-11-07 06:13:01,690 [ WIN-L3EEURCNCP1] [ STANDARD] (pr.DefaultAsyncSupportResolver) ERROR - Real error: Unable to configure jsr356 at that stage. ServerContainer is null

This message appears because the Pega 7.2.2 real-time notification feature initially tries to use WebSocket and then falls back to long polling. The Pega 7 Platform does not support WebSocket for Oracle Weblogic servers, and instead uses long polling for real-time notifications.