[cisco-voip] Database communication error 7.1

[Ryan Ratliff]

Don't do anything until you've seen what the CURT db status report says.  There is no one magic fix for db replication issues, each CLI command is intended to fix a specific type of failure.  As of now I don't know of any good customer-facing document that details exactly what you are supposed to do and when.   I know of several people writing docs like this but they will be posted to supportforums.cisco.com (CSC) when completed.

-Ryan

On Oct 15, 2010, at 4:22 PM, Ahmed Elnagar wrote:

Nothing changed to server at all lately
And services are working normally
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]
 
 
Should I follow what is in this document http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080b04158.shtml
As I understand from it that I should stop replication then reset it…is it safe to do so without involving TAC.
 
 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 <image001.jpg>
 
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Friday, October 15, 2010 10:11 PM
To: Ahmed Elnagar
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Database communication error 7.1
 
sounds like database may not be running at all.  'utils service list'. Is A Cisco DB running?  Did hostname or DNS resolution of hostname recently change?

/Wes

Ahmed Elnagar wrote:
Hi all;
 
I am facing the below problem…I am trying to login to PUB server and I got Database communication error and I found the below output
 
admin:utils dbreplication status
 
 -------------------- utils dbreplication status --------------------
Fri Oct 15 21:59:45 EET 2010:main:General SQL failure:
Fri Oct 15 21:59:45 EET 2010:main:java.sql.SQLException: Failed to get Connection.Connector(NOT CONNECTED: Driver=com.informix.jdbc.IfxDriver;)
        at com.cisco.ccm.dbl.Connector.getConn(Connector.java:698)
        at com.cisco.ccm.dbl.Connector.connect(Connector.java:588)
        at com.cisco.ccm.dbl.Connector.connect(Connector.java:530)
        at com.cisco.ccm.dbl.Connector.createStatement(Connector.java:757)
        at com.cisco.ccm.dbl.Connector.createStatement(Connector.java:744)
        at com.cisco.ccm.dbl.Connector.executeQuery(Connector.java:921)
        at com.cisco.ccm.dbl.idbl.executeSelect(idbl.java:672)
        at com.cisco.ccm.dbl.idbl.executeSQL(idbl.java:1251)
        at com.cisco.ccm.dbl.idbl.run(idbl.java:1404)
        at com.cisco.ccm.dbl.idbl.main(idbl.java:1470)
 
 
 
Status cannot be performed when replication is down on the publisher, or on a cluster with a single active node; aborting replication status check operation
 
 
Output is in file cm/trace/dbl/sdi/ReplicationStatus.2010_10_15_21_58_25.out
 
Should I go ahead and repair DB replication or the issue maybe more complicated than that?
 
  Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
 
<image002.jpg>
  RAYA Building El Motamiez District, 6th of October, Egypt
 
  Mob: +2019-0016211
  Phone: +202 3827 6000 Ext.2475
  Website: www.rayacorp.com
  E-mail: ahmed_elnagar at rayacorp.com
  CCIE#24697 (Voice)
 <image001.jpg>
 
 
Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.
 


 
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
  
 
Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message._______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101015/2cd7818f/attachment.html>