{"id":7263,"date":"2021-07-29T14:30:12","date_gmt":"2021-07-29T14:30:12","guid":{"rendered":"https:\/\/rax-stg-wp-aws.com\/blogs\/converting-a-12c-ebs-database-to-unicode-using-dmu\/"},"modified":"2026-11-03T19:28:21","modified_gmt":"2026-11-03T19:28:21","slug":"converting-a-12c-ebs-database-to-unicode-using-dmu","status":"publish","type":"blogs","link":"https:\/\/www.rackspace.com\/en-gb\/blogs\/converting-a-12c-ebs-database-to-unicode-using-dmu\/","title":{"rendered":"Converting a 12c EBS database to Unicode using DMU"},"content":{"rendered":"

This blog post describes how you can convert your client database running with a single-byte character set database, WE8ISO8859P1<\/em>, to a Unicode Character Database (UCD)<\/em>, AL32UTF8<\/em>, by using the Oracle Data Migration Assistant for Unicode (DMU) tool. <\/p>\n

To migrate Oracle\u00ae; Database 12.1.0.2 and R12.1.3 E-Business Suite\u00ae; (EBS) application file system character set databases from WE8ISO8859P1 to AL32UTF8, complete the following steps:<\/p>\n

1. Prerequisites Task
\n2. Install DMU, create the repository, and connect the DB into DMU
\n3. Scan the full Database
\n4. Cleanse Sys schemas and application schemas
\n5. Convert the database
\n6. EBS-related post-migration steps
\n7. Validate the UCD<\/p>\n

1. Prerequisite tasks<\/strong><\/p>\n

Perform the following tasks before starting the migration:
\n 
\n1. <\/strong>Take a complete backup of the DB and applications. Count the invalid details and disable DB force logging.
\n2.<\/strong> Run Purge RECYCLEBIN<\/em> and use the GATHER AUTO<\/em> option to gather statistics on e-Business schemas. Check the optimizer_features_enable<\/em> setting and correct it as needed.
\n3. Apply patch 28956851:R12.TXK.B (R12.1.3). <\/strong>Refer to Oracle Doc ID 393861.1.
\n4.<\/strong> Run AutoConfig on the Application node
\n5. <\/strong>Create the \/admin\/out\/appsutil.zip<\/strong> file on the application node by running the following command:<\/p>\n

         $perl $AD_TOP\/bin\/admkappsutil.pl<\/em><\/p>\n

6. Copy appsutil.zip<\/strong> to RDBMS ORACLE_HOME<\/strong> and run the following command:
\n 
\n          $unzip -o appsutil.zip<\/em>
\n 
\n7. Run adautocfg.sh<\/strong> on the DB node.
\n8. Run adautocfg.sh<\/strong> on the application node.<\/p>\n

 2. Install DMU, create the repository, and connect the DB into DMU<\/strong><\/p>\n

Perform the following steps to prepare to use the DMU:<\/p>\n

1. Execute the following commands as a SYS user:
\n 
\n        SQL> spool prvtdumi.log
\n        SQL> @?\/rdbms\/admin\/prvtdumi.plb
\n <\/em>
\n2. Run the following command to create a password file:
\n 
\n        NONPROD [oradi@nordlrbbnebsd01 dbs]$ orapwd file=$ORACLE_HOME\/dbs\/orapw$ORACLE_SID password=*****<\/em>
\n 
\n3. Download and install JDK if required.<\/p>\n

4. To launch DMU on a VNC session and create a database connection to the DMU tool, run the following command:
\n 
\n        $ sh dmu.sh<\/em>
\n 
\n5. Save the connection.<\/p>\n

\"12c<\/p>\n

 
\n6. Select the `Install the DMU repository` checkbox.
\n <\/p>\n

\"12c<\/p>\n

 
\n7. Click Next.<\/strong>
\n <\/p>\n

\"12c<\/p>\n

 
\n<\/br>
\n 
\nClick Next<\/strong> and then Finish<\/strong>.
\n <\/p>\n

\"12c<\/p>\n

 
\nThe preceding message displays after the repository installs successfully.
\n 
\n### 3. Scan the full Database<\/strong>
\n 
\nNow scan the data dictionary and the application schemas:
\n 
\n1. When you right-click on the DB connection name, you see the following navigation list to select and scan the database:
\n <\/p>\n

\"12c<\/p>\n

 
\n2. Click Next<\/strong>
\n <\/p>\n

\"12c<\/p>\n

 
\n  
\n3. Click Next<\/strong> to change the number of scanning processes and the scan size to speed up the DMU scan.
\n <\/p>\n

\"12c<\/p>\n

\n4. Click Finish<\/strong>
\n <\/p>\n

\"12<\/p>\n

 <\/p>\n

\"12c<\/p>\n

 The following screenshot shows the scan in progress:
\n <\/p>\n

\"12c<\/p>\n

 <\/p>\n

The following screenshot confirms the complete database scan:
\n <\/p>\n

\"12c<\/p>\n

 4. Cleanse sys schemas and application schemas<\/strong>
\n 
\nAfter scanning, you need to look at the data using the Database Scan Report<\/strong> 
\n <\/p>\n

\"12c<\/p>\n

Notice that your actual data shown in the DMU is in the following columns:
\n 
\n– Need no change<\/strong>: The data in this column does not require conversion.
\n– Need conversion<\/strong>: The DMU converts the data in this column.
\n– Invalid representation<\/strong>: You need to fix this before converting the database. Manually fix this data issue by using the – Cleansing Editor<\/strong> to edit the data.
\n– Over column limit<\/strong>: Use the Bulk Cleansing<\/strong> wizard. You can fix this by changing the VARCHAR2<\/strong> columns to use CHAR<\/strong> instead of BYTE<\/strong> semantics.
\n– Over type limit<\/strong>: Use SQL Developer or the Cleansing Editor<\/strong> wizard to fix this problem.
\n 
\nTo perform bulk cleansing, perform the following steps:
\n 
\n1. Right-click on the database connection and select the Bulk Cleansing<\/strong> option from the pop-up menu.
\n 
\n2. Run the Migrate to character length semantics<\/strong> option and check the results of the bulk cleansing. You also have the option to select a different parameter to clean the dirty data.
\n 
\n3. You can also refer to some tips for the issues and fixes related to DMU Doc ID 2018250.1.
\n 
\n4. You need to clear all the warnings before proceeding to the conversion steps. Sometimes you need to open a service request (SR) to confirm some issue or data purge during cleansing.
\n <\/p>\n

\"12c<\/p>\n

\n5. Convert the database<\/strong>
\n 
\n After fixing all the issues, right-click on the Database connection, select the Convert Database<\/strong> option, and click Convert<\/strong>. 
\n <\/p>\n

\"12c<\/p>\n

\n 
\nAccept all the defaults by clicking the Next.<\/strong> The Migration Status<\/strong> tab also shows the conversion status when it completes.
\n 
\nMigration in progress:   
\n <\/p>\n

\"12c<\/p>\n

\n 
\nMigration is complete as indicated by the Status<\/strong> panel:
\n <\/p>\n

\"12c<\/p>\n

\n 
\n6. EBS-related post-migration steps<\/strong>
\n 
\nThis section includes steps 3.1.4 through 3.3 from Doc ID 393861.1 Update Database Tier AutoConfig Context Files, Appendix A:
\n 
\n1. On the DB node, execute the following command and verify **NLS_LANG** is in the DB env file:
\n 
\n        $ perl txkSetUnicodeCharSet.pl <\/em>
\n 
\n2. On the Apps tier, execute the following commands:
\n 
\n        $ ls $ORACLE_CONFIG_HOME\/reports\/Tk2Motif_AL32UTF8.rgb
\n        \/u01\/app\/appdi\/DEV\/inst\/apps\/MKS_mksdbcs\/ora\/10.1.2\/reports\/Tk2Motif_AL32UTF8.rgb
\n        $ ls $ORACLE_HOME\/guicommon\/tk\/admin\/Tk2Motif_UTF8.rgb \/u01\/app\/appdi\/DEV\/apps\/tech_st\/10.1.2\/guicommon\/tk\/admin\/Tk2Motif_UTF8.rgb
\n        $ cd $ORACLE_CONFIG_HOME\/reports\/
\n        $ cp Tk2Motif_AL32UTF8.rgb $ORACLE_CONFIG_HOME\/reports\/Tk2Motif_AL32UTF8_backup.rgb
\n        $ grep -i fontMapCs Tk2Motif_AL32UTF8.rgb
\n        !Tk2Motif*fontMapCs: iso8859-2=EE8ISO8859P2
\n        Tk2Motif*fontMapCs: iso8859-1=UTF8
\n        $ vi Tk2Motif_AL32UTF8.rgb
\n        $ grep -i fontMapCs Tk2Motif_AL32UTF8.rgb
\n        !Tk2Motif*fontMapCs: iso8859-2=EE8ISO8859P2
\n        Tk2Motif*fontMapCs: iso8859-1=AL32UTF8<\/em>
\n 
\n3. Execute the following command and verify NLS_LANG<\/strong> is in the Application env file:
\n 
\n         $ perl txkSetUnicodeCharSet.pl<\/em>
\n 
\n4. Regenerate Forms and Reports through adadmin<\/strong>.
\n5. Regenerate Messages through adadmin<\/strong>.
\n6. Update the ICX:Client IANA<\/strong> profile option to UTF-8<\/em>.
\n 
\n7. Validate the UCD  <\/strong>
\n 
\nStart services and validate the application. It should work fine for you.
\n 
\nConclusion <\/strong>
\n 
\nThe Oracle DMU tool provides a streamlined solution for migrating a legacy single-byte character set database to a UCD. The DMU tool helps ensure all character data migrates correctly quicker and easier. It also ensures that the migration completes without any data loss and validates the data integrity of the databases. 
\n 
\nIf the Oracle EBS application has more than one language group, UCD is the only choice. Oracle recommends using Unicode as the database character set for maximum compatibility and extensibility. The UCD character set supports all frequently used languages. It also supports symbols like the Euro sign, smart quotes, and scientific and musical notations. The IT industry is using UCDs more and more every day.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Converting a 12c EBS database to Unicode using DMU<\/p>\n","protected":false},"author":2,"featured_media":7265,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","format":"standard","meta":{"content-type":"","nid":"26346","content_type":"blog","created_by":"10130","authored_on":"2023-12-05T15:30:12+00:00","field_article_industries":"","tag_category":"Technical","field_blog_author_text":"by Rackspace Technology Staff","seo_description":"Execute domestic ACH payments efficiently using NACHA files and leverage Oracle R12's support for mass payment batches with ease.\r\n","field_featured_image":"","insights_image":"\/wp-content\/uploads\/2026\/blog_technical_images\/26346-insights_image-oracle-technical-blog-1-insights.jpg","field_partners":"","rxt_platforms":"Oracle","product":"","publisheddate":"2021-07-29T14:30:12","rxt_solutions":"Databases","opengraph_tag":"","x_tag":"","teaser_flag":"Technical Blog","seo_titile":"12c EBS Database Unicode Conversion with DMU | Rackspace","field_topics":"","field_slug":"converting-12c-ebs-database-to-unicode-using-dmu","footnotes":""},"categories":[178],"tags":[204],"class_list":["post-7263","blogs","type-blogs","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-technical"],"_links":{"self":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs"}],"about":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/types\/blogs"}],"author":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/comments?post=7263"}],"version-history":[{"count":2,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7263\/revisions"}],"predecessor-version":[{"id":9300,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7263\/revisions\/9300"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/media\/7265"}],"wp:attachment":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/media?parent=7263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/categories?post=7263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/tags?post=7263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}