Cisco Cisco IP Contact Center Release 4.6.1 Maintenance Manual
Overview
The local database (awdb) contains configuration and real-time data, if the Administration &
Data Server role includes a real-time server. Because the real-time data in the local database
(awdb) are constantly overwritten by new data, the database size remains fairly constant. You
normally do not need to resize the local database (awdb). If you do need to resize the local
database (awdb), you can do so using the ICM Database Administration (ICMDBA) tool. The
procedures for using the ICMDBA tool are described later in this chapter.
Data Server role includes a real-time server. Because the real-time data in the local database
(awdb) are constantly overwritten by new data, the database size remains fairly constant. You
normally do not need to resize the local database (awdb). If you do need to resize the local
database (awdb), you can do so using the ICM Database Administration (ICMDBA) tool. The
procedures for using the ICMDBA tool are described later in this chapter.
The data in the central database and HDS database grow as they accumulate historical data and
call detail records. The growth is directly related to the following factors:
call detail records. The growth is directly related to the following factors:
•
Size of the Unified ICM configuration; for example, how many services, skill groups, routes,
and trunk groups are configured.
and trunk groups are configured.
•
Call rate; that is, how many calls per day the system software is handling.
•
How long historical data is kept in the database.
The amount of configuration data directly affects the amount of historical data generated. The
system software generates a new historical record every half hour for each service, skill group,
route, trunk group, etc., configured in the Unified ICM system.
system software generates a new historical record every half hour for each service, skill group,
route, trunk group, etc., configured in the Unified ICM system.
You must size and create the central and HDS databases after installing the system software.
Use the Database Sizing Estimator applet for estimating the size of these databases, based on
the expected usage. (See the "
Use the Database Sizing Estimator applet for estimating the size of these databases, based on
the expected usage. (See the "
details.)
The database size remains adequate as long as your usage is consistent with the values used to
size the database. If your configuration expands significantly or if you change the retention
times for historical data, you might have to increase the size of the database. This might involve
adding additional disks to the system.
size the database. If your configuration expands significantly or if you change the retention
times for historical data, you might have to increase the size of the database. This might involve
adding additional disks to the system.
Normally, the central database transaction logs are sized to handle the processing of historical
data at a call rate of 35 calls per second.
data at a call rate of 35 calls per second.
Retaining Historical Data
The system software initiates a purge process on the Logger once every day. By default, the
purge process runs each night at 12:30 A.M. The purge process deletes records that are older
than a specified number of retain days. When you set up the Logger using the Web Setup tool,
you can modify the default retention time and purge schedule.
purge process runs each night at 12:30 A.M. The purge process deletes records that are older
than a specified number of retain days. When you set up the Logger using the Web Setup tool,
you can modify the default retention time and purge schedule.
The following data lists the default settings for retaining historical data.
Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x
46
Chapter 4: Database Administration
Overview