RE: Data Guard to Logical Standby

Hi April,

You're not mentioning any version info.

>From what I've done with Logical Standby, it does not support cross
platform standby's.

Can you elaborate in your configuration?

Best regards,

Carel-Jan Engel

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


  

On Thu, 2008-05-01 at 14:25 -0500, April Wells wrote:
> Okay… I’ll buy that.
> 
>  
> 
> However… 
> 
>  
> 
> On the logical standby, can I create users that are not in the primary
> database?  I’m trying to multi-purpose this database rather than
> “just” being a transformation database between solaris source and
> linux destination by keeping historical data and giving us an
> alternative place to run some batch reporting.  But I don’t want to
> rely on the fact that the data and structures are all representative
> of the up stream primary.
> 
>  
> 
> Or am I stuck with “just” having the ability to structure the whole
> database as if it were the primary?
> 
>  
> 
> April
> 
> 
>                                    
> ______________________________________________________________________
> 
> From: Howard Latham [mailto:howard.latham@xxxxxxxxx] 
> Sent: Thursday, May 01, 2008 2:09 PM
> To: April Wells
> Cc: oracle-l@xxxxxxxxxxxxx
> Subject: Re: Data Guard to Logical Standby
> 
> 
> 
>  
> 
> AFAIK
> 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
> 
> 
> 
> 
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner, and is 
> believed to be clean.


Other related posts: