My Oracle Support Banner

Tips For and Known Issues With The Database Migration Assistant for Unicode (DMU) Tool version (Doc ID 2018250.1)

Last updated on JUNE 14, 2024

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
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
Information in this document applies to any platform.

Purpose

To document known issues with the Database Migration Assistant for Unicode (DMU) Tool

For information about installing the DMU tool please see <note 1272374.1> The Database Migration Assistant for Unicode (DMU) Tool
If there are questions not answered please see point 5) Is DMU supported / how to get help? in <note 1272374.1> The Database Migration Assistant for Unicode (DMU) Tool

The latest version is DMU 23.1 which can be download here.

Check the FAQ page here , for additional details.

Questions and Answers

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
Purpose
Questions and Answers
 A) Things to check before using the DMU tool
 A.1) Purge the RECYCLEBIN before using the DMU tool
 A.2) Make sure your database has good statistics
 A.3) Check if the compatible parameter is set to your base version (recommendation - not mandatory)
 A.4) Check optimizer_features_enable setting.
 A.5) Can I simply do the conversion without testing on production? How long will scanning and/or conversion take?
 A.6) Check the source database for unneeded or problematic objects:
 A.6.a) Invalid objects.
 A.6.b) Orphaned Datapump primary tables
 A.6.c) Unneeded sample schema/users.
 A.6.d) Leftover Temporary tables using CHAR semantics.
 A.6.e) Make sure your database is in good health by doing an healthcheck.
 B) Often asked questions / seen issues:
 B.1) For some CHAR, VARCHAR2 , LONG or CLOB columns who store binary data (like PDF , doc, docx, jpeg, png , etc files) or encrypted data like hashed/encrypted passwords there are rows who have "Invalid Binary Representation".
 B.2) How to deal with Physical / Logical Standby databases?
 B.3) How much extra space do I need / Check if there is enough space before the conversion.
 B.4) Change , if needed, the MVIEW and Oracle Text index settings of the DMU tool .
 B.5) How to deal with "Invalid Binary Representation" in application data?
 B.6) How can i see all currently scheduled column modifications and/or "Assumed Characterset" set on column level?
 B.7) Do I need to run the dmu client on the database server / what do i need to stop to use DMU?
 B.8) Can i scan on a live/working database?
 B.9) What scan option should I choose for the first scan ever of a database?
 B.10) Check the DMU release notes , DMU requirements and the DMU FAQ
 C) Problems starting DMU or during scanning
 C.1) starting DMU on Microsoft Windows fails with error about a missing MSVCR100.dll
 C.2) starting ./dmu.sh fails with interpreter "/bin/bash" not found file link resolves to "/usr/bin/bash" ksh: ./dmu.sh:  not found ( or similar error)
 C.3) Starting DMU on windows 64bit gives " unable to create an instance of the Java virtual machine located at path <path>\jvm.dll"
 C.4) starting DMU gives "Bad version number in .class file" error.
 C.5) DMU does not accept the path to the java directory on unix systems on the "specify the full pathname of a J2SE installation" prompt
 C.6) Ora-01031: Insufficient Privileges when connecting with DMU
 C.7) DMU Failed to install the repository.
 C.8) What is the meaning of the "Flashback data archives exist in database" warning ( with orange bullet) in the migration status panel?
  C.9) "calculating the table split threshold " in dmu is very slow (popup in the scan wizard)
 C.10) ORA-29913: error in executing ODCIEXTTABLEOPEN callout (or other errors) on SYS.SYS_TZUV2_AFFECTED_REGIONS during scan
 C.11) ORA-00942: table or view does not exist during scan of the database.
 C.12) why is for some tables the "copy data as create table as select" conversion method not available ?
 C.13) Scan fails with ORA-01426 on some tables who have no rows (size is 0) and are created with deffered segment creation.
 C.14) DMU say's "there are partition keys in the database that contain columns defined with character length semantics" ).
 C.15) The scan of an EBS database "hangs" on ASO.ASO_ORDER_FEEDBACK_T
 C16) connecting with the DMU tool to the database "hangs" for a long time .
 D) "Invalid Binary Representation" or "Need conversion" for datadictionary objects after scanning the database ( DMU-00112 , DMU-00113 ,.. errors ):
 D.1) How to remove "Invalid Binary Representation" or "Need conversion" data in the SESSION_KEY column of SYS.REG$ or SYS.REGZ$ :
 D.2) How to remove "Invalid Binary Representation" or "Need conversion" in ERR_TEXT of CTXSYS.DR$INDEX_ERROR :
 D.3) How to remove "Invalid Binary Representation" or "Need conversion"  in TEXT column of SYS.ERROR$ :
 D.4) How to remove "Invalid Binary Representation" or "Need conversion" in QUERY_TXT Column of SYS.REG_SNAP$ (and SYS.SNAP_REFOP$(SQL_TXT), SYS.SNAP$(QUERY_TXT),  SYS.SUM$(SUMTEXT), SYS.SUMDEP$(VW_QUERY)) :
 D.5) How to remove "Invalid Binary Representation" or "Need conversion" in SYS.WRI$_ADV_SQLT_PLANS or SYS.WRI$_ADV_MESSAGE_GROUPS :
 D.6) How to remove "Invalid Binary Representation" or "Need conversion" in  SYS.SCHEDULER$_JOB_RUN_DETAILS :
 D.7) How to remove "Invalid Binary Representation" or "Need conversion" in NAME or DEFAULT$ column of SYS.COL$ :
 D.8) How to remove "Invalid Binary Representation" or "Need conversion" in SYS.TRIGGER$ :
 D.9) How to remove "Invalid Binary Representation" in COMMENT$ column of SYS.COM$ :
 D.10) How to remove "Invalid Binary Representation" in SOURCE column of SYS.SOURCE$ :
 D.11) How to remove "Invalid Binary Representation" AWR tables (WRI$_%, WRH$_%, WRR$_%)? (for example WRH$_ACTIVE_SESSION_HISTORY WRH$_SQLSTAT WRH$_SQLTEXT) :
 D.12) How to remove "Invalid Binary Representation" or "Need conversion" data in  SYS.CDEF$ :
 D13) How to remove "Invalid Binary Representation" or "Need conversion" data in SYS.DBMS_LOCK_ALLOCATED :
 D14) there is only "Need conversion" in SOURCE column of SYS.SOURCE$ but this is still blocking the conversion (= not having a green triangle):
 D15) How to remove "Invalid Binary Representation" or "Need conversion" or... data in SYS.TEMP_TEMP_SEG_USAGE
 
D16) How to remove "Invalid Binary Representation" or "Need conversion" in SYS.WRP$_REPORTS table
 E.1) DMU-00122 when choosing "Convert" in the dmu interface / ORA-12721 during conversion phase.
 E.2) Various errors and dmu "hanging" during conversion: Check UPFRONT if there is enough enough space in the tablespaces and on OS level.
 E.3) DMU asks again to scan a (part) of the dataset during the conversion phase, why?
 F) During the Post Conversion phase:
 F.1) DMU refreshes by default all read only Materialise views (MVIEWS) after conversion.
 F.2) Oracle Text index re-creation fails
 F.3) database alert file shows indexes marked as unusable:
 F.4) Oracle EBS ( APPS ) instances : Mview refresh fails with ORA-08002: sequence <name> is not yet defined in this session
 F.5) something hangs during Post conversion, how to interrupt?
 G) Steps to do after the migration to UTF8 or AL32UTF8 with DMU:
 G.1) Purge object statistics kept in Automatic Workload Repository
 G.2) Make sure all statistics are updated:
 G.3) Use Oracle SQL Developer to verify you data, not toad or sqlplus.
 G.4) Check for Invalid objects.
 G.5) if any of the post conversion actions in Database Properties: Converting tab was set to Generate SQL Script
 H) How to have an idea of what DMU is doing if it "hangs" and what to do?
 I) Can I remove / how to remove the DMU objects after conversion?
 J) How to see all objects that need action?
 K) I need to have the rowid's of the data in the database objects having convertibility issues like Invalid Binary Representation or an overview of the max expansion in bytes for columns that need adjustment due "Over Column Limit" or "Over Type Limit"
 L) Is there a command line interface for DMU.
 M) DMU reporting unconvertible data for EXP_HEAD$
 N) DMU unable to proceed due to character violation on SYS.PDB_SYNC$
References

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