LOGMINER LOB Writes Not Mined Correctly
Last updated on OCTOBER 01, 2012
Applies to:Oracle Server - Enterprise Edition - Version 10.2.0.1 to 18.104.22.168 [Release 10.2 to 11.2]
Information in this document applies to any platform.
The replication process using dbms_logmnr can result intermittently the SQL_REDO found in v$logmnr_contents for LOB_WRITE operations is incorrect. The SELECT statement that gets the lob locator contains the wrong data in the WHERE clause.
No errors are reported in the alert.log and no trace files are generated.
LogMiner is used to track all changes to production data and record them in a history database. When a LOB can't be mined accurately, the only workaround is to collect the current LOB from the production database. If the LOB has changed since the time of the original log miner failure, then the LOB update is lost forever. This impacts the functionality of the history application.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms