Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
I am curious - why does the dropping of syscdr cause a long transaction
?
I thought this was just a simple & quick "drop database ..." - sounds
like I need to RTFM ...
-----Original Message-----
From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]
On Behalf Of Tsutomu Ogiwara
Sent: Wednesday, December 01, 2004 6:20 AM
To: ben_informix@comcast.net; informix-list@iiug.org
Subject: RE: Trouble dropping the syscdr database
Long transaction ?
Add logical log.
--
Tsutomu Ogiwara from Tokyo Japan.
ICQ#:168106592
>From: "Ben" <ben_informix@comcast.net>
>Reply-To: "Ben" <ben_informix@comcast.net>
>To: <informix-list@iiug.org>
>Subject: Trouble dropping the syscdr database
>Date: Tue, 30 Nov 2004 16:34:32 -0500
>
>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
sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.