2 Overview of Migration

This chapter includes an overview of the major steps required to migrate a version 7 or version 6 database to Oracle8i. These migration procedures transform an existing version 7 or version 6 database system (including associated applications) into an Oracle8i database system. Oracle8i is compatible with all earlier Oracle versions and releases. Therefore, databases transformed using the migration procedures described in this book can work in the same manner as in earlier versions and, optionally, can leverage new Oracle8i functionality.

Several preparatory steps are required before you migrate the current production database. After migrating the database, you should perform several additional test steps to test the migration. Other procedures enable you to add new Oracle8i functionality to existing applications.

Overview of Migration Steps

Before you perform a database migration, you should understand the major steps in the migration process. These major steps apply to all operating systems, with the possible exception of a few operating system-specific details identified in your operating system-specific Oracle documentation.

Note:

The rest of this chapter describes migration. If you plan to perform an operation other than migration, such as upgrading or downgrading, then you can proceed to the appropriate chapter for the operation.

Figure 2-1 Major Migration Steps

Careful planning and use of Oracle8i tools can ease the process of migrating a database to Oracle8i. You can use one of the following migration methods to migrate your database:

The Oracle Data Migration Assistant is the easiest way to migrate an entire database

Migration utility is more complicated to use but provides more control over the process of migrating an entire database.

Export/Import and SQL copy utilities enable piecemeal migration of parts of a database.

The following sections contain a brief outline of the major steps shown in Figure 2-1. The purpose of these descriptions is to familiarize you with the major steps in the migration process. For detailed instructions, refer to the appropriate chapters and sections later in this book.

Step 1: Prepare to Migrate

Become familiar with the features of the Oracle8i database. SeeGetting to Know Oracle8ifor an overview of these features.

Decide which migration method to use, based on considerations involving the current production database, your migration objectives, and the behavior and capabilities of available migration methodologies.

Estimate and secure the system resources required for the migration.

Develop a plan for testing the migration with an Oracle8i test database and a plan for testing the migrated Oracle8i production database.

Prepare a backup strategy so that you can recover quickly from any unexpected problems or delays.

Step 2: Test the Migration Process

Perform a test migration using a test database. The test migration should be conducted in an environment created for migration testing and should not interfere with the actual production database.

Step 3: Test the Migrated Test Database

Perform the tests you planned in Step 1 on the version 7 or version 6 test database and on the version 7 or version 6 test database that was migrated to Oracle8i.

Compare results, noting anomalies between test results on the version 7 or version 6 test database and on the migrated Oracle8i database.

Investigate ways to correct any anomalies you find and then implement the corrections.

Repeat Step 1, Step 2, and the first parts of Step 3, as necessary, until the test migration is completely successful and works with any required applications.

Step 6: Tune and Adjust the New Production Database

Tune the new Oracle8i production database. The Oracle8i production database should perform as good as, or better than, the Oracle database prior to migration. Chapter 8 describes these tuning adjustments.

Determine which new features of the Oracle8i database that you want to use and update your applications accordingly.

Develop new database administration procedures as needed.

Do not migrate production users to the Oracle8i database until all applications have been tested and operate properly. Chapter 10 describes considerations for updating applications.

During migration, multi-versioning can be a useful feature because you can keep multiple copies of the same database on one computer system. You can use the existing version as your production environment while you test the new version.

Role of the Database Administrator During Migration

Typically, the database administrator (DBA) is responsible for ensuring the success of the migration process. The DBA is usually involved in each step of the process, except for steps that involve testing applications on the migrated database.

The specific DBA duties typically include the following:

meeting with everyone involved in the migration process and clearly defining their roles during migration

performing test migrations

scheduling the test and production migration process

performing backups of the version 7 or version 6 production database

completing the production database migration

performing backups of the newly migrated Oracle8i production database

Role of the Application Developer During Migration

The application developer is responsible for ensuring that applications designed for the version 7 or version 6 database work correctly with the migrated Oracle8i database. Application developers often test applications against the migrated Oracle8i database and decide which new features of Oracle8i should be used.

Before migrating the Oracle7 production database, the DBA or application developer should install an Oracle8i test database. Then, the application developer can test and modify the applications, if necessary, until they work with their original (or enhanced Oracle8i) functionality.

The following references provide information about identifying differences in the migrated Oracle8i database that could affect particular applications. Application developers can use these differences to guide modifications to existing applications.