Cisco Cisco IP Contact Center Release 4.6.2 User Guide
Cause:
This can occur if you have not enabled Service Control reporting and queue reporting for the VRU
peripheral.
peripheral.
Action:
In the ICM Configuration Manager, open the VRU peripheral. Select the Service Control option
and the Queue reporting option.
and the Queue reporting option.
Troubleshooting Historical Data Server Data
Historical Data Server is losing the oldest data
Historical Data Server (HDS) data that is within the data retention time set for the HDS is being purged
from the database.
from the database.
Message:
None
Cause:
This could occur because the database has reached 80% capacity and is therefore performing purge
adjustment each night to reduce the size to 80%. Unlike scheduled purges, in which data is purged
nightly to remove all records older than the data retention time you specified, purge adjustment
removes the last record from each table in the database until 80% capacity is reached. Purge
adjustment continues to reduce the size of the database to 80% until the database size is increased.
adjustment each night to reduce the size to 80%. Unlike scheduled purges, in which data is purged
nightly to remove all records older than the data retention time you specified, purge adjustment
removes the last record from each table in the database until 80% capacity is reached. Purge
adjustment continues to reduce the size of the database to 80% until the database size is increased.
Action:
To correct this problem, increase the size of the database.
Historical report is missing data for a recent interval
A historical report is missing data for a recent interval.
Message:
None
Cause:
This could occur because you are running the report at the end of the last interval (for example it
is 12:31 and you are running a report from the 12:00:00 to 12:29:59 interval). Data replication
from the Logger to the Historical Data Server can be delayed by 1 to 5 minutes. The data for the
last interval might not be in the HDS yet.
is 12:31 and you are running a report from the 12:00:00 to 12:29:59 interval). Data replication
from the Logger to the Historical Data Server can be delayed by 1 to 5 minutes. The data for the
last interval might not be in the HDS yet.
This also could be because the Logger connected to the HDS has gone offline or because the Logger
went offline and is now in the process of recovering. When the Logger fails, the HDS does not switch
to the back up Logger. Instead, it waits for its Logger to recover. When the Logger recovers, it
begins receiving current data and recovers data from the back up Logger for the time it was down.
went offline and is now in the process of recovering. When the Logger fails, the HDS does not switch
to the back up Logger. Instead, it waits for its Logger to recover. When the Logger recovers, it
begins receiving current data and recovers data from the back up Logger for the time it was down.
Cisco IP Contact Center Enterprise Edition Reporting Guide Release 6.0
142
Troubleshooting IPCC Enterprise Report Data
Troubleshooting Historical Data Server Data