|
|
 Copyright © 1999, 2005, Oracle. All rights reserved. | Cookie Preferences | Ad Choices. |
|
|
Oracle® Migration Workbench Release Notes
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 Part No. B15858-01 |
|
Copyright © 1999, 2005, Oracle. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Release Notes
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86
Part No. B15858-01
January 2005
This document contains the following topics:
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. 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 additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation
JAWS, a Windows screen reader, 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, JAWS 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.
Oracle Migration Workbench (Migration Workbench), Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 enables you to migrate the following databases to an Oracle Database 10g, Oracle9i, or Oracle8i database:
IBM DB2/AS400 V4R5 and V4R3
IBM DB2 UDB 6 Beta, 7 Beta
Informix Dynamic Server 7.3
Informix Dynamic Server 9.x (Oracle Migration Workbench Beta)
Microsoft Access 2.0, 95, 97, 2000
This release of Migration Workbench also allows you to migrate a Microsoft Access 2.0, 95, 97, or 2000 database to an Oracle9i 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 for Linux enables you to migrate the following databases to an Oracle Database 10g, Oracle9i, or Oracle8i database:
Informix Dynamic Server 7.3
Informix Dynamic Server 9.x (Oracle Migration Workbench Beta)
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 2.0, 95, 97, 2000 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)
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.
This section describes new features of Migration Workbench Release 10.1.0 and provides pointers to additional information:
Migrating to Oracle using Migration Workbench for Linux
Migration Workbench enables you to migrate the following databases to an Oracle Database 10g, Oracle9i, or Oracle8i database on the Red Hat Enterprise Linux 3 (Linux) operating system:
Informix Dynamic Server 7.3
Informix Dynamic Server 9.x (Oracle Migration Workbench Beta)
MySQL 3.22, 3.23, 4.x
Sybase Adaptive Server 11, 12
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.
Migrating to Oracle Database 10g
Migration Workbench enables you to migrate a third-party database to Oracle Database 10g.
Mapping Data Types
Table 1 shows the new data types that Oracle Database 10g provides. Using Migration Workbench, you can map appropriate data types in the source database to these numeric data types.
|
Note: Oracle recommends that you do not change the default data type mappings unless you are an experienced Oracle database administrator. |
Table 1 Oracle Database 10g Data Types
| Data Type | Description |
|---|---|
| BINARY_FLOAT | This is a 32-bit double-precision floating point number data type. |
| BINARY_DOUBLE | This is a 64-bit single-precision floating point number data type. |
For more information about data types, see the Oracle Database SQL Reference.
Table 2 shows a sample of data types that you can map to BINARY_FLOAT for each plug-in.
Table 2 Data Type Mappings for BINARY_FLOAT
| Plug-in | Data Type |
|---|---|
| IBM DB2/400 V4R3 and V4R5 | REAL
DECIMAL |
| IBM DB2 UDB 6, 7.1, and 7.2 | REAL |
| Informix Dynamic Server 7.3 | FLOAT
SMALLFLOAT |
| Informix Dynamic Server 9.x | SINGLE
DECIMAL |
| Microsoft Access 2.0, 95, 97, and 2000 | SINGLE
DECIMAL |
| Microsoft SQL Server 6.5, 7.0, and 2000 | FLOAT |
| MySQL 3.22, 3.23, and 4.x | FLOAT |
| Sybase Adaptive Server 11 and 12 | FLOATN
REAL |
Table 3 shows a sample of data types that you can map to BINARY_DOUBLE for each plug-in.
Table 3 Data Type Mappings for BINARY_DOUBLE
| Plug-in | Data Type |
|---|---|
| MySQL 3.22, 3.23, and 4.x | DOUBLE PRECISION |
| IBM DB2/400 V4R3 and V4R5
IBM DB2 UDB 6, 7.1, and 7.2 Informix Dynamic Server 9.x Microsoft Access 2.0, 95, 97, and 2000 MySQL 3.22, 3.23, and 4.x |
DOUBLE |
Using Row Timestamp for Optimistic Locking
Oracle Database 10g provides optimistic locking through the introduction of the Row Timestamp pseudo-column. This pseudo-column represents the System Change Number (SCN) values for each row. Until now, when posting updates to the database, applications had to read in all column values or user-specified indicator columns, compare them with those previously fetched, and update those with identical values. With the Row Timestamp feature, applications only need to retrieve and compare the row SCN to verify that no changes occurred between selecting and updating the values. For information about the row SCN, see the Oracle Database SQL Reference.
Other databases may implement optimistic locking differently from Oracle. For example, Sybase Adaptive Server provides optimistic locking through the use of its TIMESTAMP data type. However, Migration Workbench does not automatically map the row timestamp to the Oracle Database 10g Row Timestamp.
To maintain optimistic locking within Oracle Database 10g using the Row Timestamp feature, you might have to do the following:
Modify the application code that implements or uses another method of optimistic locking in your source database.
Remove the migrated timestamp columns from the target tables in Oracle to ensure that your Oracle database does not contain redundant data. To remove a column from a table in Oracle, use the following command:
ALTER TABLEtableNameDROPcolumnName;
In the previous command, tableName is the name of the table and columnName is the name of the timestamp column that you want to remove.
Enhanced Regular Expressions
Migration Workbench can map the Oracle Database 10g REGEXP_LIKE SQL function when you are migrating Informix Dynamic Server, Microsoft SQL Server, and Sybase Adaptive Server to Oracle. REGEXP_LIKE is similar to the LIKE condition, except REGEXP_LIKE performs regular expression matching instead of the simple pattern matching performed by LIKE. This condition evaluates strings using characters as defined by the input character set.
|
Note: The Informix Dynamic Server online help has been updated for this release. Therefore, for more information about the Oracle Database 10g REGEXP_LIKE SQL function for Informix Dynamic Server, see the Informix Dynamic Server online help. |
In the stored procedures, triggers, and views parser options page of Migration Workbench, you have the following option available for Microsoft SQL Server and Sybase Adaptive Server:
|
Note: Use column name aliases in reference cursor, is no longer available on the stored procedures, triggers, and views parser options page of Migration Workbench for Microsoft SQL Server and Sybase Adaptive Server. |
Using Oracle Database 10g REGEXP_LIKE Function
Select the Use Oracle 10g REGEXP_LIKE function option to enable Migration Workbench to determine whether a specific column, variable, or text string contains text matching a regular expression. If Migration Workbench cannot convert an expression during the creation of the Oracle Model, it uses the Alter_TSQL_Regexp function in the omwb_emulation schema. This enables Migration Workbench to automatically modify the syntax at the runtime of the application. For more information about the REGEXP_LIKE function, see the Oracle Database SQL Reference.
Using the MySQL Connector/J3.0 JDBC Driver
Migration Workbench now uses the MySQL Connector/J 3.0 JDBC driver to connect to MySQL. For more information about downloading and using this driver, see the Oracle Migration Workbench User's Guide.
|
Note: Migration Workbench does not provide support for the MM MySQL JDBC driver release 1.2a. |
Migrating From MySQL 4.x
Migration Workbench supports the migration of MySQL 4.x databases, including Foreign Key constraints. For more information about migrating your MySQL 4.x database to Oracle, see the Oracle Migration Workbench User's Guide and the Reference Guide for MySQL 3.22, 3.23, 4.x Migrations.
Before you install Migration Workbench, review the Hardware Requirements and Software Requirements topics.
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
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 |
After you download the Migration Workbench, you can install it on Windows or Linux x86. The following sections describe the installation process:
To install Migration Workbench on Windows:
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.html
|
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.
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. |
Start Microsoft Windows.
Log on to the system as a member of the Administrators Group.
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. |
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. |
To install Migration Workbench on Linux x86:
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.html
|
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.
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. |
Open a terminal session on Linux x86.
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. |
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. |
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:
Close Migration Workbench.
Navigate to the following directory:
On Windows:
OMWB_install_dir\Omwb\bin
On UNIX:
OMWB_install_dir/Omwb/bin
Open the state.properties file.
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
From the File menu, select Save, then close the file.
Restart Migration Workbench for the changes to take effect.
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 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.
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. |
The following documents are updated for this release:
Online Help for Informix Dynamic Server 7.3 and 9.x
Online Help for Microsoft SQL Server and Sybase Adaptive Server
Online Help for MySQL 3.22, 3.23 and 4.x
Oracle Migration Workbench User's Guide
The following issues apply to the Oracle Migration Workbench documentation:
The Oracle Migration Workbench Frequently Asked Questions (FAQ) contains an error in the Installation and Configuration section. The following question and its answer are obsolete:
Can I install the Migration Workbench into an Oracle home directory that contains a release of the Oracle Server earlier than Oracle9i?
For accurate information about installing Migration Workbench, see "Installing Migration Workbench".
This section describes the missing information in the Migration Workbench Repository Login topic of the online help.
By default, Migration Workbench uses a thin JDBC driver to connect to the Workbench repository. However, if you have a thick JDBC driver installed on your computer, it is possible to use it to connect to the Workbench repository.
To connect to the Workbench repository using a thick JDBC driver:
From the Oracle Migration Workbench Repository Login dialog box, specify only the following options:
Username
Password
SID
|
Note: You must have these connection details in the tnsnames.ora file. |
Click OK.
Migration Workbench connects to the Workbench repository.
This section describes the missing nonstandard character encoding information in the Oracle Migration Workbench User's Guide.
To configure Migration Workbench to use nonstandard character encoding:
Set the JRE file encoding property as follows:
Using a text editor, open the Migration Workbench startup file by editing the omwb.bat file located in the OMWB_install_dir/Omwb/bin directory.
Add the following information to the start command, before -jar:
-Dfile.encoding="file_encoding"
In the previous line, file_encoding is the required file encoding. For example, for Japanese file encoding, the omwb.bat file should look similar to the following:
start ..\jre\bin\javaw -ms30m -mx256m -Dfile.encoding="Shift_Jis" -jar ..\lib\boot.jar oracle.mtg.migrationUI.MigrationApp
Save the file, then exit.
Install the appropriate font.properties file for the required file encoding as follows:
Make a backup copy of your existing font.properties file in the OMWB_install_dir/Omwb/jre/lib directory.
Download the required Java font.properties file from the following Web site:
http://www.sun.com/
Rename the downloaded file to font.properties. For example, rename the Japanese font.properties file from font.properties.ja to font.properties.
Copy the new font.properties file into the OMWB_install_dir/Omwb/jre/lib directory.
If you are performing an offline capture, you must specify delimiter characters in the offline capture scripts as follows:
Using a text editor, open the omwb.properties file located in the OMWB_install_dir/Omwb/bin directory.
Edit or add the following fields:
OFFLINE_CAPTURE_COLUMN_DELIMITER="delimiter_column" OFFLINE_CAPTURE_ROW_DELIMITER="delimiter_row"
In the previous lines, delimiter_column is your choice of column delimiter and delimiter_row is your choice of row delimiter.
|
Note: These delimiter values must correspond to the delimiter values used in the offline capture scripts. |
Save the file, then exit.
Migration Workbench is now enabled to handle the new character encoding.
To report a bug, see the instructions in the Oracle Migration Workbench Support Web site at:
http://www.oracle.com/technology/support/tech/migration/workbench/index.html
This section contains the following topics:
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.
If you are migrating Informix Dynamic Server 9.x using the offline capture method, use the offline capture scripts provided with this release of Migration Workbench. Otherwise, the offline capture fails. If you convert script files to UNIX, you must create offline capture files in Linux x86, not Windows.
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:
Create a database with a name that does not contain special characters.
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.
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 4119713 - CLOB ROWS ARE MIGRATED IN THE WRONG ORDER
Migrating rows with CLOB values from Microsoft SQL Server 7.0 to Oracle online, they are inserted into the Oracle table in the wrong order.
Workaround Migrate the Microsoft SQL Server 7.0 database using the offline method. For more information about offline migrations, see the Oracle Migration Workbench User's Guide.
The following table lists the bugs fixed in this release of Migration Workbench:
| Bug No | Component | Description |
|---|---|---|
| 3507285 | TSQLPARSE | SUPPORT ORACLE 10G REGEXP_LIKE EXPRESSION IN TSQL PARSER |
| 3507293 | INFORPARSE | SUPPORT ORACLE 10G REGEXP_LIKE EXPRESSION IN INFORMIX PARSER |
| 3202676 | COMMON | UNIQUE CONSTRAINTS ARE DISPLAYED UNDER PRIMARY KEYS CONTAINER TREE ITEM IN SM |
| 2694054 | COMMON | UNIQUE CONSTRAINTS BEING DISPLAYED WITHIN 'INDEXES' AND 'UNIQUE CONSTRAINTS' |
| 3287180 | SQLSRV2000 | FAIL TO MAP ANY PRIMARY KEYS TO ORACLE MODEL WHEN PK'S HAVE SAME NAME |
| 2739049 | COMMON | MULTIPLE FOREIGN KEYS ON SAME COLUMNS MAPPED TO ORACLE, 2ND FAILS TO GENERATE |
| 3479353 | SYBASE12 | DEFAULTS 'EXPRESSION' IN SYBASE 12 NOT MAPPED PROPERLY BY OMWB |
| 3286082 | SQLSRV2000 | DELETION OF 'LOGIN' NODE FROM SOURCE MODEL NO LONGER ALLOWED |
| 2740584 | COMMON | OFFLINE DATA MOVE SCRIPTS FOR UNIX |
| 3274327 | COMMON | SQL_LOAD_SCRIPT.SH INCORRECTLY GENERATED |
| 3479495 | SQLSRV2000 | DATABASE OFFLINE CAPTURE NOT POSSIBLE IF SQL SERVER DATABASE IS CASE SENSITIVE |
| 2694372 | TSQLPARSE | T-SQL PARSER NOT PREPENDING FUCNCTION CALLS WITH CORRECT OWNER NAME IN PLSQL |
| 3569486 | SQLSRV2000 | CANNOT DISPLAY JAPANESE OBJECT NAME |
| 3287163 | SQLSRV2000 | MULTIPLE LOADING OF PRIMARY KEYS |
| 2921208 | SYBASE | EMPTY STRING IN DEFAULTS NOT MIGRATED CORRECTLY - VALUE SHOULD BE OPTIONAL |
| 3261738 | SYBASE12 | DSML/OFFLINE CAPTURE RESULTS IN MTG_SYSCONSTRAINTS VIEW IN SOURCE MODEL |
| 3330000 | COMMON | GENERATE MIGRATION SCRIPTS VARIABLE STARTVAL NUMBER |
| 2146804 | SQLSERVER7 | SYSTEM TABLE DTPROPERTIES IS CAPTURED AS USER TABLE |
| 3415768 | INFORMIX73 | OFF-LINE CAPTURE RESTRICTED TO LESS THAN 70 DATABASES PER REPOSITORY |
| 3406886 | INFORMIX73 | INFORMIX STORED PROCEDURE TEXT IS MISSING SOME SPACE( " ") CHARACTERS WITH DSML |
| 3403388 | INFORMIX73 | DOUBLE QUOTES IN STORED PROGRAMS HAVE ESCAPE BACKSLASH'S BEFORE THEM (\") |
| 3258678 | COMMON | PUBLIC SYNONYMS BEING GENERATED TWICE IN MIGRATION SCRIPTS |
| 3194411 | SYBASE | EXCEPTION :SYBASE11DISCONNSOURCEMODELLOAD.SOURCEMODELINDEXDROP(): JAVA.UTIL.VECT |
| 3403446 | INFORMIX73 | OMWB SOURCE MODEL FAILS TO DISPLAY DATABASE TREE BECAUSE OF TABLE DEFAULT |
| 3604148 | INSTALLER | MYSQL3 REPOSITORY NOT CLEANING UP AFTER DE-INSTALL |
| 3604239 | MYSQL | CANNOT RUN MYSQL4.0 PLUGIN |
| 3604130 | INSTALLER | REMOVAL OF PLUGIN+ADDITION OF PLUGIN CAUSES ERROR ON OMWB STARTUP |
| 3261805 | DOC | USER'S GUIDE INCORRECT W.R.T DESTINATION USER PRIVILEGES |
| 3249714 | DOC | INFORMIX ONLINE HELP SEARCH DOES NOT WORK |
| 3073363 | DOC | NEED TO DESCRIBE USE OF DEFAULT_OWNER ENV. VARIABLE IN ONLINE HELP |
| 2312024 | INFORMIX73 | HELP TOPIC MISSING FOR ESQL, FILE REGENERATION |
| 2115966 | INFORMIX73 | ERROR IN NAMING OF SOURCE MODEL LOAD IN STEP 1, SOURCE MODEL LOAD DETAILS |
| 3638042 | SQLSERVER7 | NULLPOINTEREXCEPTION (USERFLOW) DURING CAPTURE |