Skip Headers

Oracle Migration Workbench Reference Guide for MySQL 3.22, 3.23 Migrations
Release 9.2.0 for Microsoft Windows 98/2000, Microsoft Windows NT and Red Hat Linux 6.2

Part Number A97249-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to next page

A
MySQL Error Messages

This appendix provides error messages that you may receive while migrating the MySQL database to Oracle.

Error Messages

As you use the Migration Workbench to migrate the data, the following error messages can occur:

Error Message Solution

Cannot connect to MySQL server <name>. Is there a MySQL server running on the system/port you are trying to connect to?

You may see this error message during Step 1: Source Database Details of the Capture Wizard. This error can be caused by the following:

  • The source port number is set to 3306 by default. This port number refers to the port through which MySQL communicates. This is the default port that the MySQL installer uses. If the MySQL server was configured to use a different port, replace the 3306 value with the correct port value in the Source Port Number fields in Step 1: Source Database Details of the Capture wizard.

  • The Data Source Name field refers to the name of the system where the MySQL server resides. Make sure you enter the correct values in the Data Source Name.

Communication link failure: bad handshake

You may see this error message during Step 1: Source Database Details of the Capture wizard. The Source Password field refers to the MySQL password for the root user. Specify the source password correctly in Step 1: Source Database Details of the Capture wizard to avoid this error.

Failed to create index <name>: java.sql.SQLException:ORA-01408: such column list already indexed.

You may see this error message during the migration phase. It occurs because you can declare a column or set of columns in MySQL as the primary key index and as a unique key index. In SQL*Plus, you can declare a column or set of columns as either primary or unique, not both. If the Migration Workbench has already migrated a set of columns declared as a primary key in a MySQL table, then discovers the same set of columns declared as a unique index, it is flagged as an error.


Go to previous page Go to next page
Oracle
Copyright © 1998, 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback