RE: Trouble dropping the syscdr database

In 9.4 you can bring the engine up using oninit -D. That will bring the engine up without replication, but it doesn't sound like that is the problem if you are getting a long transaction error. If replication was up you would be getting a database is being used by another user error, not a long transaction. Still sounds like you need to add more logical logs and possibly increase the size of the logs. -Dana Dana Carney III | Sr. Database Administrator/Team Lead | Intraware Manage Complex Entitlements, Enhance Customer Visibility, Accelerate Profits Any transaction terms in or attached to this message are proposals and are subject to the parties' signature of a definitive written agreement. -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of Brice Avila Sent: Wednesday, December 01, 2004 12:20 PM To: informix-list@iiug.org Subject: Re: Trouble dropping the syscdr database In 9.4 does one still need to set the CDRBLOCKOUT environmental variable to drop syscdr? I knew in earlier versions of IDS this was necessary. HTH. Brice Avila "Ben" <ben_informix@comcast.net> wrote in message news:<1101858834.EPddMNWDd0SN1+L2PWK7/w@teranews>... > I am having a bit of trouble eradicating replication from one of our servers > (Solaris 2.9, IDS 9.4 FC1) > > The cdr command to remove the replication environment failed and I am now > reverting to the brute force method (but trying to avoid oninit -i). > > When I attempt to drop the syscdr database it begins a long transaction that > eventually rolls back. Even if I explicitly set the syscdr database to no > logging it still behaves in the same way. > > Any ideas on how I can drop the syscdr database w/o logging? > > Thanks in advance, > > Ben > > > sending to informix-list sending to informix-list