50 likes | 59 Views
Oracle Change Data Capture is a technology that identifies modified data (added, updated, or deleted) from Oracle database, captures the changes, and integrates them into applications. It is based on the concept of publishers and subscribers where publishers are the users of Oracle who publish the changes and the subscribers are the applications or individuals that use or subscribe to the changed data.
E N D
Oracle Change Data Capture is a technology that identifies modified data (added, updated, or deleted) from Oracle database, captures the changes, and integrates them into applications. It is based on the concept of publishers and subscribers where publishers are the users of Oracle who publish the changes and the subscribers are the applications or individuals that use or subscribe to the changed data.
This post will deal with the many intricacies of implementing Oracle CDC (Oracle Change Data Capture) and how data is copied to various target databases in real-time. • Oracle is a proprietary database management system used to run transaction processing, warehousing, or mixed loads. There are, of course, various open-source platforms that can carry out the same activities but Oracle is in a league of its own. It has a powerful querying layer with enterprise-grade security, advanced analytical functions, access controls, and support, all of which have made it a favorite for crucial enterprise transactional workloads. The rise in approval for open-source distributed data warehouse systems has resulted in a situation where a mix of Oracle-based transactional database and a separate data warehouse is very common in enterprise ETL stack.
Types of Oracle CDC · Synchronous Change Data Capture – A synchronous Oracle CDCis implemented using triggers that inserts entries to a change-table whenever data is modified. Triggers are points that get activated as part of the transactions. The first step is creating a user to act as the change data publisher. The user should have access to namespace and the table at source from which the changes are to be captured. The next step in the exercise is to create a change set and table and subscribe to the changes. To carry out this process, that is copy data to the destination database, a script has to be used that can process these records and insert data to the target database. A disadvantage here is that triggers affect the performance of the source database. To get around this issue, there is another alternative to implement Oracle CDC. · Asynchronous Change Data Capture – Asynchronous Oracle CDC is done using redo logs. Redo logs are ones that keep a record of all the activities in a database without any drop in speed or performance. Configuring Oracle CDC can be a long process with specific set of challenges. However, the following steps can help make the whole activity quick and efficient. · Several configuration changes and user permission changes need to be done to initialize and complete it. · Oracle CDCrevolves only around enabling and capturing change data and developers have to implement the logic for processing the change data and inserting into the target databases. • · The admin must have expert Oracle and programming skills to implement the logic. However, database administrators don’t need to go the manual route. Technologically advanced tools can automate the whole process and ensure that Oracle CDC goes off without a hitch.