With each new release of Dbvisit Replicate we strive to have additional targets. Dbvisit Replicate 2.8 is no different and we have added three new targets. Many of these new targets come out of partner and customer requests. Let’s look into the first new target of Dbvisit Replicate 2.8. The first target we want…
We have several databases where automatic capturing of sql plan baselines is enabled for a few schemas.
Execution of some queries deeply depend on variables where is not always the best to reuse same execution plan for all executions. For those queries I want to avoid using literals and inefficient execution plans. Also, I want to use SQL plan baselines as I have automatic capturing enabled.
Question is, can I make Adaptive Cursor Sharing to work with SQL Plan Baselines without changing query?
The Goldengate INSERTALLRECORDS commands can be used in cases where the requirement is to have on the target database a transaction history or change data capture (CDC) tables which will keep a track of changes a table undergoes at the row level.
So every INSERT, UPDATE or DELETE statement on the source tables is captured as INSERT statements on the target database
But in certain cases update statements issued on the source database can cause the replicat process to abend with an error:
The goal of this blog is to to easily explain an efficient way of moving ASM to new Disks. Every now and then we need to come up with a way to move to new hardware, especially when Disks are created with external redundancy. New disks are required to come in, and old disk need to be phased out.