Back Forward Working with the PegaRULES database
System, Log, and miscellaneous tables

 Working with the PegaRULES database

zzz Show all 

This topic describes PegaRULES database tables with names that start with one of these values:

  pr_log pr_perf_stats
  pr_sys pr_*usage*
  pr4_rule_sysgen pr_license

zzz Tables for Log- instances

Ten tables can store instances of Log- classes. The key to these instances contains a date and time in UTC format.

Table

Description
pr_log_system Inactive. Associated with the class Log-System-.
pr_perf_stats Holds instances of the Log-Usage class. See Analyzing System-wide usage with the Log-Usage table.
pr_daily_usage pr_hourly_usagepr_license_parameters
pr_usage_summary		 Support the License Compliance facility. See Working with the License Compliance facility. Select View > System > Usage Summary to report on the pr_usage_summary table.
pr4_log_rule_usage Holds statistics collected during system shutdown about cumulative rule execution statistics. Associated with the Log-RuleUsage class. See Working with the shutdown rule usage facility.
pr4_log_rule_usage_details Corresponds to the Log-RuleUsage-Details class. Holds details of a daily snapshot of the rules assembly cache, which the system can scan later at the next system startup to pre-populate the rules assembly cache. See Working with the rules assembly cache.
pr_log_dataaccessaudit Corresponds to the Log-DataAccessAudit class. When configured in harness rules and flow action rules, holds the details for each operator's use of those rules. See Flow Action form — Completing the Security tab.
pr_log Holds instances of concrete classes derived from the Log- base class, other than those in the above tables.

The Pega-RULES agent normally runs the standard Code-.SystemCleaner activity once each day for housekeeping tasks, including purging older records (instances) from certain log tables. (Separately, the License Compliance facility includes built-in daily and end-of-period purging of Log- classes.)

zzz Tables for System- instances

Nine tables can store instances of classes derived from the System- base class. These tables typically contain only a few rows with high turnover.

CautionDo not alter the mapping, schema, or structure of these tables except as advised by Pegasystems support staff.

Table

Description
pr_page_store Contains rows corresponding to instances of the System-SavedPages class. When a user session times out, the system saves a user's entire thread context automatically in this table, until that user completes a log-in challenge or an expiration timeout occurs. The system automatically deletes rows of this table that are more than three days old.
pr_sys_context Contains rows corresponding to instances of the System-Requestor-Context class, for passivated requestors.
pr_sys_decchg Contains rows corresponding to instances of the System-Declare-Changes class, to support execution of declarative expression rules.
pr_sys_locks Contains rows corresponding to locks held, instances of the System-Locks class. Supports the Locks report, available from the Developer portal View > System > Locks menu selection.
pr_sys_queues Contains rows for queued service requests, instances of concrete classes derived from the System-Queues- class. About Service Request Processor data instances.
pr_sys_statusnodes Contains one row for each participating node in the system, corresponding to instances of the System-Status-Nodes class. This table occasionally can contain apparently duplicate rows, because the true key is based on an encrypted form of the node name, system name, and path of the temporary directory. Run the RemoveOldNodes activity to purge rows corresponding to nodes that have been inactive for at least 24 hours.
pr_sys_updatescache Contains one row for each change to the rules since the most recent pulse processing by the PegaRULES agent. These rows correspond to instances of the System-Updates-Cache class. This table is canned by a trigger when rules are updated and added to the cache; it is emptied when cache processing completes. See Understanding the PegaRULES agent.
pr_sys_user Contains one row for each rule delegation, corresponding to instances of the System-User-MyRules class.
pr_sys_workindexer_queue Contains temporary instances of the System-Work-Indexer class, Supports advanced search for work objects. Hold agent queue entries after a new work object is created. After Lucene indexing is complete, the agent queue entry is removed. See How to enable and control the full text search facility.
pr4_rule_sysgen Contains instances of the System-CachedConclusion class.
Definitions Custom Fields, Log- base class, passivation, referencing rules, timeouts
Standard rules Atlas — Initial Database Table data instances
Atlas — Standard classes derived from the Log- base class
Atlas — Standard classes derived from the System- base class

HomeWorking with the PegaRULES database