Jump to: navigation, search


Section: agg
Default Value: 1800 (30 min)
Valid Values: Any positive integer
Changes Take Effect: After restart

Specifies the amount time, in seconds, within which each aggregation writer thread must return the results of its aggregation of a batch of data. If a writer thread does not respond within this time frame, RAA assumes either that the process is deadlocked or that the database is too slow and cannot process aggregation in a timely fashion. When the deadlock-threshold time period has elapsed, RAA cancels all database queries and closes all sessions. To resume processing, aggregation must be restarted.

Reporting and Analytics Aggregates Release Notes

Reporting and Analytics Aggregates is part of 9.x starting in
Release Date Release Type Restrictions AIX Linux Mac Solaris Windows
02/01/21 Update X X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • Aggregation enhancements — The performance of the ID_FCR aggregate is improved through refactoring, and through the addition of the IDX_IRFUG_CUST index to the IRF_USER_DATA_GEN_1 table. (GCXI-4300)

Resolved Issues

This release contains the following resolved issues:

The aggregation process no longer produces a NullPointerException (NPE) in scenarios where a non-Writer command continues processing after the period of time specified by the deadlock-threshold has elapsed. (GCXI-4320)

Upgrade Notes

Refer to the Deployment Procedure for this release to deploy the installation package within your environment.

This page was last edited on March 1, 2021, at 17:19.
Comments or questions about this documentation? Contact us for support!