Documentation Accessibility

Oracle Migration Workbench Release Notes Release 10.1.0.4 for Microsoft Windows 98/2000/NT/XP and Linux x86 B19131-01 June 2005 This document contains the following topics: Documentation Accessibility Introduction What s New in Oracle Migration Workbench Setting Up Migration Workbench Installing Migration Workbench Configuring Migration Workbench to Use the Default Browser Using a Workbench Repository Created by a Previous Release Removing the Migration Workbench Documentation Updates Problems and Considerations Documentation Accessibility Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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. 1

TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398. Introduction Oracle Migration Workbench (Migration Workbench), Release 10.1.0.4 for Microsoft Windows 98/2000/NT/XP and Linux x86 enables you to migrate the following databases to an Oracle10g or Oracle9i database: IBM DB2/AS400 V4R3, V4R5 IBM DB2 UDB 6, 7 IBM DB2 UDB migration is supported on UNIX and NT systems. It is not supported on Z/OS, OS/390, or iseries systems. Informix Dynamic Server 7.3, 9.x Microsoft Access 2.0, 95, 97, 2000, XP (2002), 2003 This release of Migration Workbench also allows you to migrate a Microsoft Access database to an Oracle Lite database. Microsoft SQL Server 6.5, 7.0, 2000 MySQL 3.22, 3.23, 4.x Sybase Adaptive Server 11, 12 Migration Workbench, Release 10.1.0.4 for Linux enables you to migrate the following databases to an Oracle Database 10g or Oracle9i database: Informix Dynamic Server 7.3, 9.x MySQL 3.22, 3.23, 4.x Sybase Adaptive Server 11, 12 Purpose of this Document This document outlines how to install Migration Workbench. For more information about Migration Workbench, see the following documentation: Oracle Migration Workbench Online Help Oracle Migration Workbench User s Guide Oracle Migration Workbench Reference Guide for Informix Dynamic Server Migrations Oracle Migration Workbench Reference Guide for Microsoft Access Migrations Oracle Migration Workbench Reference Guide for Microsoft SQL Server and Sybase Adaptive Server Migrations Oracle Migration Workbench Reference Guide for MySQL 3.22, 3.23, 4.x Migrations Oracle Migration Workbench Reference Guide for IBM DB2/400 V4R5 Migrations Oracle Migration Workbench Reference Guide for IBM DB2 UDB Migrations Oracle Migration Workbench Frequently Asked Questions (FAQ) 2

Terminology The following operating systems have been shortened in this guide to Windows, where appropriate: Microsoft Windows 98 Microsoft Windows NT 4.0 Microsoft Windows 2000 Microsoft Windows XP The name for the UNIX operating system, Red Hat Enterprise Linux 3, has been shortened in this guide to Linux x86, where appropriate. What s New in Oracle Migration Workbench This section describes new features of Migration Workbench Release 10.1.0.4 and provides pointers to additional information. Microsoft Access Plug-in and Exporter Enhancements The Microsoft Access plug-in now supports migrations from Microsoft Access XP (2002) and 2003, in addition to the other previously supported versions. The plug-in also now supports the migration of Microsoft Access queries to Oracle views. Several changes have been made to the Exporter tool, which generates XML files representing the database schema and table data for Microsoft Access databases. You can now simultaneously export multiple MDB files into a single schema or multiple schemas. The usability of the tool has also been enhanced. For information about how to use the Exporter tool, see the online help available within the tool. IBM Informix Dynamic Server Plug-in Updated The Informix Dynamic Server plug-in now supports migrations from Informix Dynamic Server 7.3, 9.1, 9.2, 9.3, and 9.4. It also supports the migration of collection data types and sequences. The procedural language parser has been updated to accommodate the migration of these additional objects. The following subsections describe additional changes in more detail. Row Data Support This release supports the migration of row data types (NAMED and UNNAMED) in Informix Dynamic Server tables, and it includes the following features: Row data types can be migrated to Oracle object data types. The name of a generated object data type can be changed. Nested row types are supported. Collection data types nested within a row type can be migrated, but you must use the online data migration capability. The following basic data types are supported as row field data types (including nested row types): CHAR DATE 3

DATETIME DECIMAL FLOAT INT8 INTEGER MONEY NCHAR NVARCHAR SMALLINT SMALLFLOAT VARCHAR The LVARCHAR (size less than 4000) opaque data type is supported as row data types (excluding nested row types). The following data types are not supported as row data type fields: Opaque data types (including built-in opaque data types such as BOOLEAN, BLOB, and CLOB) User-defined data types INTERVAL SERIAL, SERIAL8, BYTE, and TEXT. (In Informix, these data types are not supported as field types in unnamed row types or in named row types that are to be used as a column type in a table.) Sequence Support This release supports the migration of Informix Dynamic Server sequences to Oracle sequences. SQL Statement Support SQL statements: CASE SPL and CALL SPL statements This release supports the following additional support for CREATE FUNCTION support for the INTO keyword EXECUTE FUN CTION statement in an Informix SPL body TRUNCATE statement CREATE TABLE and CREATE VIEW support for the AS TYPE clause T-SQL Parser Enhancement The T-SQL parser has been improved to generate clearer, more concise PL/SQL code by default. This code is easier to read, maintain, and test. Advanced parse options can be specified in either the Source Model or Oracle Model. Using the Sybase Adaptive Server jconnect 5.5 for JDBC Driver Migration Workbench for Linux uses the jconnect 5.5 for JDBC driver to connect to Sybase Adaptive Server. For more information about downloading and using this driver, see the Oracle Migration Workbench User s Guide. 4

Usability and Performance Enhancements Several enhancements have been made to reduce the effort required to complete a migration and to improve the performance of the Migration Workbench. Setting Up Migration Workbench Before you install Migration Workbench, review the Hardware Requirements and Software Requirements topics. Hardware Requirements Migration Workbench has the following minimum and recommended hardware requirements: Personal computer based on an Intel 80486 processor or higher. A minimum of Pentium 233Mhz processor is recommended 128MB RAM (256MB recommended) 65MB hard disk space for the installation of Migration Workbench and its dependencies VGA video (SVGA is recommended) Microsoft Windows 98/2000/NT/XP or Linux x86 compatible network adapter Software Requirements Migration Workbench has minimum and recommended software requirements. To migrate a plug-in, it is recommended that you have the following: Microsoft Windows NT 4.0 (Service Pack 6.0a), Microsoft Windows 98/2000/XP, or Red Hat Enterprise Linux 3 At least 30MB of space available in the tablespace where you create the Workbench repository. You should create a separate default tablespace for the user of the Workbench repository The following table lists the version of each component that is used by Migration Workbench: Component Version Olite database 5.0.2.0.0 EWT 3.4.29 Oracle Help for Java 4.2.5 Java Runtime Environment (JRE) 1.4.2_04 Java Database Connectivity (JDBC) JDK 1.2/1.3 Kodiak 1.2.1 XML Parser 9.2.0.5.0 ICE browser 5.06.10 5

Installing Migration Workbench After you download the Migration Workbench, you can install it on Windows or Linux x86. The following sections describe the installation process: Windows Installation Linux x86 Installation Windows Installation To install Migration Workbench on Windows: Task 1: Download Migration Workbench and Plug-in Download Migration Workbench and the plug-in for the database that you want to migrate from the Oracle Migration Workbench Web site: http://www.oracle.com/technology/tech/migration/workbench/index.ht ml Note: To install Migration Workbench, you need an unzip tool. The Oracle Migration Workbench Downloads page provides specific instructions about how to download the Migration Workbench installation (omwb.zip) file and the relevant plug-in (plug-in.jar) file. Task 2: Installing Migration Workbench and Plug-in Migration Workbench provides a user interface, including wizards, that help you migrate third-party databases to an Oracle database. Individual plug-ins are available to migrate different third-party databases to an Oracle database. To install Migration Workbench and plug-in for the database that you want to migrate: Note: You must install at least one plug-in with Migration Workbench. 1. Start Microsoft Windows. 2. Log on to the system as a member of the Administrators Group. 3. Unzip the omwb.zip file to the directory where you want to install Migration Workbench. Note: The remainder of this document uses OMWB_install_dir to represent the directory location in which Migration Workbench was installed. For example, if you unzipped Migration Workbench to c:\omwb1010, OMWB_install_dir is the c:\omwb1010 directory. 4. Copy the plug-in.jar file to the OMWB_install_dir\Omwb\plugins directory. 6

See Also: For information about using Migration Workbench, see the Oracle Migration Workbench User s Guide. Linux x86 Installation To install Migration Workbench on Linux x86: Task 1: Downloading Migration Workbench and Plug-in Download Migration Workbench and the plug-in for the database that you want to migrate from the Oracle Migration Workbench Web site: http://www.oracle.com/technology/tech/migration/workbench/ Note: To install Migration Workbench, you need an unzip tool. The Oracle Migration Workbench Downloads page provides specific instructions about how to download the Migration Workbench installation (omwb.zip) file and the relevant plug-in (plug-in.jar) file. Task 2: Installing Migration Workbench and Plug-in Migration Workbench provides a user interface, including wizards, that help you migrate third-party databases to an Oracle database. Individual plug-ins are available to migrate different third-party databases to an Oracle database. To install Migration Workbench and plug-in for the database that you want to migrate: Note: You must install at least one plug-in with Migration Workbench. 1. Open a terminal session on Linux x86. 2. Unzip the omwb.zip file to the directory where you want to install Migration Workbench. Note: The remainder of this document uses OMWB_install_dir to represent the directory location in which Migration Workbench was installed. For example, if you unzipped Migration Workbench to /home/user/omwb1010, OMWB_ install_dir is the omwb1010 directory. 3. Copy the plug-in.jar file to the OMWB_install_dir/Omwb/plugins directory. See Also: For information about using Migration Workbench, see the Oracle Migration Workbench User s Guide. 7

Configuring Migration Workbench to Use the Default Browser To view Migration Workbench HTML files, such as the Quick Tour, Migration Workbench attempts to activate the default browser on a Windows system. However, Migration Workbench does not know the name or path of the default browser. It relies on the Windows or Linux x86 file associations to activate the browser, if one exists. To avoid any Web browser problems, Migration Workbench uses the state.properties file to specify the exact path of the system browser. The state.properties file is automatically generated the first time you launch Migration Workbench. If there is a problem executing the browser command on a Windows or Linux x86 system, you receive the following error message: Problem executing Browser command command executed. Please specify the browser path in the c:\omwb1010\omwb\state.properties initialization file for the BROWSER_PATH property, then restart the Migration Workbench. For more information please read the release notes. To ensure that Migration Workbench launches the correct browser, edit the state.properties file as follows: 1. Close Migration Workbench. 2. Navigate to the following directory: On Windows: OMWB_install_dir\Omwb\bin On UNIX: OMWB_install_dir/Omwb/bin 3. Open the state.properties file. 4. In the BROWSER_PATH section, enter the exact path of the browser Migration Workbench should use. For example: On Windows: c:\program Files\Netscape\Communicator\Program\Netscape.exe On UNIX: user/local/bin/mozilla 5. From the File menu, select Save, then close the file. 6. Restart Migration Workbench for the changes to take effect. Using a Workbench Repository Created by a Previous Release This release of Migration Workbench does not support Workbench repositories created by previous releases of Migration Workbench. If you log in to the current release of Migration Workbench with a Workbench repository user from an earlier release, you cannot continue unless you re-create the Workbench repository. Re-creating the Workbench repository deletes all information from the 8

earlier version. Oracle recommends that you create a specific Workbench repository user account, for example, REPUSER. For more information about creating the REPUSER account, see the Oracle Migration Workbench User s Guide. Removing the Migration Workbench To remove this release of Migration Workbench, delete the entire Migration Workbench installation directory OMWB_install_dir. No other action is required. Note: For Migration Workbench Release 9.2.0.16 or earlier, use Oracle Universal Installer to remove the product. Documentation Updates The following Migration Workbench documentation is updated for this release: Online help for the Migration Workbench user interface, including information specific to the following plug-ins: Microsoft Access, Microsoft SQL Server and Sybase Adaptive Server, and Informix Dynamic Server Online help for the Exporter tool for Microsoft Access Oracle Migration Workbench User s Guide Oracle Migration Workbench Frequently Asked Questions (FAQ) Reference Guide for Microsoft Access Migrations Reference Guide for Microsoft SQL Server and Sybase Adaptive Server Migrations Reference Guide for Informix Dynamic Server Migrations Problems and Considerations To report a problem, see the instructions in the Oracle Migration Workbench Support Web site at: http://www.oracle.com/technology/support/tech/migration/workbench/ This section contains the following topics: Migrating a Microsoft Access Database to Oracle10g Lite Multi-level Linked Tables in Microsoft Access Informix Dynamic Server Migration Issues Open Bugs Migrating a Microsoft Access Database to Oracle10g Lite If you use the default repository (Oracle Lite) to migrate a Microsoft Access database, and if you later click Action > Modify Microsoft Access Database and try to link the Microsoft Access database with an Oracle10g Lite database, the following error will occur: Unable to connect to target database. java.sql.sqlexception: Specified driver could not be loaded due to system error 127 (Oracle Lite 40 ODBC Driver). 9

Instead, to migrate a Microsoft Access database to Oracle10g Lite, follow these steps: 1. Use an Oracle9i or Oracle10g database as the Migration Workbench repository. (That is, do not use the default Oracle Lite repository.) 2. Migrate the schema and the table data to Oracle10g Lite. 3. Exit the Migration Workbench. 4. Start the Migration Workbench. 5. Click Action > Modify Microsoft Access Database and link the Microsoft Access database with an Oracle10g Lite database. Multi-level Linked Tables in Microsoft Access Migration Workbench only supports one level of linked tables. If you have a table with links to a second table, these links are preserved. However, links in the second table are not migrated to Oracle. Informix Dynamic Server Migration Issues The following issues and considerations apply to Informix Dynamic Server migrations: Opaque data types and user-defined types are not supported as the field of a row type. When you use offline scripts to move data, table data having a NULL value (atomic null) for any of its row type columns, or having any row data type columns with an atomically null nested row type, will not be migrated correctly. A row typed table is not supported. Such tables will be migrated to untyped tables. Migrated sequences in Oracle will have a starting value taken from the START WITH option (specified or default value) when the sequence was created in Informix Dynamic Server; they will not have their current value. To use the current values, you must obtain the current values from Informix Dynamic Server, and either specify these values as starting values for sequences or (after the migration) drop the sequences and re-create them with the desired starting values. Opaque, row type (named or unnamed), and UDT are not supported as collection elements. The maximum size for the VARRAY type is 100 by default; however, you can change this value during the migration. If you use an offline script to move complex data with date elements, date column formats other than MM/DD/YYYY are not supported. Either use the online Migration Workbench interface, or modify the SQL*Loader control (.ctl) file for the affected tables before performing the load operation. For offline capture of the Source Model from an Informix Dynamic Server database, use the appropriate script file. The file name and location depends on your Informix Dynamic Server release number, as explained in the 10

chapter on disconnected source model loading in Oracle Migration Workbench Reference Guide for Informix Dynamic Server Migrations. If you convert script files for offline capture to UNIX, you must create offline capture files in Linux x86, not Windows. Open Bugs The following are known issues with this release of Migration Workbench: Bug 2751529 - Database Names That Contain Special Characters Do Not Work If a database name in the source database contains special characters, such as a dash (-), Migration Workbench cannot extract that database. Workaround To migrate a database name that contains special characters: 1. Create a database with a name that does not contain special characters. 2. Copy the schema and data from the database containing special characters to the new database. Bug 3213619 - In Stored Procedures and Trigger T-SQL Code, DBO is Mapped to Unknown The user dbo is set to unknown in the T-SQL code of stored procedures and triggers. Workaround Before migrating, edit the PL/SQL text in the Oracle Model to reset the user dbo to the required value. Bug 3246470 - Two Instances of Migration Workbench Might Cause Uniqueness Problems Two instances of Migration Workbench running at the same time may create problems. For example, if you create a tablespace with the name TABSPC in one instance, you may have problems if you create the same tablespace in another instance of Migration Workbench. This causes two tablespaces of the same name to exist in the Workbench repository that results in unnecessary errors during migration. Workaround Oracle recommends that you run only a single instance of Migration Workbench. Bug 3274651 - Custom Tablespace: Constraints Need to be Given for the OM_TABLESPACE_ INFO Migration Workbench does not validate the directory path entered in the Data File Directory option on the General page of the Options dialog. You may have problems creating tablespaces if the directory path is incorrect or invalid. Workaround Ensure that the directory path is correct in the Data File Directory option of the Options dialog. You should also ensure that the directory path uses the correct format for your destination platform. To verify or change the directory path, from the Tools menu, select Options. If the directory path is incorrect, modify it or leave it blank. If this field is blank, Migration Workbench uses the default data file directory for the destination database. 11

Bug 3211372 - Updating Default Tablespace Under One Schema Filters Across All Schema If you make changes to the Indexes: Default Storage Options or Tables: Default Storage Options property sheet for one user, they apply to all users. Workaround Oracle recommends that after you migrate the database using Migration Workbench, you use Oracle Enterprise Manager to make changes to the index or table storage options. You can also use Migration Workbench to make changes to the default storage options that only apply to a specific user for that index or table. From the Oracle Model tree, make your changes by selecting the Override Default Storage Options tab from the specific index or table, not the Default Storage Options tab for all indexes or tables. Bug 3252653 - JAVA.SQL.EXCEPTION: [POL-4005] Null Class Object is Not Allowed When you are using the default Workbench repository, Migration Workbench raises this error when it attempts to create an index on an empty Source Model table column. Workaround Ignore this error, as it has no effect on the migration. Bug 4457908 - Filenames Greater Than 30 Characters Must Be Considered During Capture If you are migrating a Microsoft Access database, the database name (not including the.mdb extension) must be less than or equal to 30 bytes, because it is stored in a field of type VARCHAR2(30). If the name is too long, an exception is recorded in the Error.log file. Workaround Rename the Microsoft Access database file so that the name is less than or equal to 30 bytes. Oracle Migration Workbench Release Notes, Release 10.1.0.4 for Microsoft Windows 98/2000/NT/XP and Linux x86 B19131-01 Copyright 1999, 2005, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065 The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. 12