cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6899
Views
0
Helpful
3
Replies

UCCX error while updating Cisco Script Application

cndilip123
Level 1
Level 1

Hi all,

I am using UCCX 9.0.2 in my lab.

I have a working Cisco Script Application mapped to a trigger.

I want to update to the script to a new script in this application.

When I click on the Update button I get this error: "Error while performing the operation. Please look into logs for more information. "

 

Please let me know what logs would be helpful to check further on this error. I could not see any logs matching the error in the default MIVR logs.

 

Thanks,

Dilip

1 Accepted Solution

Accepted Solutions

Arundeep Nagaraj
Cisco Employee
Cisco Employee

Hi Dilip,

Can you check if the Cisco Unified CCX Database is IN SERVICE on both the nodes?

To verify the integrity can you run the following command on both the nodes (non-business impacting)

utils uccx database dbserver integrity

Check the update post that. If it still fails, look out for the Replication Servers under the Cisco Unified CCX Serviceability -- Tools -- Datastore Control Center -- Replication Servers.

Both nodes should show Connected and Active with the Reset replication button available.

then proceed to the Related Links for Datastores and check the Config Datastore. See if it shows both the nodes and if the status is RUNNING.

The Config Datastore works on the Informix 2 phase commit protocol which means that for a transaction to be commited into the DB, both the primary and target node (Informix terminology) needs to participate in the transactions.

This will fail if the one of the nodes is down, DB on one of the nodes is down. If the secondary node goes down, then to make a config update, the Disable CDS/HDS can be carried out which will remove this protocol and the config changes will be successful from the primary.

if the primary is down and the secondary is up and if you try to make a config change, it will fail always as the IDS need the primary to be up for the protocol and there is no workaround to this.

Hope this helps!

Regards,

Arundeep

View solution in original post

3 Replies 3

Arundeep Nagaraj
Cisco Employee
Cisco Employee

Hi Dilip,

Can you check if the Cisco Unified CCX Database is IN SERVICE on both the nodes?

To verify the integrity can you run the following command on both the nodes (non-business impacting)

utils uccx database dbserver integrity

Check the update post that. If it still fails, look out for the Replication Servers under the Cisco Unified CCX Serviceability -- Tools -- Datastore Control Center -- Replication Servers.

Both nodes should show Connected and Active with the Reset replication button available.

then proceed to the Related Links for Datastores and check the Config Datastore. See if it shows both the nodes and if the status is RUNNING.

The Config Datastore works on the Informix 2 phase commit protocol which means that for a transaction to be commited into the DB, both the primary and target node (Informix terminology) needs to participate in the transactions.

This will fail if the one of the nodes is down, DB on one of the nodes is down. If the secondary node goes down, then to make a config update, the Disable CDS/HDS can be carried out which will remove this protocol and the config changes will be successful from the primary.

if the primary is down and the secondary is up and if you try to make a config change, it will fail always as the IDS need the primary to be up for the protocol and there is no workaround to this.

Hope this helps!

Regards,

Arundeep

Thanks Arundeep.

You are correct the secondary node is down. Meanwhile, I disabled CDS/HDS to complete my work.

 

Regards,

Dilip

Below is how I have been able to temporarily fix mine but I need a perm fix

 

Ran the utils uccx database dbserver integrity on both nodes and didn't look good
Error on both nodes showed=Internal CLI Error: Failed to connect to the database of node DC21-CUCCX1
I restarted Cisco Unified CCX Cluster View Daemon service and issue came clear

 

*Why is this failing continously?

*Also, what is the impact of leaving CDS/HDS disabled ?
========================================================
admin:utils uccx database dbserver intergrity

Executed command unsuccessfully
No valid command entered
admin:utils uccx database dbserver integrity
This operation may take a few minutes to complete. Please wait...

Output is in file: uccx/cli/DbServerIntegrity_1524829028379.txt

Command successful.
Starting DB config integrity check
This operation may take a few minutes to complete. Please wait...

Output is in file: uccx/cli/DbConfigIntegrity_1524829209977.txt
Internal CLI Error: Failed to connect to the database of node DC21-CUCCX1
admin:utils service list

Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STARTED]
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STARTED]
Cisco Audit Event Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco Certificate Change Notification[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STARTED]
Cisco Database Layer Monitor[STARTED]
Cisco Desktop Administrator Service[STARTED]
Cisco Desktop Agent E-Mail Service[STARTED]
Cisco Desktop Browser and IP Phone Agent Service[STARTED]
Cisco Desktop Call/Chat Service[STARTED]
Cisco Desktop Enterprise Service[STARTED]
Cisco Desktop LDAP Monitor Service[STARTED]
Cisco Desktop License and Resource Manager Service[STARTED]
Cisco Desktop Recording and Playback Service[STARTED]
Cisco Desktop Recording and Statistics Service[STARTED]
Cisco Desktop Sync Service[STARTED]
Cisco Desktop VoIP Monitor Service[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco Serviceability Reporter[STARTED]
Cisco Syslog Agent[STARTED]
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Cisco Unified CCX Administration[STARTED]
Cisco Unified CCX CVD Dependent Webapp[STARTED]
Cisco Unified CCX Cluster View Daemon[STARTED]
Cisco Unified CCX DB Perfmon Counter Service[STARTED]
Cisco Unified CCX Database[STARTED]
Cisco Unified CCX Engine[STARTED]
Cisco Unified CCX Perfmon Counter Service[STARTED]
Cisco Unified CCX SNMP Java Adapter[STARTED]
Cisco Unified CCX Serviceability[STARTED]
Cisco Unified CCX Voice Subagent[STARTED]
Cisco Unified Serviceability[STARTED]
Cisco Unified Serviceability RTMT[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Primary Node =true

admin:utils service restart Cisco Unified CCX Cluster View Daemon
Service Manager is running
Cisco Unified CCX Cluster View Daemon[STOPPING]
Cisco Unified CCX Cluster View Daemon[STOPPING]
Cisco Unified CCX Cluster View Daemon[STOPPED] Commanded Out of Service
Cisco Unified CCX Cluster View Daemon[STOPPED] Commanded Out of Service
Service Manager is running
Cisco Unified CCX Cluster View Daemon[STARTING]
Cisco Unified CCX Cluster View Daemon[STARTING]
Cisco Unified CCX Cluster View Daemon[STARTING]
Cisco Unified CCX Cluster View Daemon[STARTING]
Cisco Unified CCX Cluster View Daemon[STARTED]
Cisco Unified CCX Cluster View Daemon[STARTED]
admin:utils uccx database dbserver integrity
This operation may take a few minutes to complete. Please wait...

Output is in file: uccx/cli/DbServerIntegrity_1524829466201.txt

Command successful.
Starting DB config integrity check
This operation may take a few minutes to complete. Please wait...

Output is in file: uccx/cli/DbConfigIntegrity_1524829483114.txt
Command successful.
admin: