Unlike Active Data Guard, GoldenGate captures primary database changes by reading redo records from disk, transforming those records into a platform independent trail file format, and transmitting the trail file to the target database. GoldenGate maintains a logical replica by converting the trail file into SQL and applying SQL to the target database. The target database is open read-write while synchronization occurs. While this provides substantial flexibility as a replication solution when compared to Data Guard, care must be taken to insure that the target database is not modified independent of the source, unless it is explicitly desired to do so.
Baselines – session creating privs v session running privs - A colleague Richard Wilkinson was telling me about an issue he had come across with baselines and I asked him to write it up as it was an interesting exper...
Acum 2 zile