Avoid Unexpected Outputs Returned By LogMiner
(Doc ID 1934944.1)
Last updated on OCTOBER 11, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 8.1.5 to 12.1]
Oracle Database - Standard Edition - Version 22.214.171.124 to 126.96.36.199 [Release 8.1.5 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
How to avoid incorrect/incomplete/corrupted outputs returned by the LogMiner Utility?
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
|1. UNKNOWN or NULL outputs in V$LOGMNR_CONTENTS|
|2. Redo dump and SQL_REDO|
|3. Incorrect output when PRINT_PRETTY_SQL is used|
|4. 11g Optimization and LogMiner|
|5. Known defects related to LogMiner providing incorrect output|