Oracle LogMiner Continuous Mining Deprecation: What You Need to Know

3 Minute Read

Striim for Oracle CDCIn this era of digital transformation, companies are shifting to the cloud to increase their agility and shorten the time to business insights. Oracle databases have long been entrusted with operational data, and various methods have emerged to replicate or migrate data to cloud targets. 

Change Data Capture (CDC) tracks database changes as they happen and generates a continuous stream of change data. Oracle CDC methods allow companies to stream database changes to their cloud targets in real time, enabling timely business intelligence and zero-downtime cloud migrations.

Various CDC approaches have been developed over the years to facilitate real time business operations.

“Efficient and reliable log mining techniques are critical for real time business operations. As database log-mining approaches continue to evolve, data architects need to incorporate low latency methods to stream changes from mission critical database workloads.”
-Alok Pareek, Founder at Striim, former CTO at GoldenGate

Oracle CDC methods include LogMiner-based CDC, trigger-based CDC, and third-party tools like Striim. Here’s a brief overview of these methods:

1. Oracle LogMiner-based CDC

LogMiner provides a SQL-based interface to Oracle database redo log files. LogMiner is designed to help users track data corruption (and identify any required recovery actions) and carry out performance tuning and capacity planning. 

The LogMiner “continuous mine” feature was introduced to allow automatic, continuous mining of the redo logs. This feature provides near real-time access to redo log changes, which has made it the target for many third-party data integration tools that offer CDC from Oracle.

Recently, Oracle announced that continuous mine would be deprecated in Oracle Database 19c. For that reason, companies using newer versions of Oracle can no longer use the continuous mine feature for CDC.

2. Trigger-based Oracle CDC

Trigger-based Oracle CDC, also known as “synchronous” CDC, starts with defining database triggers that fire before or after INSERT, UPDATE, or DELETE commands (that indicate a change). The change data is used to populate a change table. Each table requires its own change table.

Trigger based Oracle CDC
Image source: Oracle documentation

Triggers introduce overhead to operational tables while changes are being made, and can have significant performance impacts on any applications accessing the tables. Furthermore, maintaining the triggers as the application changes leads to management burden.

3. Striim for Oracle CDC

Striim is a real-time data integration platform that natively performs change data capture by mining Oracle redo logs while managing additional metadata.

Striim for Oracle CDC

Striim’s Oracle CDC solution offers a variety of benefits:

  • It does not require the LogMiner continuous mining feature (and has a 3x faster capture rate than LogMiner-based CDC)
  • It can also read Oracle GoldenGate Trail files (for companies who are using Oracle GoldenGate)
  • It is RAC-cluster compatible
  • It offers high-speed, error-free, high-performance change data capture (with exactly once processing and support for long-running transactions)
  • It’s an end-to-end data integration tool with real time monitoring, analysis, and enrichment; and connectors to over 100 sources/targets 
  • It’s designed for mission critical, high-volume environments

Striim offers Oracle CDC to Snowflake, Kafka, BigQuery, Azure SQL database and many more targets.

If you’re looking for a high-performance alternative to LogMiner-based or trigger-based Oracle CDC, one of Striim’s CDC experts would be happy to give you a personalized walkthrough of the Striim platform. Alternatively, you can give Striim a try for free.