In one of my previous posts I have described the rationale for using a checkpoint table in the Replicat process. This is a summary of all possible combinations of Replicat process and which of them are able of (not) using checkpoint table.
According to the documentation it is not allowed to use NOSCHEDULINGCOLS with ADD TRANDATA when you would use Integrated Replicat. Why would Oracle care for that? Let’s find out what can happen if you don’t apply the rules.
One of the key aspects for replication is checkpointing. A target database checkpoint tells which transactions are actually committed and which not yet. This is a key aspect of transactional replication. Let’s look how that works for the Oracle GoldenGate Classic Replicat.
Most people I have spoken to are are absolutely convinced that the Extract process has to be running on the source database host. This thinking comes from all Oracle diagrams where the Extract process is located on the source database host. Till OGG version 11.1.1 this was indeed true. Some have heard that the Extract …
According to the Oracle database documentation there are two types of constraints: DEFERRED and NOT DEFERRED. The first one can be evaluated at the and of the transaction, and the second one if validated immediately. On the other hand Oracle GoldenGate can handle the replication when the target uses both of them. Let’s find out …
How Oracle GoldenGate Replicat handles Foreign Key Constraints Read More »
In my previous post I have analyzed what happens if you would like to prevent archive logs from deletion so that they can be further processed by Oracle GoldenGate. I have assumed that it would work the same if the RMAN recovery catalog was being used. Lets find out what happens.
This is a follow up of my previous article about an analysis of all Extract parameters for Oracle GoldenGate 11.2 and 12.1. It is a comprehensive analysis of how the parameters UPDATERECORDFORMAT COMPACT|FULL, (NO)COMPRESSUPDATES, (NO)COMPRESSDELETES, (IGNORE)GETUPDATEBEFORES and also (NO)LOGALLSUPPCOLS used in Extract param file affect what is written to the trail file.
This is a follow up of my previous article about an analysis of all Extract parameters for Oracle GoldenGate 11.2. How the parameters UPDATERECORDFORMAT COMPACT|FULL, (NO)COMPRESSUPDATES, (NO)COMPRESSDELETES, (IGNORE)GETUPDATEBEFORES affect what is written to the trail file.
This article presents the complete full list of cases that has been used in Extract analysis of Oracle GoldenGate 11.2
In one of my previous posts I have made a detailed analysis about supplemental logging in the database that is a result of ADD TRANDATA command from OGG. Apart of what is written to the redo log it is another subject of what is read from the redo log by OGG and written to the …
What is Oracle GoldenGate Extract writing to the trail file (OGG 11.2) Read More »