|
Home > Archive > Voice over IP Cisco > August 2007 > BARS Restore - Failed to drop database CCM0300
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BARS Restore - Failed to drop database CCM0300
|
|
| Linsemier, Matthew 2007-08-25, 7:11 am |
| I am attempting to do a BARS restore on a CallManager 4.1(3) publisher
at this time. When I run the BARS restore Wizard and enter all of the
information (local file, CCM Database, admin ID & PW) the restore
starts, but I always receive a "failed to drop database CCM0300" in the
logs. The CDR database is dropped and restored without any issues.
Could this mean I am using the wrong version of BARS that it was backed
up with or is there something else going on?
Matt
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
| |
| Wes Sisk 2007-08-26, 1:11 pm |
| turn off all 3rd party monitoring apps like infortel, prognosis,
etc. they make queries to the database that will keep it open and
locked.
worst case scenario use 'sp_who2' and 'sp_lock' to see what apps have
open sessions to the database.
/wes
On Aug 25, 2007, at 2:58 AM, Linsemier, Matthew wrote:
I am attempting to do a BARS restore on a CallManager 4.1(3)
publisher at this time. When I run the BARS restore Wizard and enter
all of the information (local file, CCM Database, admin ID & PW) the
restore starts, but I always receive a “failed to drop database
CCM0300” in the logs. The CDR database is dropped and restored
without any issues. Could this mean I am using the wrong version of
BARS that it was backed up with or is there something else going on?
Matt
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may be
protected by one or more legal privileges. It is intended solely for
the use of the addressee identified above. If you are not the
intended recipient, any use, disclosure, copying or distribution of
this communication is UNAUTHORIZED. Neither this information block,
the typed name of the sender, nor anything else in this message is
intended to constitute an electronic signature unless a specific
statement to the contrary is included in this message. If you have
received this communication in error, please immediately contact me
and delete this communication from your computer. Thank you.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Linsemier, Matthew 2007-08-26, 7:11 pm |
| I wanted to let everyone know that the problem was resolved when I
installed BARS 4.0(9). This may have been the version that I was using
to make backups all the time, I just couldn't check on the failed hard
disk. BARS restored the data quickly and flawlessly for both CCM and
CRS. This is the first time (and hopefully the last) where I had to
restore a publisher. It's nice to know that the utilities that Cisco
provides do work. Thanks again for everyone's suggestions and help.
Matt
From: Wes Sisk [mailto:wsisk@cisco.com]
Sent: Sunday, August 26, 2007 1:25 PM
To: Linsemier, Matthew
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] BARS Restore - Failed to drop database CCM0300
turn off all 3rd party monitoring apps like infortel, prognosis, etc.
they make queries to the database that will keep it open and locked.
worst case scenario use 'sp_who2' and 'sp_lock' to see what apps have
open sessions to the database.
/wes
On Aug 25, 2007, at 2:58 AM, Linsemier, Matthew wrote:
I am attempting to do a BARS restore on a CallManager 4.1(3) publisher
at this time. When I run the BARS restore Wizard and enter all of the
information (local file, CCM Database, admin ID & PW) the restore
starts, but I always receive a "failed to drop database CCM0300" in the
logs. The CDR database is dropped and restored without any issues.
Could this mean I am using the wrong version of BARS that it was backed
up with or is there something else going on?
Matt
________________________________
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may be
protected by one or more legal privileges. It is intended solely for the
use of the addressee identified above. If you are not the intended
recipient, any use, disclosure, copying or distribution of this
communication is UNAUTHORIZED. Neither this information block, the typed
name of the sender, nor anything else in this message is intended to
constitute an electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete this
communication from your computer. Thank you.
________________________________
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
|
|
|
|
|