RE: Reasons for not considering Logical Standby Databases for Reporting purposes

Of primary concern is the datatype support. Logical standby doesn't support all datatypes so that should certainly be high on the list of things to check. For a reporting database a logical is likely to be a good idea, but to have it as your standby (that is as a disaster recovery site) it's likely to not be the best choice, a physical is the best for that.  

Ric Van Dyke

Hotsos Enterprises

Hotsos Symposium March 4-8, 2007. Be there.

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Anurag Verma Sent: Friday, November 03, 2006 11:02 AM To: oracle-l_at_freelists.org
Subject: Reasons for not considering Logical Standby Databases for Reporting purposes  

Hello friends,

We are thinking of setting up a Standby database for reporting purposes during the business hours and after that apply the pending logs.

We are considering various options of multiple physical standby databases, cascaded
redo log destinations and logical standby databases.

Today, I was reading the Logical standby databases and their advantages.

Have any of you guys thought about Logical standby databases while designing a standby database where it can be used for reporting purposes.

I want to know what are the reasons or disadvantages of Logical standby databases
that prompted you for NOT TAKING Logical standby databases for such a design.

If you can give me some inputs, it would be really great...

Thanks in advance,

 Anurag

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