Document ID: 66230
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Problem
Cause
Solution 1
Solution 2
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document describes one reason why WebView historical reports contain no data, and provides a solution.
The statistics appear with all zeros on the Cisco Intelligent Contact Management (ICM) WebView report system in a Cisco IP Contact Center (IPCC) Enterprise environment.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
-
Cisco ICM
-
Cisco WebView
Components Used
The information in this document is based on these software and hardware versions:
-
Cisco ICM version 6.x
-
Cisco WebView version 6.x
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.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Problem
WebView historical reports contain no data. The statistics appear with all zeros. See Figure 1 for an example. However, real-time WebView reports do not have any problems, and display current and correct data.
Figure 1 – WebView Historical Reports with All Zeros
Furthermore, if you issue SQL commands to examine the database content, the historical data is accurate and reliable. For example, data that you extract through this SQL command contains all the historical rows:
select * from t_Termination_Call_Detail
Cause
Corrupt table views on the Historical Data Server (HDS) cause the statistics to appear with zeros in WebView historical reports.
When you issue the sp_helptext Termination_Call_Detail SQL command on the Admin Workstation (AW), an error message appears (see Figure 2).
Figure 2 – Failure Run of sp_helptext
Solution 1
Complete these steps in order to solve the problem:
-
Run Update Version set CCMinor=0 on the AW.
-
Run Update Version set CCMinor=0 on the HDS.
-
Run Setup.exe on the AW.
-
Run sp_helptext Termination_Call_Detail (see arrow A in Figure 3). If this command fixes the problem, the result appears as shown in Figure 3.
Figure 3 – Successful Run of sp helptext
Solution 2
Choose Program Files > Sybase > shared > PowerBuilder and open the file pbodbXXX.ini. Find this part:
[MSSQLSERVER_DATETIME] ; PBDateFmt='\'yyyy-mm-dd\'' PBDateFmt='\'yyyy-dd-mm\'' PBTimeFmt='\'hh:mm:ss\'' ; PBDateTimeFmt='\'yyyy-mm-dd hh:mm:ss.fff\'' PBDateTimeFmt='\'yyyy-dd-mm hh:mm:ss.fff\''
Now, make some changes as in this example:
Note: You need to put ; in front of some lines and delete from some lines.
[MSSQLSERVER_DATETIME] PBDateFmt='\'yyyy-mm-dd\'' ; PBDateFmt='\'yyyy-dd-mm\'' PBTimeFmt='\'hh:mm:ss\'' PBDateTimeFmt='\'yyyy-mm-dd hh:mm:ss.fff\'' ; PBDateTimeFmt='\'yyyy-dd-mm hh:mm:ss.fff\''
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for Customer Contact Software |
| IP Communications and Video: Contact Center |
Related Information
| Updated: Oct 05, 2005 | Document ID: 66230 |
