"Unsupported" Entries in V$LOGMNR_CONTENTS For SQL_REDO and SQL_UNDO When Mined Objects Contain JSON Column
(Doc ID 2945532.1)
Last updated on APRIL 28, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
When using ad-hoc LogMiner (i.e. the DBMS_LOGMNR API) to mine redo for tables with columns that have JSON attributes in an extended varchar2 environment (MAX_STRING_SIZE=EXTENDED), the SQL_REDO and SQL_UNDO columns show 'Unsupported'.
A simple test case that illustrates the issue is:
If max_string_size=STANDARD, this issue does not occur.
Cause
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
Symptoms |
Cause |
Solution |
References |