This document describes potential reasons why the local database
initialization on a Cisco Intelligent Contact Management (ICM) Distributor
Admin Workstation (AW) or Historical Data Server (HDS) takes a long time to
Readers of this document should have knowledge of these topics:
The information in this document is based on these software and
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
For more information on document conventions, refer to the
Technical Tips Conventions.
When you install Distributor AW software, automatic creation and
initialization of the local database occurs. The local database contains this
configuration information, which the software copies from the central
scripts, which the software copies from the central
real-time data between the real-time server and
You do not need to initialize the local database. However, you need to
reinitialize the local database in some situations, such as database corruption
or an out-of-sync database.
The time necessary to complete the local database initialization
depends on these factors:
the actual size of the configuration information and
the available resource, such as the CPU or virtual memory on the
Distributor AW and HDS
the network infrastructure between the Distributor AW, HDS, and the
If the database initialization fails for any reason, such as a network
failure, the initialization process begins again from the start. Therefore,
when the local database initializes, do not permit any ICM user to make
configuration changes to ICM. A change can interrupt the database
reconstruction and interrupt the initialization process.
To manually prevent configuration changes by ICM users, perform this
Open the Windows registry on the ICM
Navigate to the DBMaintenance key with this path:
For versions earlier than 5.0:
For versions 5.0 and later:
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<cust_inst>\
Note: Here, these two registry keys display over two lines because of
Set the DBMaintenance key value to 1, as Figure 1 shows.
Note: Set this setting back to 0 after initialization of the database
in order to allow ICM users to make configuration changes.
Figure 1: DBMaintenance—1
Note: In a duplex environment, you must set the DBMaintenance key value
to 1 on both CallRouterA and CallRouterB.
The problem is the inability to initialize the real-time feed,
for instance pmusa. You cannot proceed until the real-time is
This issue that you cannot start the configuration manager occurs
because Windows 2000 does not support the console being taken over through
RDP/TS. You can use VNC in order to resolve this issue.