Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Troubleshooting Guide
8-41
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 8 Troubleshooting Tips
Cisco Unified CCX Engine Problems
Step 2
Alternatively, you can shrink the log files by running the batch file runTruncateHistDBLogs.bat,
installed under the wfavvid directory. Depending on the arguments, it shrinks the log files of db_cra or
tempdb.
installed under the wfavvid directory. Depending on the arguments, it shrinks the log files of db_cra or
tempdb.
Examples:
•
Truncate the log files for db_cra to 10MB:
•
runTruncatedHistDBLogs “sa” “sa_password” “db_cra_all” 10
•
Truncate the tempdb transaction log:
•
runTruncateHistDBLogs “sa” “sa_password” “tempdb”
Additional information can be found about truncating logs in the Managing Historical Reporting
Databases section of the Cisco Unified CCX Administration Guide.
Databases section of the Cisco Unified CCX Administration Guide.
Note
This troubleshooting tip also applies to the Cisco Unified CCX Database Problems section and the Cisco
Unified CCX Historical Reporting Problems section.
Unified CCX Historical Reporting Problems section.
Cisco Unified CCX Server runs at 100% capacity or is slow
Symptom
The Cisco Unified CCX server CPU works at or close to 100 percent capacity. DTMF digits
are delayed.
Error Message
None
.
One of the following configurations might be causing this problem:
•
Trace settings include debugging.
•
Cisco Unified CM polling is enabled. (Polling is enabled by default, but it can consume server
resources.)
resources.)
•
You are running many applications on a smaller system simultaneously. For example, you are
running Cisco Unified CM, and Cisco Unified CCX Server, all on a low-end MCS.
running Cisco Unified CM, and Cisco Unified CCX Server, all on a low-end MCS.
Recommended Action
Complete the following steps:
Step 1
Turn off debugging as a trace level option. Debugging consumes substantial server resources. Only use
debugging as a trace level option when you are actively debugging Cisco Unified CCX.
debugging as a trace level option when you are actively debugging Cisco Unified CCX.
Step 2
Turn Cisco Unified CCX debugging off if the system is running BHCC higher then 4500.
Step 3
If you have a high load with 300 agents, disable all the logs and traces.
Step 4
If you have high load with 300 agents, you should redirect logs (for example Cisco Unified CM logs) to
a different drive where Cisco Unified CCX and SQL is installed.
a different drive where Cisco Unified CCX and SQL is installed.
Step 5
Turn off Cisco Unified CM polling. Polling enables JTAPI (and therefore the telephony applications that
use JTAPI, such as Cisco Unified CCX) to detect the addition of devices to an application or user’s
controlled list. For example, polling can detect when an agent is added to a call center or a CTI port is
added to the Cisco Unified CCX Engine. If you do turn off polling, Cisco Unified CM does not update
new devices automatically. For example, you must restart the Cisco Unified CCX Server after adding a
new CTI port or route point to Cisco Unified CM.
use JTAPI, such as Cisco Unified CCX) to detect the addition of devices to an application or user’s
controlled list. For example, polling can detect when an agent is added to a call center or a CTI port is
added to the Cisco Unified CCX Engine. If you do turn off polling, Cisco Unified CM does not update
new devices automatically. For example, you must restart the Cisco Unified CCX Server after adding a
new CTI port or route point to Cisco Unified CM.