Troubleshoot the Migration Process
Database Migration Workbench reviews and informs at several steps during the process that all prerequisites, requirements, databases, and schema are met, available, and ready. Should an issue or error come up during the Database Migration Workbench process this section can help you troubleshoot your migration.
The following table is a list of the most common migration issues and potential solutions:
| Issue | Reason | Category | Workaround | Database Version |
|---|---|---|---|---|
| Upload dump file step generates error because the agent is down. | The agent may have run out of memory. Review the log files. | EM Agent | You can update the degree of parallelism within the failed step to a lower number and retry. Pending files will upload. | All |
| Creation of Table Space fails at destination Autonomous Database | Autonomous Databases do not allow Table Space creation with small Data Files | ADB | Create a tablespace at the destination ADB with a large data file and specify remap_tablespace.
|
All versions |
| Creation of schema fails at destination ADB | The user profile does not get created at the destination ADB, causing schema creation failure.
Data Pump does not export Profiles when not run in |
ADB | Pre-create profile at the ADB, or use remap_schema.
Example:
|
All versions |
Export failed because of error: DETERMINE_FATAL_ERROR with ORA-20005: object statistics are locked (stattype = ALL) |
Tables used for statistic gathering are blocked. | Data Pump | Unlock the tables for statistics using the command: SQL> exec dbms_stats.unlock_table_stats('owner', 'tablename');To get a list of tables that are locked you can execute: |
All versions |