DMU Scan - Taking Long Time To Come Back After Scanning Individual Table due to more data in SYSTEM.DUM$EXCEPTIONS table
Last updated on APRIL 17, 2018
Applies to:Database Migration Assistant for Unicode - Version 1.2 and later
Oracle Database - Enterprise Edition - Version 220.127.116.11 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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms