[cisco-voip] Database communication error 7.1

Ryan Ratliff rratliff at cisco.com
Fri Oct 15 16:48:47 EDT 2010


Sounds like the pub can't connect to its own database.   You've already established that A Cisco DB is running which is good.

If you want to try rebooting then go for it, otherwise I think it's time to call TAC.

-Ryan

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

I am able to run it on SUB01 and the output shows that the replication is good on the publisher and bad on all subscribers!!!!
 
 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 <image001.jpg>
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Elnagar
Sent: Friday, October 15, 2010 10:41 PM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Database communication error 7.1
 
The same error when I try to access the page with PUB IP…when using SUB IP it stays long time and nothing generated.
By the way subscribers admin pages are accessible…RTMT to PUB is not working ….RTMT to SUB working and shows DB replication 2 for PUB and 3’s for SUBs.
 
 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 <image001.jpg>
 
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Friday, October 15, 2010 10:26 PM
To: Ahmed Elnagar
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Database communication error 7.1
 
Go into the CURT web page and run the db status report, see what it says for replication status.
 
-Ryan
 
On Oct 15, 2010, at 4:02 PM, 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
 
<image001.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)
 <image002.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.
 
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.

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


More information about the cisco-voip mailing list