2 Migrating Third-Party Databases

2.2.1 How Migration Works

The components of SQL Developer work together to migrate a third-party database to an Oracle database. Figure 2-1, "SQL Developer Migration Architecture" shows how SQL Developer reads the information from the source database and creates the Oracle database schema objects. SQL Developer uses the information stored in the migration repository to migrate to the Oracle schema. You can make changes to the captured model or the converted model, or both, before migrating. The information in the converted model is used to complete the migration, that is, to generate the database objects in the destination Oracle schema.

Figure 2-1 SQL Developer Migration Architecture

2.2.2 Migration Implemented as SQL Developer Extensions

Migration support is implemented in SQL Developer as a set of extensions: one for Oracle Migration Workbench, and one "plugin" for each supported third-party database. If you want, you can disable migration support or support for individual plugins.

To view the installed extensions, and to enable or disable individual extensions, click Tools, then Preferences, then Extensions.

2.3.1 Task 1: Determining the Requirements of the Migration Project

In this task, you identify which databases you want to migrate and applications that access that database. You also evaluate the business requirements and define testing criteria.

To determine the requirements of the migration project:

1. Define the scope of the project.

   There are several choices you must make about the third-party database and applications that access that database in order to define the scope of the migration project. To obtain a list of migration issues and dependencies, you should consider the following

   • What third-party databases are you migrating?

     • What is the version of the third-party database?

     • What is the character set of the third-party database?

   • What source applications are affected by migrating the third-party database to an Oracle database?

     • What is the third-party application language?

     • What version of the application language are you using?

     In the scope of the project, you should have identified the applications you must migrate. Ensure that you have included all the necessary applications that are affected by migrating the database

   • What types of connectivity issues are involved in migrating to an Oracle database?

     • Do you use connectivity software to connect the applications to the third-party database? Do you need to modify the connectivity software to connect the applications to the Oracle database?

     • What version of the connectivity software do you use? Can you use this same version to connect to the Oracle database?

   • Are you planning to rewrite the applications or modify the applications to work with an Oracle database?

2. Use Table 2-1 to determine whether you have a complex or simple source database environment. Identify the requirements based on the specific scenario.

   If the migration project is a simple scenario, you may not have to complete all of the tasks listed in this guide. You make decisions based on your specific environment. For example, if you have a complex scenario, you may require extra testing based on the complexity of the application accessing the database.

   Table 2-1 Complex and Simple Scenarios

   Complex Scenario	Simple Scenario
   More than one of the following: Large database (greater than 25 GB) Data warehouse Large applications (greater than 100 forms, reports, and batch jobs) Database is used by multiple lines of business Distributed deployment Large user base (greater than 100) High availability requirement (such as a 24 X 7 X 365 environment)	Contains the following: Small database (less than 25 GB) Simple online transaction processing (OLTP) Small application (less than 100 forms, reports, and batch jobs) Database is used by one department Centralized deployment Small user base (less than 100) Average availability (business hours)

   
   

3. Determine whether the destination database requires additional hardware and rewriting of backup schedules.

4. Define testing and acceptance criteria.

   Define tests to measure the accuracy of the migration. You then use the acceptance criteria to determine whether the migration was successful. The tests that you develop from the requirements should also measure stability, evaluate performance, and test the applications. You must decide how much testing is necessary before you can deploy the Oracle database and applications into a production environment.

5. Create a requirements document with a list of requirements for the migration project.

   The requirements document should have clearly defined tasks and number each specific requirement, breaking these into sub-requirements where necessary.

2.3.2 Task 2: Estimating Workload

In this task, you use SQL Developer to make calculated decisions on the amount of work that can be automated and how much is manual.

To estimate the workload:

1. Capture the captured model, create the converted model, and migrate to the destination database.

   You can analyze the source database through the captured model and a preview of the destination database through the converted model. After you have captured the source database, analyze the captured data contained in the captured model and the converted model. Ensure the content and structure of the migration repository is correct and determine how much time the entire process takes.

2. Generate and use reports to evaluate the capture and migration process, categorize the total number of database objects, and identify the number of objects that can be converted and migrated automatically.

   The Summary, Detailed, and Error and Warnings reports provide information about the actions that have occurred and record any warnings and errors. They identify the changes that have been made to the converted model so that you can evaluate if you should make changes to the applications that access the destination database.

3. Evaluate and categorize the issues that occurred. The reports can help by providing information about:

   • Tables that did not load when you captured the source database

   • Stored procedures, views, and triggers that did not parse when you created the converted model

   • Syntax that requires manual intervention

   • Database objects that were not created successfully when you migrated the destination database

   • Data that did not migrate successfully when you migrated the destination database

4. For each error or warning in reports, evaluate the following:

   • Number of times an issue occurred

   • Time required to fix the issues, in man hours

   • Number of resources required to fix the issue

     After you have solved a complex problem, it should be easier and quicker to resolve the next time you have the same problem.

   Use these reports to evaluate each error and determine how long it would take to rectify. The reports help identify the size of the database that was created.

2.3.3 Task 3: Analyzing Operational Requirements

In this task, you analyze the operational requirements, as follows:

1. Evaluate the operational considerations in migrating the source database to a destination database. Consider the following questions:

   Note:

   If the scope of the migration project is a complex scenario as defined in Table 2-1, Oracle recommends that you answer all of these questions. If you have a simple scenario, determine the answers to the most appropriate questions.

   • What backup and recovery changes do you require?

   • What downtime is required during the migration?

   • Have you met the performance requirements?

   • Are you changing the operational time window?

   • What effect does the downtime have on the business?

   • What training requirements or additional staff considerations are required?

   • Is it necessary to have the third-party and the Oracle database running simultaneously?

2. For each task, determine the resources and time required to complete.

3. Create an initial project plan.

   Use the information that you have gathered during the requirements and planning stage to develop an initial project plan.

2.3.4 Task 4: Analyzing the Application

In this task, you identify the users of the applications that run on the source database, what hardware it requires, what the application does, and how it interfaces with the source database. You also analyze the method the application uses to connect to the database and identify necessary modifications.

To analyze the application:

1. Determine whether changes to the application are required to make them run effectively on the destination database.

2. If changes are required to the application, determine whether it is more efficient to rewrite or modify the applications.

   If you are rewriting the application to use the Oracle database, consider the following:

   1. Create the necessary project documentation to rewrite the application. For example, you need a design specification and requirements documentation.

   2. Rewrite the application according to the specification.

   3. Test the application works against the Oracle database.

   If you are modifying the application to use the Oracle database, consider the following:

   1. Identify the number of connections to the database that are in the application and modify these connections to use the Oracle database.

      You may need to change the connection information to use an ODBC or JDBC connection.

   2. Identify the embedded SQL statements that you need to change in the application before you can test it against the Oracle database.

   3. Test the application using the Oracle database.

3. Allocate time and resource to address each issue associated with rewriting or modifying the application.

4. Update the general requirements document for the project that you created in Task 1.

2.3.5 Task 5: Planning the Migration Project

In this task, you evaluate the unknown variables that the migration project may contain, such as the difference in the technologies of the source database and the destination database. During the planning stage, you:

• Estimate the budget constraints of the project

• Gather information to produce a migration plan

• Estimate how much time the migration project should take

• Calculate how many resources are required to complete and test the migration

To plan a migration project:

1. Define a list of tasks required to successfully complete the migration project requirements of Task 1.

2. Categorize the list of tasks required to complete the migration project.

   You should group these tasks according to your business. This allows you to schedule and assign resources more accurately.

3. Update and finalize the migration project plan based on the information that you have obtained from Task 3 and Task 4.

4. Make sure the migration project plan meets the requirements of the migration project.

   The migration plan should include a project description, resources allocated, training requirements, migration deliverable, general requirements, environment analysis, risk analysis, application evaluation, and project schedule.

2.4.1 Creating a Database User for the Migration Repository

SQL Developer requires a migration repository to migrate a third-party database to an Oracle database. To use an Oracle database for the migration repository, you must have access to that database using a database user account. Oracle recommends that you use a specific user account for migrations, For example, you may want to create a user named MIGRATIONS, create a database connection to that user, and use that connection for the migration repository; and if you wish, you can later delete the MIGRATIONS user to remove all traces of the migration from the database.

When you create a user for migrations, specify the tablespace information as in the following example, instead of using the defaults for tablespaces:

CREATE USER migrations IDENTIFIED BY migrations 
  DEFAULT TABLESAPACE users TEMPORARY TABLESPACE temp,

Do not use a standard account (for example, SYSTEM) for migration.

When SQL Developer creates a migration repository, it creates many schema objects that are intended only for its own use. For example, it creates tables, views, indexes, packages, and triggers, many with names starting with MD_ and MIGR. You should not directly modify these objects or any data stored in them.

2.4.2 Requirements for Creating the Destination Oracle Objects

The user associated with the Oracle database connection used to perform the migration (that is, to run the script containing the generated DDL statements) must have the following roles and privileges:

Roles

CONNECT WITH ADMIN OPTION
RESOURCE WITH ADMIN OPTION

Privileges

ALTER ANY ROLE
ALTER ANY SEQUENCE
ALTER ANY TABLE
ALTER TABLESPACE
ALTER ANY TRIGGER
COMMENT ANY TABLE
CREATE ANY SEQUENCE
CREATE ANY TABLE
CREATE ANY TRIGGER
CREATE VIEW WITH ADMIN OPTION
CREATE PUBLIC SYNONYM WITH ADMIN OPTION
CREATE ROLE
CREATE TABLESPACE
CREATE USER
DROP ANY SEQUENCE
DROP ANY TABLE
DROP ANY TRIGGER
DROP TABLESPACE
DROP USER
DROP ANY ROLE
GRANT ANY ROLE
INSERT ANY TABLE
SELECT ANY TABLE
UPDATE ANY TABLE

For example, you can create a user called migrations with the minimum required privileges required to migrate a database by using the following commands:

CREATE USER migrations IDENTIFIED BY migrations
  DEFAULT TABLESAPACE users TEMPORARY TABLESPACE temp;
 
GRANT CONNECT, RESOURCE, CREATE VIEW, CREATE PUBLIC SYNONYM TO 
  migrations WITH ADMIN OPTION;
 
GRANT  ALTER ANY ROLE, ALTER ANY SEQUENCE, ALTER ANY TABLE, ALTER TABLESPACE,
ALTER ANY TRIGGER, COMMENT ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY TABLE,
CREATE ANY TRIGGER, CREATE ROLE, CREATE TABLESPACE, CREATE USER, DROP ANY
SEQUENCE, DROP ANY TABLE, DROP ANY TRIGGER, DROP TABLESPACE, DROP USER, DROP ANY
ROLE, GRANT ANY ROLE, INSERT ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE TO 
migrations;

2.4.3 Using Nonstandard Character Encoding on Windows Systems

If you need to configure SQL Developer to use nonstandard character encoding, such as for multibyte character sets, on Microsoft Windows systems, follow these steps:

1. Set the JRE file encoding property as follows:

   1. Using a text editor, open the SQL Developer startup file by editing the omwb.bat file located in the OMWB_install_dir/Omwb/bin directory.

   2. 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 multibyte Microsoft Access databases, the file encoding should be set to UTF-8, and the omwb.bat file should look similar to the following:

      start ..\jre\bin\javaw -ms30m -mx256m -Dfile.encoding="UTF-8" -jar ..\lib\boot.jar oracle.mtg.migrationUI.MigrationApp
       
      

      If you are migrating a multibyte Microsoft Access database (for example Japanese or Chinese), the character set on the target Oracle database instance should be set to UTF8.

   3. Save the file, then exit.

2. Install the appropriate font.properties file for the required file encoding as follows:

   1. Make a backup copy of your existing font.properties file in the OMWB_install_dir/Omwb/jre/lib directory.

   2. Download the required Java font.properties file from the following Web site:

      http://www.sun.com/
      
      

   3. Rename the downloaded file to font.properties. For example, rename the Japanese font.properties file from font.properties.ja to font.properties.

   4. Copy the new font.properties file into the OMWB_install_dir/Omwb/jre/lib directory.

3. If you are performing an offline capture, you must specify delimiter characters in the offline capture scripts as follows:

   1. Using a text editor, open the omwb.properties file located in the OMWB_install_dir/Omwb/bin directory.

   2. 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.

   3. Save the file, then exit.

      SQL Developer is now enabled to handle the new character encoding.

2.5.1 Before Migrating From Microsoft SQL Server

To configure a Microsoft SQL Server database for migration:

1. Ensure that the source database is accessible by the Microsoft SQL Server user that is used by SQL Developer. This user must have DBA access to the Microsoft SQL Server database.

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

3. Install the Microsoft SQL Server ODBC driver release 3.70.06.23 or higher is installed on the same system as SQL Developer, as follows:

   The Microsoft SQL Server ODBC driver is shipped with the Microsoft SQL Server client software. Installation procedures depend on the version of Microsoft SQL Server. For more information about the Microsoft SQL Server ODBC driver, see the Microsoft SQL Server specific documentation.

4. Set the Oracle ODBC Data Source as follows:

   The Oracle ODBC Data Source is used to set up Data Source Names (DSN). You can create a DSN at the user or system level.

   1. From the Start option, select Settings, then select Control Panel.

      The Control Panel window appears.

   2. If you are using Microsoft Windows 2000, select the Administrative Tools icon.

   3. Select the Data Source (ODBC) icon.

      The ODBC Data Source Administrator dialog appears.

   4. From the User DSN tab, click Add.

      The Create New Data Source dialog appears.

   5. Select SQL Server, then click Finish.

      The Create a New Data Source to SQL Server dialog box appears.

   6. Type a name for the data source in the Name field.

   7. From the drop-down list, select the SQL Server database you want to connect to or type it in, then click Next.

   8. Verify the authenticity of the login ID, then click Next.

   9. Review the options, then click Next.

   10. Click Next.

   11. Click Finish.

       The ODBC Microsoft SQL Server Setup page appears.

   12. Click the Test Data Source option to ensure that you have set up the ODBC connection correctly, then click OK.

       If the connection fails, return to Step d and modify the connection details.

   13. Click OK.

       The DSN connection is now created.

2.5.2 Before Migrating From Microsoft Access

To configure a Microsoft Access database for migration:

1. Make backup copies of the database file or files.

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

3. 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.

4. 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.

   Note:

   SQL Developer supports linked tables to other Microsoft Access databases. SQL Developer automatically creates a user schema within the Oracle database for each Microsoft Access database migrated. However, Oracle recommends that you move all tables into a single Microsoft Access database to ensure that a single user schema is created in the destination database.

5. 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.

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

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

8. 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/
   
   

   You install the Oracle ODBC driver to allow Microsoft Access forms and reports to work with the migrated data. 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.

   Note:

   For more information about installing the networking products needed to connect to an Oracle database, see the installation guide for your Oracle Database release.

9. Set the Oracle ODBC Data Source in the ODBC Data Source Administrator, as follows:

   1. From the Start option, select Settings, then select Control Panel.

      The Control Panel window appears.

   2. If you are using Microsoft Windows 2000, select the Administrative Tools icon.

   3. Select the Data Source (ODBC) icon.

      The ODBC Data Source Administrator dialog appears

   4. From the User DSN tab, click Add.

      The Create New Data Source dialog box appears.

      Note:

      If you want to use the data source name (DSN) for multiple users on the same system, you should create a System DSN instead of a User DSN.

   5. Select the Oracle ODBC Driver from the list of ODBC drivers installed on the system, then click Finish.

   6. In the Data Source Name field, type a name to the ODBC data source.

      This data source name is the ODBC Data Source that you must specify in the Modify Microsoft Access Database dialog box of SQL Developer.

2.5.3 Before Migrating From MySQL

To configure a MySQL database for migration:

1. Install MySQLConnector/J release 3.0 on the system where you have installed SQL Developer, as follows:

   1. Download the MySQLConnector/J API from the MySQL Web site at:

      http://www.mysql.com/
      
      

   2. Extract the mysql-connector-java-3.x.xx-stable.zip file.

   3. From the com subdirectory zip the extracted files.

      Note:

      Ensure that the zip file contains the path information beginning with the com path name.

   4. Rename the zip file to the following:

      mysql-connector-java.zip
      
      

   5. Copy the mysql-connector-java.zip file to the following directory:

      On Windows:, copy to:

      OMWB_install_dir\Omwb\drivers
      
      

      On UNIX, copy to:

      OMWB_install_dir/Omwb/drivers
      
      

2. Ensure that the MySQL database is accessible by the root user. This user must have database administrative privileges.

2.7.1 Correcting Errors in the Converted Model

If error messages with the prefix Parse Exception are listed in the progress screen, the associated schema objects do not appear in the converted model. To complete the converted model:

1. Note the captured model schema object that caused the error.

2. Select that schema object in the captured model.

3. Inspect the properties on the schema object in the captured model for possible causes of the error.

4. Modify a property of the schema object in the captured model.

   For example, you might comment out one line of a stored procedure.

5. From the Object menu, select Parse.

   Note:

   The Parse option is available only after creating the converted model.

   SQL Developer attempts to create the converted model schema object from the captured model schema object.

   A progress screen appears.

6. If the error appears again, repeat steps 2 to 5.

   If necessary, comment out all the schema object's editable properties. This ensures that a schema object is created in the converted model, and therefore in the destination database. The migrated schema object will not function as expected, but acts as a placeholder so that you can create an equivalent Oracle schema object with the correct functionality.

2.7.2 Customizing the Converted Model

You can customize the converted model to take advantage of Oracle features identified during the planning phase. For example, you can make the following changes to the converted model:

• Modifying the Properties of a Schema Object

• Working with Tablespaces

• Changing the Default User Password

2.9.1 Transferring the Data Offline

To transfer the data offline, you generate and use scripts to copy data from the source database to the destination database. During this process you must:

• Use SQL Developer to generate the data unload scripts for the source database and corresponding data load scripts for the destination database.

• Run the data unload scripts to create data files from the source database using the appropriate procedure for your source database:

  • Creating Data Files From Microsoft SQL Server or Sybase Adaptive Server

  • Creating Data Files From Microsoft Access

  • Creating Data Files From MySQL

• Run the data load scripts using SQL*Loader to populate the destination database with the data from these data files as described in Section 2.9.1.4.

2.10.1 Testing Methodology

Many constraints shape the style and amount of testing that you perform on a database. Testing can contain one or all of the following:

• Simple data validation

• Full life cycle of testing addressing individual unit tests

• System and acceptance testing

You should follow a strategy for testing that suits your organization and circumstances. Your strategy should define the process by which you test the migrated application and Oracle database. A typical test method is the V-model, which is a staged approach where each feature of the database creation is mirrored with a testing phase.

Figure 2-2, "V-model with a Database Migration" shows an example of the V-model with a database migration scenario:

Figure 2-2 V-model with a Database Migration

Description of "Figure 2-2 V-model with a Database Migration"

There are several types of tests that you use during the migration process. During the testing stage, you go through several cycles of testing to enhance the quality of the database. The test cases you use should make sure that any issues encountered in a previous version of the Oracle database are not introduced again.

For example, if you have to make changes to the migrated schema based on test results, you may need to create a new version of the Oracle database schema. In practice, you use SQL Developer to create a base-line Oracle schema at the start of testing, and then edit this schema as you progress with testing.

2.10.2 Testing the Oracle Database

Use the test cases to verify that the Oracle database provides the same business logic results as the source database.

This procedure explains one way of testing the migrated database. Other methods are available and may be more appropriate to your business requirements.

To test the Oracle database:

1. Create a controlled version of the migrated database.

   Oracle recommends that you keep the database migration scripts in a source control system.

2. Design a set of test cases that you can use to test the Oracle database from unit to system level. The test cases should:

   1. Ensure the following:

      • All the users in the source database have migrated successfully

      • Privileges and grants for users are correct

      • Tables have the correct structure, defaults are functioning correctly, and errors did not occur during mapping or generation

   2. Validate that the data migrated successfully by doing the following:

      • Comparing the number of rows in the Oracle database with those in the source database

      • Calculating the sum of numerical columns in the Oracle database and compare with those in the source database

   3. Ensure that the following applies to constraints:

      • You cannot enter duplicate primary keys

      • Foreign keys prevent you from entering inconsistent data

      • Check constraints prevent you from entering invalid data

   4. Check that indexes and sequences are created successfully.

   5. Ensure that views migrated successfully by doing the following:

      • Comparing the number of rows in the Oracle database with those in the source database

      • Calculating the sum of numerical columns in the Oracle database and compare with those in the source database

   6. Ensure that triggers, procedures, and functions are migrated successfully. Check that the correct values are returned for triggers and functions.

3. Run the test cases against the migrated database.

4. Create a report that evaluates the test case results.

   These reports allow you to evaluate the data to qualify the errors, file problem reports, and provide a customer with a controlled version of the database.

5. If the tests pass, go to step 7.

   If all tests in the test cases pass or contain acceptable errors, the test passes. If acceptable errors occur, document them in an error report that you can use for audit purposes.

6. If the test cases fail:

   1. Identify the cause of the error.

   2. Identify the test cases needed to check the errors.

   3. Log an issue on the controlled version of the migrated database code in the problem report.

   4. Add the test case and a description of the problem to the incident tracking system of your organization, which could be a spreadsheet or bug reporting system. Aside from the test case, the incident log should include the following:

      • Provide a clear, concise description of the incident encountered

      • Provide a complete description of the environment, such as platform and source control version

      • Attach the output of the test, if useful

      • Indicate the frequency and predictability of the incident

      • Provide a sequence of events leading to the incident

      • Describe the effect on the current test, diagnostic steps taken, and results noted

      • Describe the persistent after effect, if any

   5. Attempt to fix the errors.

   6. Return to step 1.

7. Identify acceptance tests that you can use to make sure the Oracle database is an acceptable quality level.

select count(*) from emp

select count(*) from emp

select sum(salary) from emp

select sum(salary) from emp

2.11.1 Choosing a Rollout Strategy

The strategy that you use for migrating a third-party database to an Oracle database must take into consideration the users and the type of business that may be affected during the transition period. For example, you may use the Big Bang approach because you do not have enough systems to run the source database and Oracle database simultaneously. Otherwise, you may want to use the Phased approach to make sure that the system is operating in the user environment correctly before it is released to the general user population. You can use one of the following approaches.

2.11.2 Deploying the Destination Database

There are several ways to deploy the destination database. The following task is an example that you should use as a guideline for deploying the destination database.

1. Configure the hardware, if necessary.

   In a large scale or complex environment, you must design the disk layout to correspond with the database design. If you use redundant disks, align them in stripes that you can increase as the destination database evolves. You must install and configure the necessary disks, check the memory, and configure the system.

2. Make sure the operating system meets the parameters of the Oracle configuration.

   Before installing any Oracle software, make sure that you have modified all system parameters. For more information about modifying system parameters, see the relevant installation guide for your platform, such as Solaris Operating System.

3. Install the Oracle software.

   Aside from the Oracle software that allows you to create an Oracle database, you may need to install ancillary software to support the application, such as Extract Transformation and Load (ETL) Software for data warehousing.

4. Create the destination database from the source database and migrate the data to the Oracle database.

   There are several ways of putting the destination database into production after testing it, such as:

   • Place the successfully tested database into production. The test system is now the production system.

   • Use Oracle Export to extract the destination database from the successfully tested database and use Oracle Import to create that database within the production environment.

   • Use the tested migration scripts to create the Oracle database and populate it with data using SQL*Loader.

5. Perform the final checks on the destination database and applications.

6. Place the destination database into production using one of the rollout strategies.

7. Perform a final audit by doing the following:

   • Audit the integrity of the data

   • Audit the validity of the processes, such as back-up and recovery

   • Obtain sign-off for the project, if necessary

2.13.1 Migration Menu

The Migration menu contains options related to migrating third-party databases to Oracle.

Show Getting Started Guide: Displays steps for getting started quickly with a migration.

Repository Management: Enables you to create, delete, or truncate (remove all data from) a migration repository; select the current migration repository; and disconnect from the current migration repository (which deactivates the current repository but does not disconnect from the database).

Microsoft Access Exporter: Contains submenu items from which you specify the version of the exporter tool to use to create an XML file to be used for creating the captured model. You can also use the exporter tool to export table data. Specify the exporter tool version for the version of Access that is on your PC and that was used to create the .mdb file.

Migrate Data: Displays a dialog box for performing no online migration of table data from the source database to the Oracle schema.

Script Generation: Generate Oracle DDL displays DDL (data definition language) statements in a SQL Worksheet window, where you can then run the script to create the Oracle schema and schema objects; Generate Data Move Scripts displays a dialog box for specifying the location in which to create files for performing an offline migration of table data from the source database to the Oracle schema.

Capture Exporter XML (Microsoft Access migrations): Creates a captured model of a Microsoft Access database from the XML file created by the exporter tool.

Translation Scratch Editor: Displays the translation scratch editor, which is explained in Section 2.13.5.

2.13.2 Other Menus: Migration Items

The View menu has the following items related to database migration:

• Captured Objects: Displays the Captured Objects navigator.

• Converted Objects: Displays the Converted Objects navigator.

2.13.3 Migration Preferences

The SQL Developer user preferences window (displayed by clicking Tools, then Preferences) contains a Migration pane with several related subpanes, and a Translation pane with a Translation Preferences subpane.

For information about these preferences, click Help in the pane, or see Section 1.12.9, "Migration".

2.13.4 Migration Log Panes

Migration Log: Contains errors, warnings, and informational messages relating to migration operations.

Logging Page: Contains an entry for each migrated-related operation.

Data Editor Log: Contains...

2.13.5 Using the Translation Scratch Editor

You can use the translation scratch editor to enter SQL statements and have them translated to PL/SQL statements. You can specify translation from T-SQL to PL/SQL or from Microsoft Access SQL to PL/SQL.

You can display the scratch editor by clicking Migration, then Translation Scratch Editor. The scratch editor has the interface shown in the following figure:

Scratch Editor toolbar (under the Scratch Editor tab): Contains icons for the following operations:

• Open lets you open a file with SQL statements to be placed in the Enter SQL Statement box.

• Translate translates the SQL statements according to the type of translation specified in the drop-down menu, and displays the results in the translated statements box.

• Translation Dif Viewer displays a read-only pane showing the original and translated statements. It provides color-coded comparison of the original and translated SQL, to display semantic similarities between the source and translated code.

• Save Original SQL File lets you save the original file to a location and name of your choice.

• Erase All erases the contents of the Enter SQL Statement box.

• A drop-down menu lets you select the type of translation: T-SQL to PL/SQL for Transact-SQL, or Access to PL/SQL for Microsoft Access.

Enter SQL Statement: The statement or statements to be translated. For multiple statements, each non-PL/SQL statement must be terminated with either a semicolon or (on a new line) a slash (/), and each PL/SQL statement must be terminated with a slash (/) on a new line. SQL keywords are automatically highlighted.

Translated statements toolbar (under Enter SQL Statement): Contains icons for the following operations on the translated statement or statements:

• Save Generated PL/SQL File lets you save the generated statements to a PL/SQL script file.

• Erase All erases the generated statements.

• Validate SQL validates the SQL statements.

Tabs display panes with the following information:

• Result: Displays the results of the most recent Translate operation.

• Source Tree: Displays the results in expandable tree format.