Oninit cdi / Archive
Talk to an expert →

Trouble dropping the syscdr database

Posted in 2004

Topics: High Availability & Replication, Versions, Editions & End-of-Life

Ben — — source: Usenet: comp.databases.informix

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

↪ replying to Ben
Andreas Legner — — source: Usenet: comp.databases.informix

wonder what would need so much log space when dropping syscdr ... non empty sendq (trg_send_stxn table), ... ??? Bug basically I think adding log space should avoid this specific situation. Ben wrote: > 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

↪ replying to Ben
Brice Avila — — source: Usenet: comp.databases.informix

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

Glossary