Re: Data Guard to Logical Standby

  • From: "April Sims" <sims@xxxxxxx>
  • To: <howard.latham@xxxxxxxxx>
  • Date: Thu, 01 May 2008 13:19:04 -0600

You can skip objects, schemas, etc.
I skip all programming staff just for the reason outlined in the original post.

exec dbms_logstdby.skip('SCHEMA_DDL','SCHEMA','%');
exec dbms_logstdby.skip('DML','SCHEMA','%');

April Sims
SELECT IOUG Contributing Editor 
OCP 8i, 9i, 10g DBA
Southern Utah University

>>> "Howard Latham" <howard.latham@xxxxxxxxx> 5/1/2008 2:08 PM >>>
All it does is ship the logs from one db (target) to another (standby)
You cant filter anything.

2008/5/1 April Wells <awells@xxxxxxxxxxxx>:

>  We are trying to create a logical standby database (solaris) using data
> guard so we can use downstream data capture to populate a reporting database
> (Linux) for historical reporting.
> Any chance anyone has done this and can give me some pointers on what I'm
> probably going to do wrong?
> Can I set rules up stream on the source database on what tables I don't
> want to have included in the data guard log apply or will it just apply
> everything?  I'm trying to tough my way through the documentation, and am
> stuck at the "uniquely identify rows" part.  It seems that EVERYONE on the
> source system has a plan table and that doesn't have a primary key.  Do I
> care?  Will it complain?
> Should I create a primary key rely disabled on ALL of those plan tables?
> Thanks for any advice
> April
> ------------------------------
> Confidentiality Notice!
> This electronic transmission and any attached documents or other
> writings are confidential and are for the sole use of the intended
> recipient(s) identified above. This message may contain information
> that is privileged, confidential or otherwise protected from
> disclosure under applicable law. If the receiver of this
> information is not the intended recipient, or the employee, or
> agent responsible for delivering the information to the intended
> recipient, you are hereby notified that any use, reading,
> dissemination, distribution, copying or storage of this information
> is strictly prohibited. If you have received this information in
> error, please notify the sender by return email and delete the
> electronic transmission, including all attachments from your
> system.

Howard A. Latham


Other related posts: