DMU Scan - Taking Long Time To Come Back After Scanning Individual Table due to more data in SYSTEM.DUM$EXCEPTIONS table
(Doc ID 2365483.1)
Last updated on JULY 27, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
While doing DMU scanning on a very large database database more rows inserted into DUM$EXCEPTIONS table.
Below pl/sql is calling and running 10 minutes for every statement when fixing the data for each table using DMU
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