Re: Using Dataguard for a cut down reporting database

Hi!

If you have those tables you need in standby, in separate tablespace, you could alter the datafiles of unneeded tables offline in standby. They don't have to exist physically, no recovery is done on them in standby.

In addition to your data tablespace files, you have to have SYSTEM and ROLLBACK online as well, also TEMP might be needed, since you are doing reporting, thus possibly on-disk sorting.

Oracle Streams is a nice utility as well, I've almost got it to work :)

Tanel.

"Paul" <thompsonp_at_logica.com> wrote in message news:aaebc71a.0303190607.643e62ee_at_posting.google.com...
> I have been reading about DataGuard and its use for creating one or
> more standby databases.
>
> Is it possible to use the same features to create a reporting
> database, but limit the tables (or data within a table) that is
> maintained in the standby.
>
> For example if the primary database has a particularly large table
> with lots of activity (inserts, updates), but the reporting database
> doesn't need to see all this data, can it be configured to ignore or
> skip the elements of the shipped log files that relate to this table?
>
> Being able to do so would save time in applying the logs, but more
> importantly allow for a much smaller reporting database.
>
> Thanks
> Paul
Received on Fri Mar 21 2003 - 14:03:31 CST