Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

Database

Valid from Pega Version 7.1.4

Improvements to data handling were made for search indexing, agent processing, and filtering.  Scripts were provided for proper population of the database tables.

 

  • Importing data from shared obj-external tables is now supported.
  • A validation warning will now display when an unexposed property is used in filter or join conditions.
  • A Global Search index may now be created across two databases.
  • Agent processing on multiple nodes has been improved.
  • Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
  • Filtering functionality involving special characters has been enhanced.
  • Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.

System Management

Valid from Pega Version 7.1.4

Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.

  • A script was created to run the data schema upgrade for z/OS systems.
  • In a split-schema configuration, indexing has been enhanced.
  • The product installer has been enhanced.
  • The stand-alone Static Assembly Utility does not require a password for its process.
  • The UpdateManager tool has been improved.

System Management

Valid from Pega Version 7.1.3

The PRPC installer has been enhanced to handle additional error conditions related to partial installs and duplicate keys; additionally, the hotfix rollback feature has been improved, and the Rulebase compare tool now supports HTTP(S) environments.

  • Rollback feature has been enhanced.
  • RuleBase Compare will work for secure (HTTPS) environments as well as  non-secure (HTTP) environments.
  • Install will gracefully handle the presence of a duplicate key during import.
  • When install fails, system will set tables back to original state.
  • Remote MBean methods will now work on multi-servant load-balancing systems.
  • Enhancements were made to harnesses in Split Schema systems.

High number of busy waits when using Oracle SecureFiles

Valid from Pega Version 7.2.1

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.

Extract marker file not created at startup

Valid from Pega Version 7.2.1

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.

Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema

Valid from Pega Version 7.2.1

If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us