Cisco Cisco IP Contact Center Release 4.6.2 Guida Utente
Once data recovery is complete, the Logger begins to send the recovery data to the HDS. Report
data for the selected interval is available once the Logger has completed recovery and the data is
replicated to the HDS.
data for the selected interval is available once the Logger has completed recovery and the data is
replicated to the HDS.
This problem could also occur if the HDS has gone offline or because the HDS went offline and is
now in the process of recovering. If it is recovering, data for the selected interval will be available
when recovery for that interval is complete. If the HDS has failed, the data for that interval will be
available when the HDS comes back up and completes recovery for that interval. In either case the
data is still on the logger and is not lost.
now in the process of recovering. If it is recovering, data for the selected interval will be available
when recovery for that interval is complete. If the HDS has failed, the data for that interval will be
available when the HDS comes back up and completes recovery for that interval. In either case the
data is still on the logger and is not lost.
Action:
No action is necessary; the data will appear in reports when the recovery and/or replication processes
are complete. Try running the report again in several minutes.
are complete. Try running the report again in several minutes.
Data is missing from the Historical Data Server after it has recovered from a failure
Historical data is missing from the HDS.
Message:
None
Cause:
This could be because your logger data retention and Historical Data Server backup schedule are
not in sync. You should plan these two schedules together so that you retain data on the logger for
the period in which the HDS is not backed up. For example, if you are retaining data on the logger
for 2 weeks, you should back up the HDS, at the minimum, once every two weeks. This way, if the
HDS fails, it can recover past data up to the last two weeks from a previous HDS back up and data
for the last two weeks from the logger. If you are backing up the HDS every two weeks but storing
data on the logger for only a week, you will be missing a week of historical data if the HDS fails or
the database has become corrupted.
not in sync. You should plan these two schedules together so that you retain data on the logger for
the period in which the HDS is not backed up. For example, if you are retaining data on the logger
for 2 weeks, you should back up the HDS, at the minimum, once every two weeks. This way, if the
HDS fails, it can recover past data up to the last two weeks from a previous HDS back up and data
for the last two weeks from the logger. If you are backing up the HDS every two weeks but storing
data on the logger for only a week, you will be missing a week of historical data if the HDS fails or
the database has become corrupted.
Action:
Change the data retention on the logger or backup schedule for the HDS to avoid this issue
Troubleshooting Application Gateway Reporting
The number of Application Gateway requests in reports is larger than the number of Router
Call Detail records
Call Detail records
The number of Application Gateway requests shown in the WebView Application Gateway Half Hour
Status report is larger than the number of Router Call Detail (RCD) records in the database.
Status report is larger than the number of Router Call Detail (RCD) records in the database.
Message:
None
Cause:
Cisco IP Contact Center Enterprise Edition Reporting Guide Release 6.0
143
Troubleshooting IPCC Enterprise Report Data
Troubleshooting Application Gateway Reporting