Hi
There are limitations, most notably to datatypes, as well as some
prerequisites such as every row needs to be uniquely identifiable, but
logical standby could serve your purpose.
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
On Fri, Apr 30, 2021 at 8:30 AM Cee Pee <carlospena999@xxxxxxxxx> wrote:
We have a standby DB in a DR server open for read only. A user wants to be
able to pull the data in the server in some schemas (call them schemaA,
schemaB) and want to write data in other schemas (say schemaX, schemaY)
after manipulation.
Without replication ($$), one thought that comes to mind is having another
DB, say workDB, in the same server which then can connect via a local DB
link to the standby DB. I am assuming performance will not be bad because
the data comes from the same server. Of course there will be additional
resource usage, esp IO and CPU that need to be considered.
One important thing that comes to my mind is the statistics. Is there a
way to make the 'workDB' see the statistics in the remote database (the
standbyDB) when the workDB queries come up with execution plans? This may
sound silly, but you never know unless you ask.
19c, multi TB size warehouse.
CP.
