Re: Trouble dropping the syscdr database

Andreas Legner <fake@xx.yy.de> wrote in message news:<315hoaF37e30tU1@individual.net>... > wonder what would need so much log space when dropping syscdr ... non empty sendq (trg_send_stxn > table), ... ??? Without any other information, I'd bet that it's due to having to remove disk queue (i.e. SBLOBS). > > 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