Overview

Universal Enterprise Controller (UEC) uses databases to maintain agent, user, configuration, and event data.

Database Files

The UEC databases reside in three files:
 

Database Management

Automated Database Cleanup

Two routines are run to clean up records that meet their expiration criteria from their UEC database.

1. Routine for monitor events used for I-Activity Monitor.
2. Routine for persistent events stored for the Universal Event Subsystem.

Both routines execute at UEC start-up. Thereafter, they are scheduled to execute one hour after the previous execution's completion. At the time of execution, all records that meet the expiration criteria are removed from their UEC database.

The following UEC configuration options control database record retention:

• COMMIT_COMPLETE_EXPIRATION
• COMMIT_INCOMPLETE_EXPIRATION
• MONITOR_EVENT_EXPIRATION
• PERSISTENT_EVENT_EXPIRATION

Memory Management

Berkeley DB uses a temporary cache in memory to manage its databases. If this cache becomes sufficiently large, it must be written to disk.

Berkeley DB has a default location for storing temporary cache files, but if UEC cannot access that location, or there is no space to write these files in the default location, the following error can occur in UEC, and UEC shuts down:

UNV5101D Database error: 'temporary: write failed for page XXXXX'

To work around this issue, the following steps will write the temporary cache files to the UEC database directory: