GoldenGate should be looked at for this solution. Especially when looking at
only moving 4 small schemas. A logical standby is more of a DR solution in
general, meaning that you would have to ship archive logs, etc (i.e. whole
database). GoldenGate is the path forward.
As for cost. Yes, GoldenGate is pricey but it is worth the cost (unless you
can find a reseller who will do discounts above Oracle’s standard discount).
Part of the cost with GoldenGate is that you get Active Data Guard included.
Basically a 2 for 1 deal with the cost. Then you can use either Active Data
Guard to offload your reporting or using GoldenGate to offload your reporting.
Another benefit with GoldenGate is that version 12.3 through 21c all support
down to Oracle Database 11g. Meaning you only need to single version of
GoldenGate to do what you want to do. If you have a Oracle Database 10g
floating around, you would have to get Oracle GoldenGate 11g or 12.1/12.2 to
pull data from it.
Just my 2 cents.
Thanks
Bobby
From: "oracle-l-bounce@xxxxxxxxxxxxx" <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Mladen Gogala <gogala.mladen@xxxxxxxxx>
Reply-To: "gogala.mladen@xxxxxxxxx" <gogala.mladen@xxxxxxxxx>
Date: Thursday, January 19, 2023 at 9:35 PM
To: "tim.evdbt@xxxxxxxxx" <tim.evdbt@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx"
<oracle-l@xxxxxxxxxxxxx>
Subject: Re: Logical Standby
On 1/19/23 17:14, Tim Gorman wrote:
Can you cite a reference stating that logical standby is being deprecated or
has been deprecated?
All I could find was references from the Oracle10g timeframe about DataGuard
Broker and failovers to Logical Standby, but nothing about deprecation.
One big advantage of Logical Standby as opposed to GoldenGate is cost, which is
probably why the original poster is intending to try it in the first place.
Here is the part from the deprecated features manual that has confused me:
Oracle Data Guard Logical Standby Properties Deprecated
Starting in Oracle Database 19c, Logical Standby properties of Oracle Data
Guard broker are deprecated.
The following Oracle Data Guard broker Properties that affect Logical Standby
are deprecated:
* LsbyMaxEventsRecorded
* LsbyMaxServers
* LsbyMaxSga
* LsbyPreserveCommitOrder
* LsbyRecordAppliedDdl
* LsbyRecordSkippedDdl
* LsbyRecordSkipErrors
* LsbyParameter
The manual can be found here:
https://docs.oracle.com/en/database/oracle/oracle-database/19/upgrd/behavior-changes-deprecated-desupport-oracle-database.html#GUID-67D84AC9-4E9A-4F10-82C4-0FCF40AD16E1
Logical standby features in DGMGRL are deprecated, not logical standby itself.
That's what happens when I don't read carefully.
With respect to price, you are right, logical standby is much cheaper than GG.
However, managing a logical standby is a pain in the neck....or lower,
especially if the standby database is used to read and write. Skipping
transactions, fixing inconsistencies and using skip packages to skip DDL
operations (truncate) can be a lot of effort. I find GG much easier to use, but
that's my personal impression only. I confess that I have much less experience
with GG than with logical standby. With GG, I was only replicating one
relatively small set of around 250 tables from an OLTP database to data
warehouse and that was it. It wasn't making any fuss at all and was easy to
maintain. However, I am a development DBA now and I leave configuration of both
standby databases and GG to other people. I also don't get called in the middle
of the night when log_archive_dest_1 gets filled up because storage team did
some maintenance and the archive log backup was turned off.
Again, I apologize for the misinformation. Please don't report me to the DHS.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
