Skip Headers
Oracle® Database Migration Assistant for Unicode Release Notes
Release 1.1

 

   

Oracle® Database Migration Assistant for Unicode

Release Notes

1.1

October 2011

 

This document contains important information that was not included in the Oracle Database Migration Assistant for Unicode product-specific documentation for this release.

The product name Oracle Database Migration Assistant for Unicode is often abbreviated as DMU throughout this document, in other Oracle documentation and on Oracle Web sites.

This document may be updated after it is released. To check for updates to this document and to view other DMU documentation, refer to the Documentation section on the Oracle Technology Network (OTN) DMU Web site:

http://www.oracle.com/technetwork/database/globalization/dmu/documentation/index.html

This document contains the following topics:

1 Changes Between Releases 1.1 and 1.0.2

1.1 New Features in Release 1.1

2 Supported Configurations

The latest support information for Oracle Database Migration Assistant for Unicode is available on the OTN DMU Web site at:

http://www.oracle.com/technetwork/database/globalization/dmu/learnmore/index.html

in the document titled Supported Configurations.

3 Installation Instructions

The installation instructions for Oracle Database Migration Assistant for Unicode are available on the OTN DMU Web site at:

http://www.oracle.com/technetwork/database/globalization/dmu/learnmore/index.html

in the document titled Getting Started.

4 Requirements

4.1 General Database Requirements

The database must meet certain requirements to be supported by the DMU. These requirements are:

4.2 Database Convertibility Requirements

Additional requirements pertain to databases that the DMU should convert. Without meeting these requirements, the DMU can still be used for scanning and cleansing the database. The requirements are:

4.3 Database Space Requirements

The migration process requires free space in the database. The free space is required in the following areas:

5 Known Issues and Limitations

5.1 JDK on Windows 64-bit

The JDeveloper IDE platform on which the DMU is based requires a 32-bit JDK. If you point to a 64-bit JDK, when the DMU is started for the first time, you will get the error:

"Unable to find Java Virtual Machine. To point to a location of a Java Virtual Machine, please refer to the Oracle9i JDeveloper Install Guide (jdev\install.html)"

If this happens, go to the directory in which you installed the DMU, open the file dmu\dmu\bin\dmu.conf, and remove the line containing the keyword SetJavaHome. Then, restart the DMU and, when it asks for the JDK location again, enter the path to a 32-bit JDK6 installation.

5.2 Editing ANYDATASET Columns with Collections

The cleansing editor cannot properly display ANYDATASET columns containing varrays or nested tables.

To cleanse data in such columns, you need to update the problematic values or use larger built-in content types, depending on the reported issues. You can use the ANYDATASET and ANYDATA OCI and/or PL/SQL APIs to access, decompose, edit and rebuild ANYDATASET values.

See Also:

  • Oracle Database PL/SQL Packages and Types Reference for information on the ANYDATASET and ANYDATA Oracle-supplied types and their methods that comprise the ANYDATASET PL/SQL API

  • Oracle Call Interface Programmer's Guide for information on the OCIAnyDataSet and OCIAnyData interfaces that comprise the ANYDATASET C API

Note:

CLOB values cannot be embedded into persistently stored ANYDATASET and ANYDATA values. Therefore, embedded character values that exceed the 32767-byte length limit of VARCHAR2 embedded in ANYDATA cannot be cleansed by moving them to the CLOB data type. A workaround, such as using two VARCHAR2 attributes to store parts of a single character value, must be applied instead.

5.3 Immediate Column Modifications

After applying immediate column modifications on a column in the cleansing editor or modifying a column definition outside of the DMU, the scan results and scheduled cleansing actions for other columns of the same table will be reset during repository refresh. You will need to rescan all columns of the table and redefine any scheduled cleansing action for other columns of the same table.

5.4 LOB Segment Attributes

Due to RDBMS bugs #5577093, #5983283, and #6677390, LOB segments in tables converted by the conversion method "Copy data using CREATE TABLE AS SELECT" may lose the storage attribute RETENTION and get the storage attribute PCTVERSION. Use the SQL statement ALTER TABLE table_name MODIFY LOB (lob_name) (RETENTION) to restore the expected attribute.

5.5 Scheduled Cleansing from CHAR to VARCHAR2

When a scheduled cleansing action is defined to migrate a CHAR column to the VARCHAR2 data type, the scan results may incorrectly report over type limit issues even if the post-conversion length fits within the VARCHAR2 data type limit. If you can confirm that the post-conversion data size fits within the VARCHAR2 data type limit in the cleansing editor, then the workaround is to set the "Allow Conversion of Data with Issues" column conversion property to "Yes" so that the converison feasiblity test on this column can be bypassed. This issue is fixed in the database 11.2.0.3 release.

5.6 Column-level Character Set Tagging in Multibyte Databases

Due to a restriction in the DMU server-side data scanning function, the DMU does not allow character set tagging for character length semantics columns when the database character set is multibyte. If such tagging is necessary, please consider temporarily switching the column to byte length semantics for the duration of the migration.

5.7 Modifying Columns Used in Virtual Column Expressions

The DMU does not exclude columns used in virtual column expressions from cleansing actions that modify column definitions. Such modifications will result in the database error "ORA-54031: column to be dropped or modified is used in a virtual column expression."

5.8 Migration Parameter Settings

The DMU currently does not preserve changes to the following settings under the database property tab across different DMU sessions. If you altered any of these settings, you will need to restore them manually after reconnecting to the database.

6 Important Security Considerations

Unless you install the DMU on a host machine to which only you and appropriately authorized people have access, you need to take precautions to protect the DMU installation and the DMU configuration files. Otherwise, unauthorized access to the files could compromise security of the databases to which you connect with the DMU.

After you have uncompressed the archive file with the DMU installation, ensure that all uncompressed files and directories are writable only to you and other authorized operating system users. The DMU does not come with an installer that could set the file permissions automatically. Removing the write privilege from unauthorized users is very important because such users with access to the DMU host could modify the DMU files to make the DMU execute arbitrary SQL statements when the DMU is later started with SYSDBA credentials. Such SQL statements could compromise database security.

If you select the Save Password check box when creating a database connection, the password you specify is saved in an obfuscated form in a password file named cwallet.sso in your user directory. Because obfuscation is a reversible operation, use this feature only for passwords to test databases with no production data or only if the DMU is installed on a very well protected host. Ensure that the password file is readable only by you.

On Unix-based platforms, the file is in the directory $HOME/.dmu/. On Microsoft Windows, the file is in the directory %APPDATA%\DMU\.

This release of the DMU requires that you connect to a database specifying a database user with the SYSDBA privilege. This user will have full access to DMU repository objects. Do not grant any privileges on any of the DMU tables or PL/SQL packages to any database user, except in cases documented explicitly in the DMU documentation.

7 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.


Oracle Database Migration Assistant for Unicode Release Notes, Release 1.1

 

Copyright © 2011, 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 software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on 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. 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.