Cisco Cisco IP Contact Center Release 4.6.2 Maintenance Manual
•
Warning message. When the central database begins to approach its capacity, the system
software issues a warning message. By default this occurs when the database is 80% full,
but this value can be configured.
software issues a warning message. By default this occurs when the database is 80% full,
but this value can be configured.
Warning messages trigger an event that is registered in AlarmTracker, which displays in an
EMS trace message in the console window.
EMS trace message in the console window.
•
Automatic purge. If you select the Automatic Purge Adjustment option when you install
the Logger software, the system software automatically deletes the oldest historical data
when database usage exceeds 80% threshold and/or when the central or HDS database nears
its capacity. If the data has not exceeded the retention period, it does not get deleted. By
default, automatic purge occurs when the database is 80% full, but you can set the percentage
when you set up the Logger. You can also set the retention period for data when you set up
the Logger.
the Logger software, the system software automatically deletes the oldest historical data
when database usage exceeds 80% threshold and/or when the central or HDS database nears
its capacity. If the data has not exceeded the retention period, it does not get deleted. By
default, automatic purge occurs when the database is 80% full, but you can set the percentage
when you set up the Logger. You can also set the retention period for data when you set up
the Logger.
Note: Refer to the Installation Guide for Cisco Unified ICM/Contact Center Enterprise &
Hosted for more on purging information from databases.
Hosted for more on purging information from databases.
•
Emergency Purge. By default, the system automatically deletes oldest historical data from
all historical tables when the database exceeds 90% usage capacity.
all historical tables when the database exceeds 90% usage capacity.
The automatic purge ensures that the database can never become completely full, which means
that you will begin to lose older historical data.
that you will begin to lose older historical data.
Monitoring the Database Size
You should regularly monitor the space used by the central database and transaction logs. You
can monitor database size by viewing the Logger’s per-process log files. The per-process log
files contain specific information on Logger and database activity. The following example shows
a per-process event log file for a side A Logger.
can monitor database size by viewing the Logger’s per-process log files. The per-process log
files contain specific information on Logger and database activity. The following example shows
a per-process event log file for a side A Logger.
Figure 18: DUMPLOG Example of Per-Process Event Log File
The Logger logs events and trace messages that show the percentage of space used in the
database. These files are stored in a \logfiles subdirectory in the Logger’s directory (la or lb).
You can view the Logger’s per-process log files by using the Unified ICM dumplog utility.
database. These files are stored in a \logfiles subdirectory in the Logger’s directory (la or lb).
You can view the Logger’s per-process log files by using the Unified ICM dumplog utility.
Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x
62
Chapter 4: Database Administration
Monitoring the Database Size