RE: Standby databases and batch loads

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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of genegurevich@xxxxxxxxxxxxxxxxxxxxx
Sent: Thursday, March 15, 2007 6:21 PM
To: oracle-l@xxxxxxxxxxxxx
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

Other related posts: