<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>[cisco-voip] FYI - CCM upgrade / SQL caveat</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText59894 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Your first upgrade?
<grin></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Robert Singleton<BR><B>Sent:</B> Mon 11/20/2006 5:34 PM<BR><B>To:</B>
'cisco-voip@puck-nether.net Voip'<BR><B>Subject:</B> [cisco-voip] FYI - CCM
upgrade / SQL caveat<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>I remembered reading this in the preparatory documentation, but
not<BR>until I had chewed my fingernails off fretting over the loss of
some<BR>very helpful SQL tools I'd written and was exploring with
Enterprise<BR>Manager trying to see what was up.<BR><BR>The database name
incremented in my upgrade from 4.0(2a)sr2 to 4.1(3).<BR>All of my tools were
modifying the still-present CCM0300 database,<BR>however CallManager is now
using the CCM0301 database. A quick edit to<BR>my odbc layer configs and
everything works
again!<BR><BR>Robert<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR>cisco-voip@puck.nether.net<BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck..nether.net/mailman/listinfo/cisco-voip</A><BR></FONT></P></DIV>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>