Before You Start Migrating: Source-Specific Information

Ensure that the source database is accessible by the Microsoft SQL Server or Sybase Adaptive Server user that is used by SQL Developer for the source connection. This user must be able to see any objects to be captured in the Microsoft SQL Server or Sybase Adaptive Server database; objects that the user cannot see are not captured. For example, if the user can execute a stored procedure but does not have sufficient privileges to see the source code, the stored procedure cannot be captured.

Ensure that you can connect to the Microsoft SQL Server or Sybase Adaptive Server database from the system where you have installed SQL Developer.

Ensure that you have downloaded the JTDS JDBC driver from http://jtds.sourceforge.net/.

In SQL Developer, if you have not already installed the JTDS driver using Check for Updates (on the Help menu), do the following:

1. Click Tools, then Preferences, then Database, then Third Party JDBC Drivers.

2. Click Add Entry.

3. Select the jar file for the JTDS driver you downloaded from http://jtds.sourceforge.net/.

4. Click OK.

In SQL Developer, click Tools, then Preferences, then Migration: Identifier Options, and ensure that the setting is correct for the Is Quoted Identifier On option (that is, the setting reflects the database to be migrated).

If this option is enabled, quotation marks (double-quotes) can be used to refer to identifiers; if this option is not enabled, quotation marks identify string literals. As an example of the difference in behavior, consider the following T-SQL code:

select col1, "col 2" "column_alias"
from tablex "table_alias"

If the Is Quoted Identifier On option is enabled (checked), the following PL/SQL code is generated:

SELECT col1, col_2 "column_alias"
  FROM tablex "table_alias";

If the Is Quoted Identifier On option is disabled (not checked), the following PL/SQL code is generated:

SELECT col1, 'col 2' "column_alias"
  FROM tablex "table_alias";

Make backup copies of the database file or files.

Ensure that the necessary software (Microsoft Access, perhaps other components) is installed on the same system as SQL Developer.

Ensure that the Admin user has at least Read Design and Read Data permissions on the MSysObjects, MSysQueries, and MSysRelationships system tables, as explained in the information about the Access tab in the Create/Edit/Select Database Connection dialog box.

If security is enabled, you should turn it off by copying the contents of the secured database into a new database, as follows:

SQL Developer does not support the migration of Microsoft Access databases that have security enabled. By default, SQL Developer uses the name of the Microsoft Access MDB file as the user name for the destination Oracle user. If you create an Oracle user in this way, the password is ORACLE.

1. From the File menu in Microsoft Access, select New Database.

2. Select the Blank Database icon, then click OK.

3. In the File New Database option, type a name for the database, then click Create.

4. From the File menu within the new database, select Get External Data, then select Import.

5. Select the secured Microsoft Access database that you want to import, then click Import.

6. From the Import Objects dialog, click Options.

7. Select the Relationships and Definition and Data options.

8. From the Tables tab, choose Select All.

9. Click OK.

   All Microsoft Access objects are copied over to the new Microsoft Access database, except for the security settings.

If the application contains linked tables to other Microsoft Access databases, refresh these links by opening the application in Microsoft Access and performing the following:

From the Tools menu in Microsoft Access 97, select Add Ins, then select Linked Table Manager.

From the Tools menu in Microsoft Access 2000, select Database Utilities, then select Linked Table Manager.

Ensure that the Microsoft Access database is not a replica database, but a master database.

When you use the Exporter for Microsoft Access to export, an error message is displayed if the database is a replica. SQL Developer does not support the migration of a replica database.

From the Tools menu within Microsoft Access, select Database, then select Compact Database to compact the Microsoft Access database files.

Ensure that the Microsoft Access MDB file is accessible from the system where you have installed SQL Developer.

Use the Oracle Universal Installer to verify that you have the Oracle ODBC driver installed. If you need to install the driver, it is available on the Oracle Database Server or Database Client CD. You can also download the Oracle ODBC driver from the Oracle Technology Network (OTN) Web site:

http://www.oracle.com/technology/software/tech/windows/odbc/

Install the Oracle ODBC driver into an Oracle home directory that contains the Oracle Net Services. You can obtain the Oracle Net Services from the Oracle Client or Oracle Database CD. You install Oracle Net Services to obtain the Net Configuration Assistant and Net Manager. These allow you to create a net configuration in the tnsnames.ora file.

Ensure that you can connect to the MySQL database from the system where you have installed SQL Developer.

Ensure that you have downloaded the MySQLConnector/J API from the MySQL Web site at http://www.mysql.com/.

In SQL Developer, if you have not already installed the MySQL JDBC driver using Check for Updates (on the Help menu), do the following:

1. Click Tools, then Preferences, then Database, then Third Party JDBC Drivers.

2. Click Add Entry.

3. Select the jar file for the MySQL driver you downloaded from http://www.mysql.com/.

4. Click OK.

Ensure that the source database is accessible by the MySQL user that is used by SQL Developer for the source connection. This user must be able to see any objects to be captured in the MySQL database; objects that the user cannot see are not captured. For example, if the user can execute a stored procedure but does not have sufficient privileges to see the source code, the stored procedure cannot be captured.