Re: Question on dropping tablespace and transportable tablespaces
From: Justin Mungal <justin_at_n0de.ws>
Date: Sat, 7 Sep 2013 06:55:09 -0500
Message-ID: <CAO9=aUz9R0bfEVYtjf2v8kSoiCsMsD-4MNbnY8J7mjWOgFDjVQ_at_mail.gmail.com>
What about a read-only standby with managed recovery stopped? The archive logs will still ship, but the users will see the data as it was when you stopped managed recovery. Then, when refresh time comes around, you turn on managed recovery, the standby catches up, and you're good to go. If there is some rule in place that states that the users can't see the database in an intermediate state, you can leave the database in mount mode while managed recovery is catching up.
Date: Sat, 7 Sep 2013 06:55:09 -0500
Message-ID: <CAO9=aUz9R0bfEVYtjf2v8kSoiCsMsD-4MNbnY8J7mjWOgFDjVQ_at_mail.gmail.com>
What about a read-only standby with managed recovery stopped? The archive logs will still ship, but the users will see the data as it was when you stopped managed recovery. Then, when refresh time comes around, you turn on managed recovery, the standby catches up, and you're good to go. If there is some rule in place that states that the users can't see the database in an intermediate state, you can leave the database in mount mode while managed recovery is catching up.
The only caveat I can think of is all of the space required for the archive logs. Still, it sounds like it would be a lot less work than using the TT method. Mind you, if you script it all out, it might not be so bad.
-- http://www.freelists.org/webpage/oracle-lReceived on Sat Sep 07 2013 - 13:55:09 CEST