Re: Consistent export vs.snapshot too old.

"Howard J. Rogers" <howardjr_at_www.com> wrote in <3aadde4f_at_news.iprimus.com.au>:

>
>"Kevin Grant" <K.Grant_at_nowhere.com.au> wrote in message
>news:Xns9063A13E939A3KGRANTBNEQLDAU_at_132.234.250.31...
>> Jarek Palka <jarek_at_kamsoft.com.pl> wrote in
>> <3AACF264.164F3D85_at_kamsoft.com.pl>:
>>

.
.
>> >How can we avoid such errors ?
>>
>> There is another option that we use here. We have a database that is
>> up 24x7. Every morning we clone this database, then export the clone.
>>
>> The whole process is automated and goes like this:
>> - Place each datafile in turn into backup mode and copy.
>> - Recover clone database to a point in time.
>> - Open clone database and export.
>
>
>I like this. It's quite clever, and will certainly produce the results
>you want. The problem as I see it is that cloning can be a tricky
>business, and point-in-time recoveries are not a picnic. Ever
>considered exporting from a read-only standby database? Only available
>in 8i, of course, but -especially with the new automated transfer of
>archive files as a possibility, it strikes me that it would be easier
>than cloning. Just a thought -though one I confess I've never tried
>myself.
>
>Regards
>HJR
You're right, cloning is a tricky business. But now that we have the script all worked out it runs like a dream. Never had a problem.

The trick though was getting the script to work. All the ones that I managed
to find on the web didn't really work well or not at all. So we spent a couple of days writing our own.

As for the standby database - this is a much better option, as you suggest. Unfortunately our database in only at 8.0.6. We are planning on upgrading shortly and I'll be looking very closely at the readonly standby as an option.

Kev. Received on Tue Mar 13 2001 - 17:03:29 CST