OpenLogReplicator can be fine-tuned over and over. Still something would to be imperfect. Some code might not be optimal and need refactor. Another feature might be recognised as super important and a must-have. This will never end. Still, after over 4 years of fixing bugs and constant development, the time has come to confirm that …
This is the question I hear very often. I think many people would like to hear a straight answer for this question. The reality is not possible to give a good answer. You might be surprised but, even though version 1.0 is not yet released, OpenLogReplicator is already used in production systems. Yet might be not feasible for everybody to use.
After almost 3 years of development, the project has reached a moment, that most of the features planned for version 1.0 are finished for OpenLogReplicator. So … announcing version 0.9.0-beta. At this point the goal is to make the code stable as possible and fix all reported bugs. If you want to test the code …
Technically speaking support of DDL is trivial. All schema is written in SYS.xxx$ tables. Just what you need to do is to track the changes, and once they appear, rebuild internal dictionaries. Someone adds column to table? Well, you would see an INSERT to SYS.COL$ and maybe some other tables. … A few months later …
The task here is just to run native replication solution directly on Raspberry PI hardware. No emulators, no workarounds, no cheating. Let’s find out what is the redo log processing speed. The key to this approach is using OpenLogReplicator as CDC engine and it’s offline mode. With this mode you can read redo logs without …
Oracle at some point of decided that users might want to replicate the changes from the database to other targets. What they noticed, that the architecture of the database did not allow easy replication since the redo log did not contain information that would allow to identify the exact row, that has been modified. The …
Supplemental logging – how much space does it require? Read More »
The format is proprietary and there is no public official document which would describe the structure. Here is a brief summary of various sources which are publicly available. One might think that there is very little information available, but that’s not true. This is a list I have made in the past when I was …
One of the most confusing with Oracle replication tools is the inability to track changes of tables owned by SYS, SYSTEM or CTXSYS. Many system tables are internally using cluster type. Since the latest version OpenLogReplicator supports cluster tables it is now possible track also tables in SYS schema and send changes as events to …
Oracle database: replicating objects from SYS schema Read More »
Replication latency is one of the key indicators of good replication. When I started working on OpenLogReplicator one of my key tasks was to keep the latency as low as possible. What does that mean? When a client commits a transaction and the database confirms that the transaction is committed – it means that the …
Every Oracle database user assumes that the output of the logdump command should provide a valid output. During testing of OpenLogReplicator I came across something strange. It appears that the output of OpenLogReplicator logdump mode is better than the original output of Oracle database logdump command. Maybe I am wrong? Let’s create a test scenario …
logdump output errors for tables with ROWDEPENDENCIES Read More »