RE: Standby databases and batch loads

And then there is a third, even more complicated strategy:

Keep your MO, but :
- stop the managed recovery (data guard) or stop applying archives (good ol' hot standby) standby after the batch load

- put the tablespace in backup mode
- copy the datafiles over to the standby
- resume the recovery

Slick RMAN scenarios can be used to create even more variations.

This is a partial instantiate. You were taking backups of your primary already, just after the batch load, weren't you? Now you're just 'backing up' to the standby.

One might argue that the database is vulnerable between the start of the batch and the end of the partial instantiate. However, as it is a batch load, probably the load can be repeated at the standby after activation. Other transactions are safe: they exist in the archives, and they can still be forwarded to the standby. Be sure you isolate the tables involved in the batch load in their own tablespace.

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Thu, 2007-03-15 at 21:18 -0400, Mark W. Farnham wrote:

> Well - it's not that it cannot be done, it is just a bit more complicated.
>
> One standard strategy is to partition the tables being loaded such that the
> bit being loaded in append mode is in a relatively small tablespace and
> file. You do indeed need to re-instantiate any of the files that contain
> unlogged operations.
>
> You can also use "force logging" but if you absolutely require the speed of
> unlogged append mode for your daily loads, that will degrade the load speed
> somewhat.
>
> Are you planning to use dataguard or roll your own?
>
> Regards,
>
> mwf
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of genegurevich_at_discoverfinancial.com
> Sent: Thursday, March 15, 2007 6:21 PM
> To: oracle-l_at_freelists.org
> Subject: Standby databases and batch loads
>
> Hi everybody:
>
> This is something that seems to be straightforward enough , but still.
> If I have a database with several large tables which are loaded daily in
> append mode (Oracle 10G),
> can we setup a standby database? Based on what I know from the oracle 7
> version (that's the last
> standby database I handled), the standby database is based on reading the
> archived logfiles
> and applying them to the standby DB. If I do loads in append mode, which do
> not create any
> logfiles, it seems to mean that standby database is not even an option in
> my scenario. Am I correct
> or am I missing something here?
>
> thank you
>
> Gene Gurevich
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l