Premium

Java Certification Latest FAQ



Question: Can I use the DMU if my database version is not listed in the supported configurations?

Answer:In order to use DMU, a database patch must be installed to add server-side migration functionality required by DMU. The patch is currently only available for the supported configurations. If your database version is not in the list, please consider upgrading to one of the supported releases.


Question: Which JDK version is required to run the DMU client? JDK 6 or 7. Question: Can I run the DMU client remotely to migrate the database?

Answer:While DMU can be run remotely from a different machine, it is highly recommended to run it locally on the same host as the database server to be migrated for faster performance and reducing network overhead. It is also recommended to run the database in dedicated server mode during migration.


Question: What are the hardware requirements for a database server to migrate a database with the DMU?

Answer:Migration to Unicode is a resource-intensive operation especially for migrating large-scale databases. It is recommended to perform the migration on sufficiently configured hardware to maximize the migration throughput. The exact hardware requirements vary depending on the size of the database and the targeted down-time window, but it is advisable to have a minimum of 8 CPU cores and 16GB memory for migrating databases of 100GB or above.


Question: What are the hardware requirements for running the DMU client?

Answer:Oracle recommends that you run the DMU client on the same host as the database server to be migrated to minimize network overhead. If you must run the DMU client on a different host, the minimum hardware requirements are: CPU speed - 2GHz, Memory - 4GB RAM. Avoid having other jobs running in the same environment if they consume significant system resources.

Related Questions


Question: I set the JDK location incorrectly when starting the DMU. How can I change the JDK location?

Question: What is the recommended strategy for cleansing invalid data?

Question: What is the recommended strategy for cleansing data expansion issues?

Question: What are the DMU conversion criteria for the data dictionary?

Question: How to deal with convertible data in AWR tables (WRI$_%, WRH$_%, WRR$_%)?

Question: Why do I get warnings for modifying columns under the Oracle E-Business Suite schemas?

Question: I just removed the characters causing invalid binary representation in my CLOB data cells in the cleansing editor. Why are they still highlighted as exceptions?

Question: How does the DMU report data cells that exhibit both invalid binary representation and size expansion issues?