Oracle Migration Workbench Release Notes Release 9.2.0 for Windows 98/2000/NT and Windows XP Part Number B10259-01 |
|
Release 9.2.0 for Microsoft Windows 98/2000/NT and Microsoft Windows XP
September 2002
Part No. B10259-01
This document contains the following topics:
Oracle Migration Workbench (Migration Workbench), release 9.2.0 enables you to migrate the following databases to an Oracle9i or Oracle8i database:
This document outlines how to install the Migration Workbench. It also provides tips on using the Migration Workbench. For more information on the Migration Workbench, see the following documentation:
The following new plug-ins are supported by of release 9.2.0 of the Migration Workbench:
The IBM DB2 UDB plug-ins for the Migration Workbench enables you to migrate users, tables, table spaces, table aliases, primary keys, foreign keys, unique constraints, indexes, groups, table and column-level privileges to Oracle8i or Oracle9i.
The Informix Dynamic Server 9 plug-in for the Migration Workbench is developed using the knowledge acquired during the development of the Informix Dynamic Server 7.3 plug-in.
The initial aim of this plug-in is to support the migration of Informix Dynamic Server 7.3 databases that were upgraded to Informix Dynamic Server 9. Some of the newer Informix Dynamic Server 9 features are not supported by this release.
This release of the Migration Workbench uses the Oracle thin jdbc driver. This reduces the Migration Workbench installation footprint. Because the thin jdbc driver is used you are now required to specify the user name, password, host, port and SID whenever you log into an Oracle8i or Oracle9i repository, use the Tablespace Discoverer, or specify a destination Oracle database.
Oracle Corporation recommends that you consult your organizations Oracle DBA for the host, port, and SID connection details.
Before you install the Migration Workbench, review the Hardware Requirements and Software Requirements topics.
The Migration Workbench has the following minimum and recommended hardware requirements:
The Migration Workbench has minimum and recommended software requirements. This sections contains the following:
In order to migrate any plug-in, it is recommended that you have the following:
You can download the Migration Workbench release 9.2.0 at:
http://otn.oracle.com/tech/migration/workbench
To install the Migration Workbench once you have downloaded the Migration Workbench:
%ORACLE_HOME%
, see the Installing into an Oracle Home Directory topic.
Note: The name of the Oracle home directory must be 1 to 16 characters long. It can only include alphanumeric characters and underscores. |
You can download the Migration Workbench release 9.2.0 plug-ins at:
http://otn.oracle.com/tech/migration/workbench
To install the Migration Workbench plug-ins:
%ORACLE_HOME%
, see the Installing into an Oracle Home Directory topic.
Note: The name of the Oracle home directory must be 1 to 16 characters long. It can only include alphanumeric characters and underscores. |
In order to obtain a successful migration, consider the following, when Installing into an Oracle Home Directory.
Since the Migration Workbench release 9.2.0 includes Oracle 9.2.0 dependencies, it can only be installed into an Oracle 9.2.0 home directory or its own home directory. If there is a previous release of Oracle installed on the system, you must install the Migration Workbench into a separate Oracle home directory.
You then need to switch the default Oracle home directory to point to the previous Oracle installation so that you do not pick up the new NT client dependencies for other applications you may use on the system.
To switch the Oracle home directory:
Note: The Home Selector is automatically installed when you install the Oracle Installation Products. |
If you attempt to install into an Oracle home directory other than Oracle 9.2.0 home directory, the Oracle Universal Installer displays the following error message:
Migration Workbench can only be installed into a new %ORACLE_HOME%
or an existing Oracle 9.2.0 %ORACLE_HOME%
.
All downloaded Migration Workbench plug-ins must also be installed into an Oracle 9.2.0 home directory.
While launching the Migration Workbench from Microsoft Windows 98, you may obtain the Finished - Shortcut To dialog box containing the following error message:
Out of environment space Out of environment space Bad command or file name
To launch the Migration Workbench after receiving these error messages:
To view Migration Workbench HTML files, such as the Quick Tour, the release notes, or reference guide, the Migration Workbench attempts to activate the default browser on a Microsoft Windows 98/2000 or Microsoft Windows NT system. However, the Migration Workbench does not know the name or path of the default browser. It relies on the Microsoft Windows file associations to activate the browser, if one exists.
To avoid any Web browser problems, the state.properties file is used to specify the exact path of the system browser. The state.properties file is automatically generated the first time you launch the Migration Workbench.
If there is a problem executing the browser command on a Microsoft Windows system, you receive the following error message:
Problem executing Browser command command executed. Please specify the browser path in the c:\Oracle\Ora9\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 the Migration Workbench launches the correct browser you must edit the state.properties file:
%ORACLE_HOME%\Omwb\
bin directory.
c:\Program Files\Netscape\Communicator\Program\Netscape.exe
In order to report a bug, refer to the Online Support page within the product. For more information about reporting bugs, see the Limitations and Bugs topic. This section contains the following topics:
The following issues must be considered when using the Migration Workbench to migrate a Microsoft Access database to Oracle:
The 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.
The Migration Workbench is unable to load BLOBs
when you choose Object -> Generate SQL*Loader Scripts to generate off-line data loading.
The Migration Workbench is unable to load CLOBs
that contain line breaks when you choose Object -> Generate SQL*Loader Scripts to generate off-line data loading.
Bug 1509958
Description: Timestamp columns do not load with SQL*Loader direct path load. When a timestamp column is migrated to Oracle the Migration Workbench generates a sequence and a trigger to mimic the behavior of the timestamp column. However, when you migrate the data in Migration Workbench release 1.3.0 or migration Workbench release 1.3.1 using SQL*Loader, the Migration Workbench uses the direct=true
syntax in the sql_load_script.bat file. This means that the sequence and trigger are bypassed and the original timestamp entry is inserted into the column with an error.
Workaround: In order to load timestamp columns correctly, you must manually edit the sql_load_script.bat file and remove the direct=true
syntax for the table that contains the timestamp column. The sql_load_script.bat file is located in the %ORACLE_HOME%/Omwb/sqlloader_scripts/<plug-in name>/<timestamp>/oracle directory.
|
![]() Copyright © 2002 Oracle Corporation. All Rights Reserved. | | Ad Choices. |
|