Maintenance Manual

3-5
Cisco ICM Enterprise Edition Administrator Guide Release 6.0(0)
Chapter 3 The ICM Databases
Central Database
• Skill group
• Trunk group
It also maintains five-minute summary data for Routing Clients and Scripts and
half-hour data for Application Gateways and Network Trunk Groups. Although
you can view these data in reports, you cannot modify them directly or indirectly.
For specific information on the tables of the ICM databases, see the Cisco ICM
Enterprise Edition Database Schema Handbook or the on-line ICM Schema Help.
The central ICM database resides with the Logger itself. If the Logger is
duplexed, each physical Logger has its own copy of the database. If the Logger
services multiple customers, each machine has a separate database for each
customer.
The name of the central database has the form inst_sideX, where inst is an
up-to-five-character instance name and X indicates the side of the central
controller (A or B). For example, the central database for cus01 on the Side A
Logger is named cus01_sideA.
Database Sizing and Creation
When you first install the Logger software on a machine, you must also create the
central database. If you install multiple instances of the Logger software (for
multiple customers), you must create a central database for each instance.
Before creating the database, you must determine how much space it requires. The
size of the database depends on a number of factors, including the size of your
configuration, the expected call load, and how long you want to retain historical
data.
To prevent the database from growing indefinitely, old records are automatically
purged from the historical tables on a regular basis. You can work with your ICM
support provider to decide how long you want to retain historical data in the
central database.
For specific information on sizing and creating the database, see Chapter 4,
“Database Administration.”