My Oracle Support Banner

How to Restore SQL_REDO and SQL_UNDO from V$LOGMNR_CONTENTS When Statements are Longer Than 4000 Bytes (Doc ID 987013.1)

Last updated on SEPTEMBER 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 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.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


You start Logminer to obtain the statements from archived or online redo logs and need to run SQL_REDO or SQL_UNDO statements against the existing tables. You observed that the statements are longer than 4000 bytes (maximum column length for SQL_REDO/UNDO in view V$LOGMNR_CONTENTS). How can you get them completely?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.