PeopleSoft PeopleTools 8.

55 and Above

Converting to Unicode on Oracle

Databases Using Database Migration
Assistant for Unicode

February 2017
PeopleSoft PeopleTools 8.55 and above Product Documentation Update: Converting to Unicode on Oracle
Databases Using Database Migration Assistant for Unicode
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS:
Oracle programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer
software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any
operating system, integrated software, any programs installed on the hardware, and/or documentation, shall
be subject to license terms and license restrictions applicable to the programs. No other rights are granted to
the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Product Documentation Update Converting to Unicode on Oracle Databases Using Database Migration Assistant for Unicode
2017

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 3

Product Documentation Update Converting to Unicode on Oracle Databases Using Database Migration Assistant for Unicode
2017

Introduction
You can maintain the application data, reports, user interface components, and other linguistic elements of
the PeopleSoft system in many languages in a single database using Unicode to create the database.

Converting to Unicode on Oracle Databases Using

Database Migration Assistant for Unicode
If your database supports it, you can convert your databases to Unicode using Database Migration
Assistant for Unicode (DMU). It is a faster method than exporting and importing the non-Unicode files.
You will need a minimum Apps version of 9.0, Tools version of 8.48, and DMU version of 2.0.

Note: A user with SYSDBA privilege, such as SYS can connect the DMU client to the database.

The database will need the PL/SQL package prvtdumi.plb, for instance:

sqlplus / as sysdba

SQL>@?/rdbms/admin/prvtdumi.plb

Note: Java SE Development Kit (JDK) is required to run the DMU client. The main DMU documentation has
details of the JDK.

To convert the database in Unicode using DMU:

1. Verify the configuration requirements for DMU and install the required patches.
a. Verify if the database and the operating system supports the current DMU release.
b. Check for any restrictions for the databases to be migrated in the DMU Release Notes.
c. Install required database patch. You can download the patch from My Oracle Support.
d. Install the PL/SQL package in the database.
e. Install Oracle XML DB component (XDB) in your database.

Note: You can check if a valid XDB is installed in your system. To check, enter following in the command
prompt:

select comp_id, status from dba_registry;

If you do not have XDB then to install XDB, enter the following in the command prompt:

4 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Product Documentation Update Converting to Unicode on Oracle Databases Using Database Migration Assistant for Unicode
2017

run catqm.sql, for instance as catqm.sql xdb SYSAUX TEMP NO.

2. Setup the client for DMU and connect to the database:

a. Install the JDK version required for the DMU version.

Note: Make a note of the directory where you installed JDK. You will need to provide the path to it in the
DMU.

b. Install the DMU software from Oracle Technology Network download page.
c. Start the DMU. When you start the DMU for the first time, it asks for the JDK installation
directory.
d. Create a database connection. Enter user Id, password and the network connection data of the
database administrator; the target database host name, the TNS listener port, and the database.

Note: Before connecting to the DMU client, grant SYSDBA privilege to your user using a password file from
orapwd utility.

For Windows, this file must be named ORACLE_HOME\database\PWD<ORACLE_SID>.ora, and for Unix
this file must be named ORACLE_HOME/dbs/orapw<ORACLE_SID>.
3. Run the Unicode migration in DMU:
a. Install the DMU repository.

Note: DMU will prompt you to update the NLS_LENGTH_SEMANTICS in init.ora at the end of the
conversion.

b. Start the migration process of the database to Unicode. The utility guides you through the three
steps to Scan, Cleanse, and Convert.
c. Validate that the character set in the database is in Unicode.
4. Set NLS_LENGTH_SEMANTICS=CHAR in your init.ora and restart your database. PeopleSoft Unicode
databases use character length semantics.
5. Run Audit:
Run the audits such as DDDAUDIT, SYSAUDIT, and an Alter Audit.

Note: With DMU versions before 2.1.2, any tables reported in the alter audit should be rebuilt in Application
Designer to ensure that fields defined as LONG are implemented as CLOB when needed. With DMU 2.1.2
and later, the alter audit should show that no changes are needed.

If you use the DMU method, you don’t need to rebuild tables and indexes, or do imports, unless tables are
reported in the alter audit. After the migration, the character set will be AL32UTF8, and the VARCHAR2
columns lengths will specify the number of characters instead of the number of bytes. For instance “descr
psmsgcatlang” will show that message_text is varchar2(100 char).

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 5

Product Documentation Update Converting to Unicode on Oracle Databases Using Database Migration Assistant for Unicode
2017

For more information about the Oracle Database Migration Assistant for Unicode on supported configuration,
DMU documentation, and accessing DMU client for download, access the Oracle Technology Network:
http://www.oracle.com/technetwork/database/database-technologies/globalization/dmu/learnmore/start-
334681.html.

6 Copyright © 2017, Oracle and/or its affiliates. All rights reserved.