8-27
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Database Problems
• You have altered the size of the CRS databases.
Recommended Action Depending upon the cause of the problem, do one of the following:
• From the CRS Administration web page, choose Tools > Historical Reporting and configure
automatic purging.
• If you change the size of the CRS databases, make sure that the CRS database size is equal to the
maxsize.
Historical Database db_cra is full
Symptom Historical data is not getting written into the database, db_cra.
Error Message Could not allocate space for object in database db_cra because the
PRIMARY file group is full in the SQL log file, MIVR log file.
Possible Cause The db_cra database is full.
Recommended Action Do one of the following:
Step 1 Try to start purging using the CRS Administration web page. Choose Tools > Historical Reporting >
Purge Now.
Step 2 Check the db_cra database size to make sure that it is of the proper size for the call volume generated.
E-mail notification of database purging activities is not sent
Symptom The CRS system does not send e-mail notification of database purging activities.
Error Message None.
Possible Cause The Email subsystem is not configured or e-mail notification is not set up properly in
CRS Administration.
Complete the following steps:
Step 1 From the CRS Administration web page, choose Subsystems > eMail and make sure that correct
information is entered in the Mail Server and eMail Address fields.
Step 2 From the CRS Administration web page, choose Tools > Historical Reporting and click the Purge
Schedule Configuration hyperlink.
Step 3 If multiple e-mail addresses are specified in the Send Email Notifications To field, make sure that each
address is separated with a semicolon (;), comma (,), or space.
Step 4 Make sure that the Send Email Notifications To field contains no more than 255 characters.
To Next Page
Loading...
Need help?
General