Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Fehlerbehebungsanleitung
8-8
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 8 Troubleshooting Tips
Backup, Restore, and Update Problems
b.
Fresh install both servers using Cisco Unified CCX installer.
c.
Rerun the Restore.
Step 4
Restart the Cisco Unified CCX Node Manager on both nodes.
Step 5
Rerun the Restore again.
Some RmCm configuration is missing after upgrade
Symptom
After the 4.5 to 7.0 upgrade is successful, the system is missing some Resource Manager
Contact Manager (RmCm) configuration (that is, resource skills group, CSQ configuration, and so on).
Error Message
None.
Possible Cause
This can happen when an upgrade was initially triggered, but failed due to the Cisco
Unified CCX Node Manager restarting in the middle of the restore. During the successful attempt for
restore, the CRS 4.5 user profile name has already been changed to a long integer by the first attempt to
restore.
restore, the CRS 4.5 user profile name has already been changed to a long integer by the first attempt to
restore.
Recommended Action
To reset the profileID = 1 for the default profilename, do the following:
Step 1
Open the SQL query analyzer and type the following:
a.
SELECT * FROM db_cra.dbo.profileIDMapping
Two records (one from Cisco CRS 4.5 and the other for Cisco Unified CCX 7.0, which is the default
one) are displayed. Note the CRS4.5_profilename record as you will need this later.
one) are displayed. Note the CRS4.5_profilename record as you will need this later.
b.
DELETE FROM db_cra.dbo.profileIDMapping, where profileName='CRS4.5_profilename
One affected row is displayed in the result window after executing the preceding command.
c.
UPDATE db_cra.dbo.profileIDMapping SET profileID =1
One affected row is displayed after executing the preceding command.
Step 2
SELECT * FROM db_cra.dbo.profileIDMapping
Step 3
Only one record with profilename 'default' and profileID=1 is displayed.
During the backup process, the backup window is accidentally closed
Symptom
During the backup process, the backup window is accidentally closed, which results in the
backup process getting terminated abruptly.
Error Message Fail to release bootstrap mutex
Recommended Action
When the backup is terminated abruptly, the Cluster Mutex lock is not released. The
lock gets automatically released after some time. Therefore, wait for 5-10 minutes and initiate the backup
process again.
process again.