Logminer Raises The Error "In Memory Undo is unsupported" When Selecting From v$logmnr_contents
(Doc ID 428167.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Q1: Why does the error "In Memory Undo is unsupported" appear when vselecting form v$logmnr_contents?
Q2: If the changes to supplemental logging were made, could we then read the transaction reads that were returning the UNSUPPORTED message?
Q3: Would enabling supplemental logging make the logminer able to read transaction records that were created before supplemental logging was enabled?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document