7
Installing, Migrating, and Upgrading Databases

This chapter describes the options available to you when you have existing databases on your computer and want to install the latest release of Oracle8 Enterprise Edition. In particular, it describes how to coexist different database releases in the same Oracle home or in multiple Oracle homes, and how to migrate an Oracle7 database or upgrade an earlier Oracle8 database release to the current release of Oracle8 Enterprise Edition. This chapter also includes information on migrating a Microsoft Access database to an Oracle8 database.

Specific topics discussed are:

• Intended Audience

• What To Do With Previous Oracle Database Releases

• Database Coexistence and Multiple Oracle Homes Overview

• Migrating, Upgrading, and Downgrading Overview

• Export/Import Overview

• Version 8 and Version 7 Client/Server Configurations

• Installing Two or More Databases Into the Same Oracle Home

• Installing Databases Into Multiple Oracle Homes

• Migrating an Oracle7 Database to Version 8

• Upgrading an Oracle8 Database Release 8.0.x to 8.0.6

• Downgrading an Oracle8 Database to Release 8.0.x or Version 7

• Migrating a Microsoft Access Database

Intended Audience

Read this chapter if you have existing Oracle7 and/or Oracle8 databases on your computer and you want to install Oracle8 Enterprise Edition release 8.0.6. If you are installing Oracle8 Enterprise Edition on a computer that has no other Oracle database releases, you do not have to read this chapter.

Additional Information: See Oracle8 Enterprise Edition Installation for Windows NT if you want to install Oracle8 Enterprise Edition on a computer containing no other databases.

The generic Oracle8 Migration guide is the primary source of migration information in the Oracle documentation set. Read the first three chapters of that guide for information on how to prepare your existing databases for migration before performing a migration. Information on how to run the various migration and upgrade utilities is also provided in the generic guide, but the focus is on UNIX. This chapter provides information on using these utilities on Windows NT.

What To Do With Previous Oracle Database Releases

If you already have Oracle7, or Oracle7 and Oracle8 databases on your computer and want to install release 8.0.6, the following options are available to you.

• Install release 8.0.6 in an Oracle home where an Oracle7 release 7.x database already exists (this procedure is known as database coexistence). Note that you cannot coexist Oracle8 release 8.0.6 and release 8.0.x in the same Oracle home; the 8.0.6 installation overwrites the 8.0.x installations.

• Install release 8.0.6 in a separate Oracle home on the same computer (this procedure is known as using multiple Oracle homes).

• Migrate release 7.x to release 8.0.6.

• Upgrade release 8.0.x to release 8.0.6.

• Use Export/Import utilities to physically copy data in the previous database release to a new release 8.0.6 database.

If you are not sure what option is best for you, read the following overview sections:

• Database Coexistence and Multiple Oracle Homes Overview

• Migrating, Upgrading, and Downgrading Overview

• Export/Import Overview

Database Coexistence and Multiple Oracle Homes Overview

Releases of Oracle for Windows NT and Windows 95 prior to release 8.0.4 only supported single Oracle homes, allowing you to install and run Oracle products in a single Oracle home. Different versions of Oracle products could be installed in the same Oracle home provided they had different second-digit release numbers. For example, you could install release 7.2 products and release 7.3 products in the same Oracle home (database coexistence). However, you could not install multiple third-digit releases of the same products. For example, you could not install release 7.3.2 and release 7.3.3 versions of the same Oracle products on the same computer; one installation would overwrite the other.

The multiple Oracle homes feature enables you to install one or more releases of Oracle products on the same computer in multiple Oracle homes. For example, with multiple Oracle homes, you can install release 8.0.6 products and 8.0.4 products in different Oracle homes on the same computer. You can still install different releases of Oracle products in the same Oracle home provided they have different second-digit release numbers. See Chapter 6, "Using Multiple Oracle Homes" for more information.

Migrating, Upgrading, and Downgrading Overview

This section explains the difference between migrating, upgrading, and downgrading, and lists the Oracle database versions that can be migrated or upgraded.

What is Migrating?

Migrating is the process of transforming one database version to a later database version. For example, transforming an Oracle7 database to an Oracle8 database is migrating the database system. The term migrating is also used in this guide to refer to the transformation of a Microsoft Access database to an Oracle8 database.

What is Upgrading?

Upgrading is the process of transforming one database release to another database release of the same database version. For example, transforming an Oracle8 database release 8.0.4 to release 8.0.6 is upgrading the database system.

What is Downgrading?

Downgrading is the process of transforming an installed version of an Oracle database from a later release back into an earlier release. For example, transforming an Oracle database from release 8.0.6 back into release 8.0.3 is downgrading, and transforming an Oracle database from version 8 back into version 7 is downgrading.

Migrating and Upgrading Using Multiple Oracle Homes

You can easily migrate or upgrade databases across multiple Oracle homes. If you use the graphical user interface (GUI) Oracle Data Migration Assistant, all database instances on your system are displayed in a drop-down list. You select the Oracle database instance you want to migrate or upgrade and the assistant takes care of any multiple Oracle homes issues.

If you use the command line tools, MIG80 to migrate, or a U*.SQL script to upgrade, you need to copy files from one Oracle home directory to another. You must also ensure the PATH variable is set correctly so that any Oracle database tools you run are started from the correct Oracle home directory.

Checklist of Database Release Numbers

Check that your Oracle database release can be migrated or upgraded directly to Oracle8 Enterprise Edition. This table provides a list of the database releases you can migrate or upgrade and the tools you can use to perform these tasks:

Oracle Database Release	Use This Tool...
Releases prior to 7.1.3.3.6	If the database version precedes release 7.1.3.3.6, migrate it to at least release 7.1.3.3.6 before using MIG80 or Oracle Data Migration Assistant to migrate it to release 8.0.6. See the documentation that accompanied your previous database release for information on how to migrate it to release 7.1.3.3.6.
Release 7.1.3.3.6 or later	MIG80 can migrate databases that are Oracle7, release 7.1.x or later to release 8.0.6. Oracle Data Migration Assistant migrates from release 7.1.3.3.6 or later to release 8.0.6.
Release 8.0.3.0.0 or later	SQL scripts executed in Server Manager can upgrade databases release 8.0.3.0.0 or later to the current Oracle8 database release. Oracle Data Migration Assistant upgrades from release 8.0.3.0.0 or later to release 8.0.6.

Export/Import Overview

An alternative method of migrating or upgrading is to:

1. Export your data from the source database using the Export Utility (EXP80). The export physically copies the data to the export dump file.

2. Create the version 8 database into which you will import the exported data.

3. Import the exported data into the new version 8 database using the Import Utility (IMP80).

The Export Utility puts all of the data in one large binary file that can require large amounts of disk space.

Additional Information: See "Choose a Migration Method" in Chapter 2 "Preparing to Migrate" of Oracle8 Migration for information on when to use the Export/Import utilities for migrating a database. See "Export an Existing Database" and "Import a Database" for information on using these tools.

Version 8 and Version 7 Client/Server Configurations

Oracle7 and Oracle8 clients can communicate either with Oracle7 or Oracle8 databases. This functionality gives you maximum flexibility when designing your network and deciding when to:

• Install Oracle7 and Oracle8 Databases in the Same Oracle Home

• Install Oracle7 and Oracle8 Databases in Multiple Oracle Homes

• Install Oracle7 and Oracle8 Databases on Separate Computers

• Migrate an Oracle7 Database to an Oracle8 Database

• Upgrade an Oracle8 Database to the Current Oracle8 Database Release

• Migrate Oracle7 Clients to Oracle8

Consider the following database coexistence issues before you decide which of the above options is most suitable for your requirements:

• Oracle7 Database Applications

• Oracle7 Client Connections to Oracle8 Databases

• Oracle8 Client Connections to Oracle7 Databases

Oracle7 Database Applications

Can all my Oracle7 applications run on an Oracle8 database?

Most Oracle7 applications can run on an Oracle8 database. Some applications cannot run on an Oracle8 database unless you upgrade them to versions that support Oracle8 databases. If you have a combination of Oracle7 and Oracle8 applications, you may want to have an Oracle7 database and Oracle8 database exist on the same computer, until you have time to upgrade all your Oracle7 applications to Oracle8. Contact your application vendor to check if your third-party applications are supported with Oracle8 Enterprise Edition.

Oracle7 Client Connections to Oracle8 Databases

Check the following criteria to ensure successful Oracle7 client connections to an Oracle8 database. If the Oracle7 client and Oracle8 database are located in:

• the same Oracle home:

  install both SQL*Net Client 2.3.x and Net8 Server in this home

• different Oracle homes on the same computer:

  install SQL*Net Client 2.3.x in the Oracle7 client home and Net8 Server in the Oracle8 home

• different computers:

  install SQL*Net Client 2.3.x in the Oracle7 client home and Net8 Server in the Oracle8 home

If you are using these releases:

• Oracle7 client release 7.3.4 and SQL*Net Client release 2.3.4:

  you can connect to the Oracle8 database without specifying a service name. Oracle7 client automatically uses the Bequeath Protocol Adapter when connecting to a local Oracle8 database.

• Oracle7 release 7.3.3 (or lower) and SQL*Net release 2.3.3 (or lower):

  you need to create a service name using SQL*Net Easy Configuration or Oracle Network Manager in the SQL*Net Client version 2.x TNSNAMES.ORA file. Ensure you specify this service name in the connect string when connecting to the Oracle8 database. The Bequeath Protocol Adapter is not supported when connecting from an Oracle7 client (release 7.3.3 or lower) to an Oracle8 database.

Oracle8 Client Connections to Oracle7 Databases

Check the following criteria to ensure successful Oracle8 client connections to an Oracle7 database. If the Oracle8 client and Oracle7 database are located in:

• the same Oracle home:

  install both Net8 Client and SQL*Net Server 2.3.x in this home

• different Oracle homes on the same computer:

  install Net8 Client in the Oracle8 client home and SQL*Net Server 2.3.x in the Oracle7 home

• different computers:

  install Net8 Client in the Oracle8 client home and SQL*Net Server 2.3.x in the Oracle7 home

Install Oracle7 and Oracle8 Databases in the Same Oracle Home

Install Oracle7 and Oracle8 databases in the same Oracle home directory and have both Oracle7 and Net8 clients connecting to Oracle7 and Oracle8 databases. The figure below gives an example of this network configuration:

You can install different versions of Oracle databases in the same Oracle home provided they have different first or second-digit versions. For example, you can have release 7.2.x, 7.3.x, and 8.0.x databases in the same Oracle home.

You cannot install multiple third-digit releases of the same products. For example, you cannot install release 7.3.2 and release 7.3.3, or release 8.0.3 and release 8.0.4, in the same Oracle home; one installation overwrites the other.

Ensure that each database instance has a unique SID. In particular, be careful that you do not use the default SID ORCL for subsequent installations if you already have a starter database with the SID ORCL installed. If you do so, the services of the later installation overwrite the services of the earlier installation.

Install Oracle7 and Oracle8 Databases in Multiple Oracle Homes

Install Oracle7 and Oracle8 databases in multiple (separate) Oracle homes and have both Oracle7 and Net8 clients connecting to Oracle7 and Oracle8 databases.

New Style Oracle Homes

Multiple Oracle homes functionality only works with releases 8.0.4, 8.0.5, and 8.0.6. These are known as new style Oracle homes.

Old Style Oracle Homes

If you have, for example, release 7.3.3 products already installed, you cannot install any other release 7.x products in a separate Oracle home. Also, if you have release 8.0.3 or earlier 8.0.x products already installed, you cannot install any other of these products in a separate Oracle home. These are known as old style Oracle homes. The figure below gives an example of this network configuration:

Install Oracle7 and Oracle8 Databases on Separate Computers

Install Oracle7 and Oracle8 databases on separate computers and have both Oracle7 and Net8 clients connecting to both databases. The figure below shows two computers and a number of Oracle7 and Oracle8 clients. On each computer you can have a mix of databases and products in both single and multiple Oracle homes.

Migrate an Oracle7 Database to an Oracle8 Database

Migrate your Oracle7 database to an Oracle8 database and have both Oracle7 and Oracle8 clients connecting to the Oracle8 database. You can migrate your Oracle7 database to an Oracle8 database either in the same Oracle home or in a different Oracle home. See "Migrating an Oracle7 Database to Version 8" for instructions. The figure below illustrates this network configuration:

Upgrade an Oracle8 Database to the Current Oracle8 Database Release

Upgrade your Oracle8 database, for example, release 8.0.4 to release 8.0.6 and have both Oracle7 and Oracle8 clients connecting to the release 8.0.6 Oracle8 database. You can upgrade databases either in the same Oracle home or across different Oracle homes. See "Upgrading an Oracle8 Database Release 8.0.x to 8.0.6" for instructions. The figure below illustrates this network configuration:

Migrate Oracle7 Clients to Oracle8

Migrate some or all of your Oracle7 clients to Oracle8 release 8.0.6 and migrate your Oracle7 database to an Oracle8 database or upgrade your Oracle8 database to the current Oracle8 release at a later date. See Net8 Getting Started for Windows NT and Windows 95/98 for instructions. The figure below illustrates this network configuration.

Multi-Versioning

You can run different versions of Oracle databases on the same computer system at the same time. However, each version can only access a database that is consistent with its version. For example, if you have version 7 and version 8 of Oracle installed on the same computer system, the version 7 server can access version 7 databases, but not version 8 databases, and the version 8 server can access version 8 databases but not version 7 databases. The only way for a version 8 database to read version 7 database files is to perform a migration. You should be aware that after migration, the version 7 database will no longer be able to read the files.

Installing Two or More Databases Into the Same Oracle Home

In the following example, an Oracle7 release 7.3.3 starter database named ORACLE with a SID of ORCL is already installed in C:\ORANT. Now, create an Oracle release 8.0.6 database named PROD with a SID of PROD in C:\ORANT.

To install an Oracle8 database and Oracle7 database into the same Oracle home:

1. Ensure you have enough hard disk space and RAM for both databases. You need to add the system requirements for Oracle8 Enterprise Edition and Oracle7 Server to determine the total system requirements. See Oracle8 Enterprise Edition Installation for Windows NT for system requirements.

2. Ensure all Oracle7 services are stopped. See "Managing Oracle Services" for information on how to stop services.

3. Install Oracle8 Enterprise Edition for Windows NT from the CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

   The Oracle Installation Settings dialog box appears.

   1. Do not enter a value in the Name field of the Oracle Installation Settings dialog box.

   2. Set the Oracle home directory location to the same directory where release 7.3.3 is already installed. In this example, enter C:\ORANT in the Location field of the Oracle Installation Settings dialog box. Click OK.

   The Select Installation Settings dialog box appears.

4. Select Oracle8 Enterprise Edition from the Select Installation Options dialog box, then click OK.

   The Select Oracle8 Cartridge dialog box appears.

5. Select any cartridges you are licensed to install, then click OK.

   The Previous Version of Oracle Database Detected dialog box appears indicating that Oracle Installer has detected an earlier version of the database. You are asked if you want to migrate your Oracle7 database to release 8.0.6 using Oracle Data Migration Assistant.

6. Click No. If you click Yes, Oracle Data Migration Assistant is launched at the end of installation. Do not click Yes to run Oracle Data Migration Assistant while you are installing another database into the same Oracle home as an existing database.

   The Select a Starter Database Configuration dialog box appears.

7. Select Custom Configuration (allows you to create a customized database).

8. Complete Oracle8 Enterprise Edition installation. At the end of installation, the Oracle Database Assistant is launched.

   The following Oracle Database Assistant window appears:

   
   
9. Respond to instructions in each Oracle Database Assistant window, and click Next when you are ready to continue to the next window.

10. When the following Oracle Database Assistant window appears, you will notice that the Database Name and SID fields are automatically set to ORC1. Substitute PROD in both of these fields. Do not set the SID to ORCL, as you will overwrite the Oracle7 release 7.3.3 starter database.

    
    

    When you get to the last window, click Finish to start the creation of the PROD database. More documentation is included with the assistant Help.

Installing Databases Into Multiple Oracle Homes

In the following example, an Oracle7 release 7.3.3 starter database called ORACLE with a SID of ORCL is already installed in C:\ORANT. Now, install the Oracle release 8.0.6 starter database ORCL in a separate Oracle home directory called C:\ORANTv8 with an Oracle home name of TESTv8.

To install an Oracle8 database and Oracle7 database in multiple (separate) Oracle homes:

1. Ensure you have enough hard disk space and RAM for both databases. You need to add the system requirements for Oracle8 Enterprise Edition and Oracle7 Server to determine the total system requirements. See Oracle8 Enterprise Edition Installation for Windows NT for system requirements.

2. Ensure all Oracle7 services are stopped. See "Managing Oracle Services" for information on how to stop services.

3. Install Oracle8 Enterprise Edition for Windows NT from the CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

   The Oracle Installation Settings dialog box appears.

   1. Enter the name of the new Oracle home in the Name field of the Oracle Installation Settings dialog box. In this example, enter TESTv8.

   2. Enter the location of the Oracle home directory where you want to install release 8.0.6. In this example, enter C:\ORANTv8 in the Location field of the Oracle Installation Settings dialog box. Click OK.

   The Select Installation Settings dialog box appears.

4. Select Oracle8 Enterprise Edition from the Select Installation Options dialog box, then click OK.

   The Select Oracle8 Cartridge dialog box appears.

5. Select any cartridges you are licensed to install, then click OK.

   The Select a Starter Database Configuration dialog box appears.

6. Select Typical Configuration (allows you to install a pre-configured starter database).

7. Complete Oracle8 Enterprise Edition installation.

   During installation of the release 8.0.6 database, Oracle Installer detects the listener of the previously installed release 7.3.3 database. To avoid conflicts of listening addresses (for example, the port number for TCP/IP), the new release 8.0.6 listener is not started and is set to Manual Startup mode. After installation is complete, modify the release 8.0.6 LISTENER.ORA file to resolve possible conflicts in listening addresses, and then start the listener. This is required to enable the release 8.0.6 database to accept connections from clients. See Net8 Getting Started for Windows NT and Windows 95/98 for information on how to modify the LISTENER.ORA file.

Migrating an Oracle7 Database to Version 8

This section describes how to migrate an Oracle7 database to the current Oracle8 database release. You can choose either of the following tools to perform a migration:

• Oracle Data Migration Assistant

• MIG80

Oracle Corporation recommends that new users use Oracle Data Migration Assistant to migrate databases because it is the easiest method to perform a migration. If you want to perform a migration manually using command line tools, use MIG80.

Before you start a migration using the assistant or MIG, read the following sections:

Ten Issues That Can Affect Oracle7 to Oracle8 Migration

The following table lists and describes the ten issues you should be aware of that can affect Oracle7 to Oracle8 migration.

Issues That Affect Migration	Description
Running out of space	Version 8 binaries may require as much as three times the disk space required by version 7 binaries. This requirement may cause you to run out of disk space during migration. It is very important that you read "System Considerations and Requirements" and "Prepare the Version7 Source Database for Migration" in Oracle8 Migration to find out more about this and other requirements before you migrate. During migration, the data dictionary requires 50% more space to hold both Oracle7 and Oracle8 data dictionaries. Actual usage can be verified by running MIG in CHECK_ONLY mode.
Duration of migration is unrelated to database size	The time it takes to migrate is not dependent on the size of the database, but on the number of objects in the data dictionary. For example, actual migration for a 3 1/2 GB database with 25,473 objects on a Sun E6000 with 20 CPUs, with datafiles stripped on the file system on 128 KB slices can take 1 1/2 hours. Remember to allow extra time for backing up and restoring database in case of problems.
Avoiding problem areas	Check for usage of ROWIDs in both user columns as well as application code (including triggers & packaged procedures). These may require to be converted to use the DBMS_ROWID package. Check the names of any Oracle7 database objects (for example, tables and columns) that use names that are key words or reserved words for Oracle8i Enterprise Edition. Usage of key words and reserved words can cause unexpected failures during migration. See Appendix C, "Oracle Reserved Words" of Oracle8 SQL Reference for a list of reserved words. Certain version 7 initialization parameters are obsolete in version 8. Remove all obsolete parameters from the release 7.x INITSID.ORA file that start a version 8 instance. Obsolete parameters may cause errors if used with a version 8 database. Also, alter any parameter whose syntax has changed in version 8. See Appendix B, "Changes to Initialization Parameters" of Oracle8 Migration for lists of new, changed, and obsolete parameters.
Compatibility	Make sure that all Oracle product versions, operating system versions, and third-party software versions are certified against Oracle8. See "Overview" for the list of supported Windows operating systems and versions. See "Oracle Products for Windows NT, Windows 95, and Windows 98" for a list of supported Oracle product versions for this release.
Invalid objects and lost statistics	Migration leaves all objects (packages, triggers, views, and so on) invalid except for tables. All other objects must be made valid again by recompilation. This can either be done manually (preferably by building a dependency tree before migration from dependency), otherwise this is done automatically as the objects are first accessed. The latter will of course slow down initial access. All estimated or calculated statistics are lost during migration. These need to be recalculated to ensure proper functionality of the Cost Based Optimizer. Some bitmapped indexes will get invalidated. Check all bitmapped indexes in the DBA_INDEXES table and recreate any that are marked as status unusable.
Editing the registry	If you edit the registry for any reason during the migration process, you need to reboot your computer.
Read-only tablespace confusions	Oracle7 read-only tablespaces are readable by Oracle8 and do not require any conversion. But to prevent Oracle8 rowid conversions to take place every time a table is accessed, the tablespaces in read-only mode should be made read-write. Perform full table scans on all tables in the tablespace. After the full table scans are complete, you can put the tablespaces in read-only mode again.
The point of no return	You can return the database to an Oracle7 version up until the ALTER DATABASE CONVERT command is run. If a failure occurs during ALTER DATABASE CONVERT (when it is converting the physical file headers of the datafiles), you must restore the database from backup and rerun the migration. Do not open the database between running the migration and executing the ALTER DATABASE CONVERT command.
Preventing large restores	To avoid restoring the entire database due to any failures during the ALTER DATABASE CONVERT, put all tablespaces, except SYSTEM and ROLLBACK into read-only or offline normal mode. This causes the ALTER DATABASE CONVERT command to only convert the datafile headers for SYSTEM and ROLLBACK. If any errors occur, you need only restore the datafiles for the SYSTEM and ROLLBACK and rerun the migration. If the migration is successful, the headers for the rest of the datafiles will be converted when they are read-write or online.
Testing	Most migration problems can be avoided if a test migration is performed first. Performing a test migration helps raise any problems that can occur as well as letting you see the amount of time it takes to migrate. See "Test the Migration Process" in Chapter 2, "Preparing to Migrate" in Oracle8 Migration.

Migration Networking Issues

If you perform a migration, you may need to resolve the following networking issues:

• Migrating Oracle7 Clients

• Using the Net8 Listener

• Editing the LISTENER.ORA File for Multiple Oracle Homes

• Installing Appropriate Versions of SQL*Net

Migrating Oracle7 Clients

Although Oracle7 clients using SQL*Net Client version 2.x can connect to Oracle8 databases, they should be migrated to Oracle8 clients configured with Net8 when their applications are upgraded to version 8. Note that SQL*Net version 2.x can coexist with Net8 in the same Oracle home directory.

Using the Net8 Listener

To use the Net8 listener, you may need to change your network configuration on either the SQL*Net version 2.x or Net8 configurations to prevent a conflict. For example, you may need to change:

• Port numbers on a TCP/IP network so that they are unique

• Service name on an SPX/IPX network

• Pipe name on a Named Pipes network

You may also need to start the Net8 listener and change the status of the service to Automatic Startup, depending upon your network needs. If you make changes to the listener, you must make changes to client configuration files to reflect those listener changes.

SQL*Net version 2.x uses configuration files from ORACLE_HOME\NETWORK\ADMIN, while Net8 uses files from ORACLE_HOME\NET80\ADMIN by default. If you want SQL*Net version 2.x and Net8 to use configuration files from the same directory, you can set the registry variable TNS_ADMIN.

Additional Information: See Net8 Getting Started for Windows NT and Windows 95 for more information on setting TNS_ADMIN.

Editing the LISTENER.ORA File for Multiple Oracle Homes

Using MIG80

When you migrate from an Oracle7 database in one Oracle home to an Oracle8 database release 8.0.6 in a different Oracle home, remove the SID from the Oracle7 Oracle home's LISTENER.ORA file and add it to the release 8.0.6 Oracle home's LISTENER.ORA file.

Using Oracle Data Migration Assistant

When you migrate from an Oracle7 database in one Oracle home to an Oracle8 database release 8.0.6 in a different Oracle home, the assistant does not remove the SID from the Oracle7 Oracle home's LISTENER.ORA file. To prevent a conflict when you start the Oracle7 listener, remove the SID entry from the Oracle7 Oracle home's LISTENER.ORA file.

Installing Appropriate Versions of SQL*Net

When migrating from Oracle7 Server release 7.3.x to Oracle8 release 8.0.6, install the appropriate version of SQL*Net for the server before using Oracle Data Migration Assistant or MIG80. Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net. You do not need to install a SQL*Net patch when migrating from Oracle7 release 7.3.4 to Oracle8 release 8.0.6.

Migrating from...	Install...
Oracle7 release 7.3.2.x and higher to Oracle8	SQL*Net release 2.3.2.1.4 and SQL*Net patch 2.3.2.1.12 Note: If you do not have SQL*Net release 2.3.2.1.4 on your system, you must install it before installing SQL*Net patch 2.3.2.1.12. SQL*Net release 2.3.2.1.4 is not available on the release 8.0.6 CD-ROM. You must install it from the release 7.3.2 CD-ROM.
Oracle7 release 7.3.3.x and higher to Oracle8	SQL*Net release 2.3.3.0.3
	To install SQL*Net patch 2.3.2.1.12 or 2.3.3.0.3: Start Oracle Installer from the CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions. Answer questions about language and Oracle home directory location. Select Custom Installation. The Software Asset Manager window appears. Click From... Navigate to \PATCHES\SQLNET\232112 on the CD-ROM if you want to install SQL*Net patch 2.3.2.1.12. Navigate to \PATCHES\SQLNET\23303 if you want to install SQL*Net release 2.3.3.0.3. Select SQL*Net Server 2.3.2.1.12 and SQL*Net Client 2.3.2.1.12 if you want to install SQL*Net patch 2.3.2.1.12. Select SQL*Net Server 2.3.3.0.3 and SQL*Net Client 2.3.3.0.3 if you want to install SQL*Net patch 2.3.3.0.3. Click Install. A window appears showing the progress of the installation. After installation is complete, a message appears confirming the installation. Click Exit to quit Oracle Installer.

Migrating Using Oracle Data Migration Assistant

Oracle Data Migration Assistant helps you migrate data from an Oracle7 database to an Oracle8 database. During installation of Oracle8 Enterprise Edition, you are prompted to migrate a database with this assistant if Oracle Installer detects that an earlier database release exists on your computer. If you do not want to migrate a database during the installation process, you can just install the assistant and use it later.

What To Do Before Using Oracle Data Migration Assistant

Complete the following steps before you use this assistant:

• Read the READMEMIG.DOC located in the ORACLE_HOME\RDBMS80 directory for migration information that is new to this release. This file contains special migration, upgrade, downgrade, word-change, and rolling upgrade instructions for release 8.0.6.

• Read Chapter 4, "Migration Using the Oracle Data Migration Assistant" in Oracle8 Migration for background information before starting the migration process.

  Note: Version 8 binaries may require as much as three times the disk space required by version 7 binaries. This requirement may cause you to run out of disk space during migration. It is very important that you read "System Considerations and Requirements" and "Prepare the Version7 Source Database for Migration" to find out more about this and other requirements before you migrate. You cannot use Oracle Data Migration Assistant in an Oracle Parallel Server environment.

• Ensure the database you want to migrate is at least release 7.1.3.3.6

• Ensure the service for the database instance is present in the Services window of the Control Panel

• Ensure SQL*Net Server release 2.x or later is installed

  Note: If you are using the assistant to migrate a 7.1.x database, you must enter the following at the SQL*DBA prompt before using the assistant to perform a migration: SQLDBA> ALTER TABLESPACE ROLLBACK_DATA ADD DATAFILE `ORACLE_HOME\RDBMS71\RBSMIGSID.ORA' SIZE 20 M;

To migrate a database using Oracle Data Migration Assistant:

1. Install Oracle Data Migration Assistant from the Oracle8 Enterprise Edition for Windows NT CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

2. Choose Start > Programs > Oracle for Windows NT - [HOME_NAME] > Oracle Data Migration Assistant.

   The Oracle Data Migration Assistant welcome window appears:

   
   
3. Respond to instructions in each Oracle Data Migration Assistant window, and click Next when you are ready to continue to the next window. When you get to the last window, click Finish to start the migration of the database. More documentation on this product is included with the Help.

Migrating Using MIG80

This section describes how to use MIG80 to migrate your Oracle7 database to an Oracle8 database.

Note: Information on how to run MIG80 (sometimes referred to as the Migration Utility) is provided in Oracle8 Migration, but the focus is on UNIX. This section provides information on using MIG80 on Windows NT.

To migrate an Oracle7 database using MIG80:

Step 1: What To Do Before Using MIG80

Step 2: Prepare for Database Backup

Step 3: Shut Down the Oracle7 Database

Step 4: Back Up the Oracle7 Database

Step 5: Install MIG80 From Oracle8 Enterprise Edition CD-ROM

Step 6: Run MIG80

Step 7: Create Oracle8 Services and Database Files

Step 8: Remove Oracle7 Software (Optional)

Step 1: What To Do Before Using MIG80

Complete the following steps before you use MIG80:

• Review Migration Concepts

• Use Appropriate SQL*DBA or Server Manager Versions

• Check Database To Be Migrated Version Number

• Check Character Set

Review Migration Concepts

• Read Chapter 1, "Migration Overview" and Chapter 2, "Preparing to Migrate" in Oracle8 Migration for background information before starting the migration process.

• Read "System Considerations and Requirements" and "Prepare the Version7 Source Database for Migration" in Chapter 3 "Migrating Using the Migration Utility" of Oracle8 Migration for information on tasks you must perform before using MIG80.

  Note: Version 8 binaries may require as much as three times the disk space required by version 7 binaries. This requirement may cause you to run out of disk space during migration. It is very important that you read "System Considerations and Requirements" to find out more about this and other requirements before you migrate.

• Read the READMEMIG.DOC located in the ORACLE_HOME\RDBMS80 directory for migration information that is new to this release. This file contains special migration, upgrade, downgrade, word-change, and rolling upgrade instructions for release 8.0.6.

Use Appropriate SQL*DBA or Server Manager Versions

When you are asked to enter commands at the SQL*DBA or Server Manager prompt, remember to use the appropriate version of the tool for the version of Oracle7 Server you are migrating:

Use...	When Migrating From...
SQLDBA71	Oracle7 release 7.1.x
SQLDBA72	Oracle7 release 7.2.x
SVRMGR23	Oracle7 release 7.3.x

Check Database To Be Migrated Version Number

Check that your database release can be directly migrated to Oracle8 Enterprise Edition. MIG80 only migrates databases that are Oracle7, release 7.1.x or later. If the database is an earlier version (for example, version 6), migrate it to at least Oracle7 release 7.1.3.3.6 before migrating it to an Oracle8 database.

Check Character Set

1. Check the character set of your Oracle7 database, and compare it with the character set in the NLS_LANG environment variable, or in the registry (if the character set does not exist as an environment variable). See "NLS_LANG Parameters and Components" for information on how to check the value of NLS-LANG.

2. Start Server Manager or SQL*DBA at the MS-DOS command prompt. If you are migrating from:

   Oracle7 Release...	Enter at the MS-DOS Command Prompt...
   7.1.x	C:\> SQLDBA71 MODE=LINE
   7.2.x	C:\> SQLDBA72 MODE=LINE
   7.3.x	C:\> SVRMGR23

3. Connect to the Oracle7 database as INTERNAL, where PASSWORD is the password of the database you want to migrate:

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x	SQLDBA> CONNECT INTERNAL/PASSWORD
   7.2.x	SQLDBA> CONNECT INTERNAL/PASSWORD
   7.3.x	SVRMGR> CONNECT INTERNAL/PASSWORD

4. Obtain the value of NLS_CHARACTERSET:

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x	SQLDBA> SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER='NLS_CHARACTERSET';
   7.2.x	SQLDBA> SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER='NLS_CHARACTERSET';
   7.3.x	SVRMGR> SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER='NLS_CHARACTERSET';

The character set value is returned by the database. If the character sets are identical, then you can proceed to run MIG80.

If the character sets are different, before you run MIG80, you must set the NLS_LANG environment variable at the MS-DOS command prompt as follows:

AMERICAN_AMERICA.database character set

where database character set is substituted with the character set of your Oracle7 database. For example, if the character set of your Oracle7 database is JA16EUC, set the NLS_LANG environment variable as follows:

C:\> SET NLS_LANG=AMERICAN_AMERICA.JA16EUC 

Messages output from MIG80 will now be in English. After MIG80 finishes, reset the NLS_LANG environment variable to its original value.

Step 2: Prepare for Database Backup

To obtain the list of database files you must back up:

1. Create a spool file called V7DBFILES.LOG:

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x	SQLDBA> SPOOL V7DBFILES.LOG
   7.2.x	SQLDBA> SPOOL V7DBFILES.LOG
   7.3.x	SVRMGR> SPOOL V7DBFILES.LOG

2. Enter the following commands at the SQL*DBA or Server Manager prompt where the WHERE clause equals control_files, DB_FILES, or LOG_FILES. Note that control_files must be lowercase. The list of database files is output to V7DBFILES.LOG.

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x	SQLDBA> SELECT MEMBER FROM V$LOGFILE; SQLDBA> SELECT NAME FROM V$DATAFILE; SQLDBA> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';
   7.2.x	SQLDBA> SELECT MEMBER FROM V$LOGFILE; SQLDBA> SELECT NAME FROM V$DATAFILE; SQLDBA> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';
   7.3.x	SVRMGR> SELECT MEMBER FROM V$LOGFILE; SVRMGR> SELECT NAME FROM V$DATAFILE; SVRMGR> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';

3. Turn off the SPOOL command:

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x	SQLDBA> SPOOL OFF
   7.2.x	SQLDBA> SPOOL OFF
   7.3.x	SVRMGR> SPOOL OFF

Step 3: Shut Down the Oracle7 Database

Shut down the database. Do not use SHUTDOWN IMMEDIATE or SHUTDOWN ABORT. If the database is not shut down before you start the migration, MIG80 stops and issues an error message. Also, if the database is not cleanly shutdown, any backup you make may be useless as it was taken while data was being written to the data files.

1. Start SQL*DBA or Server Manager:

   Oracle7 Release...	Enter at the MS-DOS Command Prompt...
   7.1.x	C:\> SQLDBA71 MODE=LINE
   7.2.x	C:\> SQLDBA72 MODE=LINE
   7.3.x	C:\> SVRMGR23

2. Connect to the Oracle7 database as INTERNAL, where PASSWORD is the password of the database you want to migrate:

   Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
   7.1.x1	SQLDBA> CONNECT INTERNAL/PASSWORD SQLDBA> ALTER USER SYS DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE SYSTEM; SQLDBA> ALTER TABLESPACE SYSTEM ADD DATAFILE `ORACLE_HOME\RDBMS71\SYS2SID.ORA' SIZE 50 M; SQLDBA> ALTER TABLESPACE ROLLBACK_DATA ADD DATAFILE `ORACLE_HOME\RDBMS71\RBSMIGSID.ORA' SIZE 20 M;
   7.2.x	SQLDBA> CONNECT INTERNAL/PASSWORD
   7.3.x	SVRMGR> CONNECT INTERNAL/PASSWORD

   1 For Oracle7 release 7.1 only, edit the INITSID.ORA file and set the REMOTE_LOGIN_PASSWORDFILE parameter to EXCLUSIVE or SHARED.

The message Connected appears if you successfully connected to the database.

• Shut down the database:

  Oracle7 Release...	Enter at the SQLDBA or SVRMGR Command Prompt...
  7.1.x	SQLDBA> SHUTDOWN
  7.2.x	SQLDBA> SHUTDOWN
  7.3.x	SVRMGR> SHUTDOWN

  Step 4: Back Up the Oracle7 Database

  1. Back up the entire Oracle home directory and all its subdirectories.

     Warning: If anything goes wrong with the Oracle7 database during migration, you will need to restore the database from the backup. Back up your database now as a precaution!

     Ensure the database was cleanly shut down before you back up. Ensure you back up the database files in the following list (and any other database files you may have created). Also, back up any scripts you may have created.

     Data files	SYS1SID.ORA, USR1SID.ORA, RBS1SID.ORA, TMP1SID.ORA
     Initialization parameter file	INITSID.ORA
     Redo log files	LOG1SID.ORA, LOG2SID.ORA, LOG3SID.ORA, LOG4SID.ORA (the last two redo log files are only available for Oracle release 7.3.4)
     Control files	CTL1SID.ORA and CTL2SID.ORA

     See Chapter 13, "Backing Up and Recovering Database Files", Oracle8 Concepts, Oracle8 Backup and Recovery, and Oracle8 Administrator's Guide for information on how to back up a database.

  Step 5: Install MIG80 From Oracle8 Enterprise Edition CD-ROM

  1. Log on to your Windows NT server as a member of the Administrators group.

  2. Stop all Oracle applications (if applicable).

  3. Stop all Oracle services (if applicable).

     To stop services:

     1. Choose Start > Settings > Control Panel.

     2. Double-click Services.

     3. If any Oracle services exist and have the status Started, select the service, and click Stop.

     4. Click Close to exit the Services window.

  4. Insert the Oracle8 Enterprise Edition for Windows NT CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

     The operating system automatically detects your Oracle8 Enterprise Edition for Windows NT CD-ROM, and the Oracle8-Autorun dialog box appears.

  5. Click Begin Installation.

     Attention: Each time you insert your CD-ROM, the process described in Step 4 occurs. To restart Oracle Installer without removing and reinserting your CD-ROM, select the drive to which the CD-ROM is mapped, and double-click SETUP.EXE.

     The Oracle Installation Settings dialog box appears.

  6. Specify a company name, Oracle home name, Oracle home location, and Oracle home language where:

     Field	Description
     Company Name	Name of the company to which this copy of Oracle software is licensed.
     Oracle Home Name	Name you want to use for this Oracle home. Ensure the same directory where the Oracle7 database to be migrated is already installed is entered in the Location field.
     Oracle Home Language	The language you want to install and run Oracle products. The default language, English, is installed in addition to any other language you select.

     The Select Installation Options dialog box appears.

  7. Select Oracle8 Enterprise Edition, then click OK.

     Note: If you select Oracle8 Enterprise Edition, you will install a complete Oracle8 software package that includes MIG80. If you just want to install MIG80, select the Custom Installation option and select Oracle8 Utilities, of which MIG80 is a component.

     The Select Oracle8 Cartridge dialog box appears.

  8. Select any cartridges you are licensed to install, then click OK.

     The Previous Version of Oracle Database dialog box appears indicating that Oracle Installer has detected an earlier version of the database. You are asked if you want to migrate your Oracle7 database to release 8.0.6 using Oracle Data Migration Assistant.

  9. Click No. If you click Yes, Oracle Data Migration Assistant is launched at the end of installation. Do not click Yes to run Oracle Data Migration Assistant while you are performing a manual migration using MIG80.

     The Select a Starter Database Configuration dialog box appears.

  10. Choose None when prompted to install a database.

  11. After installation is complete, copy the release 7.x INITSID.ORA file to the correct location:
      1. If you installed Oracle8 Enterprise Edition into the default Oracle home where Oracle7 release 7.x is already located:

         Oracle7 Release...	Copy...
         7.1.x	INITSID.ORA file from ORACLE_HOME\RDBMS71 to ORACLE_HOME\DATABASE
         7.2.x	Not required because the release 7.2.x initialization parameter file is already located in ORACLE_HOME\DATABASE
         7.3.x	Not required because the release 7.3.x initialization parameter file is already located in ORACLE_HOME\DATABASE

      2. If you installed Oracle8 Enterprise Edition into a separate Oracle home:

         Oracle7 Release...	Copy INITSID.ORA File From the Release...
         7.1.x	7.1.x ORACLE_HOME\RDBMS71 directory to the release 8.0.6 ORACLE_HOME\DATABASE directory
         7.2.x	7.2.x ORACLE_HOME\DATABASE directory to the release 8.0.6 ORACLE_HOME\DATABASE directory
         7.3.x	7.3.x ORACLE_HOME\DATABASE directory to the release 8.0.6 ORACLE_HOME\DATABASE directory

         Note: MIG80 is unable to connect to the Oracle7 database if SQL*Net version 2.x is not installed in the Oracle home directory. You will receive the error ORA-12203: TNS: Unable to connect to destination, if this is the case. If this product is not installed, install it from the Oracle8 Enterprise Edition CD-ROM.

  12. Shut down and restart the computer if you have installed Oracle8 Enterprise Edition into another Oracle home. If you have installed Oracle8 Enterprise Edition into the same Oracle home as Oracle7 release 7.x, there is no need to do this.

  Step 6: Run MIG80

  MIG80 was installed as part of Oracle8 Utilities when you installed Oracle8 Enterprise Edition in "Step 5: Install MIG80 From Oracle8 Enterprise Edition CD-ROM".

  1. Ensure that you have DBA privileges, which are necessary to run MIG80.

  2. Ensure that no other DBA (connected as INTERNAL or SYS) with the RESTRICTED SESSION privilege connects to the database while MIG80 is running. Normal users cannot connect to the database during this phase.

  3. Do not start the Oracle7 database. MIG80 starts the Oracle7 database as part of its processing.

  4. Check the Oracle7 service OracleServiceSID is started. It should already be started. If it is not started, start it at the MS-DOS command prompt:

     C:\> NET START OracleServiceSID
     

  5. Set ORACLE_SID to the SID of the database you want to migrate. For example, if the database you want to migrate is the starter database with the SID named ORCL, enter the following at the MS-DOS command prompt. Note there are no spaces around the equal sign (=) character.

     C:\> SET ORACLE_SID=ORCL
     

  6. Run MIG80. You can specify MIG80 HELP=YES at the MS-DOS command prompt for a complete list of parameters that can be included with the MIG80 command.
     1. If you installed Oracle8 Enterprise Edition into the default Oracle home where Oracle7 release 7.x is already installed:

        Oracle7 Release...	Enter at the MS-DOS Command Prompt...
        7.1.x	C:\> MIG80 PFILE=ORACLE_HOME\RDBMS71\INITSID.ORA SPOOL=C:\MIG.LOG where ORACLE_HOME is the Oracle7 release 7.1.x Oracle home directory.
        7.2.x	C:\> MIG80 SPOOL=C:\MIG.LOG
        7.3.x	C:\> MIG80 SPOOL=C:\MIG.LOG

     2. If you installed Oracle8 Enterprise Edition into another Oracle home:

        Oracle7 Release...	Enter at the MS-DOS Command Prompt...
        7.1.x	C:\> MIG80 PFILE=ORACLE_HOME\RDBMS71\INITSID.ORA where ORACLE_HOME is the Oracle7 release 7.1.x Oracle home directory.
        7.2.x	C:\> MIG80 PFILE=ORACLE_HOME\DATABASE\INITSID.ORA where ORACLE_HOME is the Oracle7 release 7.2.x Oracle home directory.
        7.3.x	C:\> MIG80 PFILE=ORACLE_HOME\DATABASE\INITSID.ORA where ORACLE_HOME is the Oracle7 release 7.3.x Oracle home directory.

     This command creates the CONVERT.ORA file that is required in a later step to create Oracle8 Enterprise Edition control files.

     The prompt Oracle7 Password appears.

  7. Enter the password for Oracle7 Password. This is the same password as the INTERNAL password for the Oracle7 database.

     MIG80 runs and displays the operations being performed. MIG80 can take considerable time to run. Please wait until it has finished running.

     Check the results after running MIG80. If there are error messages see Appendix A, "Migration Utility Messages" of Oracle8 Migration for more information before going to Step 8.

  8. Stop the Oracle7 service at the MS-DOS command prompt when MIG80 has completed successfully:

     C:\> NET STOP OracleServiceSID
     

  9. Delete the Oracle7 services at the MS-DOS command prompt:

     Oracle7 Release...	Enter at the MS-DOS Command Prompt...
     7.1.x	C:\> ORADIM71 -DELETE -SID SID
     7.2.x	C:\> ORADIM72 -DELETE -SID SID
     7.3.x	C:\> ORADIM73 -DELETE -SID SID

     MIG80 creates a convert file that contains the information of the version 7 control file. Later in the migration process, the convert file is used when you execute the ALTER DATABASE CONVERT command to create a new control file for version 8.

     The default location of the convert file is ORACLE_HOME/RDBMS80 and the default filename in this directory is CONVERT.ORA.

     Warning: Do not open the Oracle7 database, which was shut down by the version 8 MIG80 utility. To ensure data file version integrity, the SCNs in the dictionary, the convert file, and file header must all be consistent when the database is converted to version 8. If the Oracle7 database is opened after running MIG80, the SCN check will fail when the database is converted to version 8, and an ORA-01211 error will be displayed, stating "Oracle7 data file is not from migration to Oracle8." If the Oracle7 database is opened, you must rerun the Migration Utility, starting at "Step 3: Shut Down the Oracle7 Database".

     After successfully running MIG80, perform a cold backup of the Oracle7 database. This backup serves the following purposes:

     • If you want to return to the Oracle7 database after executing the ALTER DATABASE CONVERT command, you can restore the backup and start the version 7 database.

     • It can be used as the first version 8 backup for a version 8 recovery.

     • If an error occurs at version 8 database convert time (ALTER DATABASE CONVERT or ALTER DATABASE OPEN RESETLOGS), you can restore this backup, fix the problem(s), and continue the conversion process. However, if you restore a backup performed before you ran MIG80, you must rerun MIG80.

       Additional Information: See Chapter 13, "Backing Up and Recovering Database Files", Oracle8 Concepts, Oracle8 Backup and Recovery, and Oracle8 Administrator's Guide for information on how to back up a database.

  Step 7: Create Oracle8 Services and Database Files

  1. If you have not already installed the Oracle8 software, do so now. Do not install a database when prompted.

  2. Create the Oracle8 database service at the MS-DOS command prompt:

     C:\> ORADIM80 -NEW -SID SID -INTPWD PASSWORD -MAXUSERS USERS -STARTMODE AUTO 
     -PFILE ORACLE_HOME\DATABASE\INITSID.ORA 
     

     where:

     SID	is the release 8.0.6 SID.
     PASSWORD	is the password for the new release 8.0.6 database instance.
     USERS	is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.
     ORACLE_HOME	is the release 8.0.6 Oracle home directory. Ensure you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory.

  3. Either delete or rename the database's control files, or use the CONTROL_FILES parameter in the INITSID.ORA file to specify new control file names. The ALTER DATABASE CONVERT command automatically creates new control files in Step 8. If you do not use the CONTROL_FILES parameter, this command uses the control file names of your pre-migration database and returns an error if the control files already exist. Therefore, in this case, you must delete or rename the control file(s). However, if you use the CONTROL_FILES parameter in the INITSID.ORA file, the ALTER DATABASE CONVERT command creates the new control file(s) with the names you specify, and you do not need to remove the old control files. Check the file V7DBFILES.LOG that you created in "Step 4: Back Up the Oracle7 Database" for the complete list and location of control files you must delete.

  4. Before starting Server Manager:
     1. Ensure all release 7.x data files and log files are accessible and in the correct directories.

     2. Ensure all release 7.x control files are deleted or renamed.

     3. Change any parameters that point to RDBMS71, RDBMS72, or RDBMS73 to point to RDBMS80 in the release 7.x INITSID.ORA file.

     4. Certain version 7 initialization parameters are obsolete in version 8. Remove all obsolete parameters from the release 7.x INITSID.ORA file that start a version 8 instance. Obsolete parameters may cause errors if used with a version 8 database. Also, alter any parameter whose syntax has changed in version 8. See Appendix C, "Version 8 INIT.ORA Changes" of Oracle8 Migration for lists of new, changed, and obsolete parameters.

     5. Ensure the COMPATIBLE parameter is set to 8.0.0.0.0 in the release 7.x INITSID.ORA file.

        If you use the default setting (8.0.0.0.0), you cannot use new features of release 8.0.4 and later such as Propagation in Advanced Queuing (AQ) and Improved SCN Generation. To use these new features, set the COMPATIBLE parameter to the following:

        COMPATIBLE=8.0.4.0.0
        

        See Appendix C "Version 8 INIT.ORA Changes" of Oracle8 Migration for more information on COMPATIBLE parameter values.

  5. Start the Oracle8 Enterprise Edition version of Server Manager at the MS-DOS command prompt:

     C:\> SVRMGR30
     

  6. Connect to the Oracle8 instance as INTERNAL:

     SVRMGR> CONNECT INTERNAL/PASSWORD
     

  7. Start an Oracle8 instance without mounting the new Oracle8 database:

     SVRMGR> STARTUP NOMOUNT  
     

     Warning: Starting in any other mode will corrupt the database!

  8. Create new version 8 control files:

     SVRMGR> ALTER DATABASE CONVERT; 
     

     Warning: Successful execution of this command is the point of no return to Oracle7. If you need to return to the Oracle7 database, please restore it from the backup you made in "Step 4: Back Up the Oracle7 Database". If an error occurs during this step, you must correct the condition(s) that caused the error(s).

     This command uses the CONVERT.ORA file that was created earlier when you ran MIG80. All data files that are online are converted to Oracle8 Enterprise Edition format, and new control files are built. Control files are considerably larger in version 8 than in version 7. Control files in the tens of kilobytes size range in version 7 could be expanded into the range of tens of megabytes automatically during migration to version 8. This size increase could be important if a control file is on a raw device or if its available disk space is restricted.

  9. Open the Oracle8 database:

     SVRMGR> ALTER DATABASE OPEN RESETLOGS; 
     

     All rollback segments that are online when the Oracle8 database is opened are also opened and converted to the Oracle8 database format.

  10. Create a spool file called CATOUT.LOG by entering the following at the Server Manager prompt:

      SVRMGR> SPOOL CATOUT.LOG
      

  11. Run the following scripts in sequence:

      Script	Required by...	Enter at the Server Manager Prompt...
      CAT8000.SQL	All databases	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\CAT8000.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory. This script can take over thirty minutes to run depending on the size of your database. Check CATOUT.LOG to verify that the operation was successful. CAT8000.SQL creates and alters certain system tables and drops the MIGRATE user. Objects in the MIGRATE user's schema are not needed after the conversion is complete. You can also delete the binary file (ORACLE_HOME\RDBMS80\CONVERT.ORA) that is used as part of the conversion process. CAT8000.SQL also runs the CATALOG.SQL and CATPROC.SQL scripts, which create the system catalog views and all the necessary packages for using PL/SQL.
      PUPBLD.SQL	All databases	SVRMGR> @%ORACLE_HOME%\DBS\PUPBLD.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory. This script creates the USER PROFILE table.
      CATREP8M.SQL	Advanced Replication	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\CATREP8M.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory. Run this script only if you have Advanced Replication and want to use it. The CATREP8M.SQL script automatically runs the CATREP.SQL script. CATREP8M.SQL takes over an hour to run.
      CATPARR.SQL	Oracle Parallel Server	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\CATPARR.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory. Run this script only if you have Oracle Parallel Server and want to use it.
      UTLRP.SQL	All databases	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\UTLRP.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory. Oracle Corporation recommends you run this script to compile all existing PL/SQL modules that were previously in an INVALID state, such as packages, procedures, types, and so on. Doing this at this stage is optional; however, it will ensure that the cost of recompilation is incurred during installation time rather than later on.

      Oracle Corporation supplies other scripts with Oracle8 Enterprise Edition that create additional structures you can use in managing your database and creating database applications. These scripts are also located in ORACLE_HOME\RDBMS80\ADMIN. See the chapter "SQL*Scripts" in Oracle8 Reference for a complete list and descriptions of available scripts.

  12. Turn off the SPOOL command:

      SVRMGR> SPOOL OFF
      

  13. Check the spool file CATOUT.LOG and verify that the scripts you ran compiled every package and procedure successfully. Correct any problems you find in this file.

  14. Shut down the Oracle8 database in NORMAL mode to perform a clean database shutdown. Do not use SHUTDOWN IMMEDIATE or SHUTDOWN ABORT. Note that NORMAL is the default parameter.

      SVRMGR> SHUTDOWN
      

      Performing a clean database shutdown flushes all caches, clears buffers, and performs other Relational Database Management System (RDBMS) housekeeping activities. These measures are an important final step to ensure the integrity and consistency of the newly migrated release 8.0.6 database.

  15. Back up the Oracle8 database. See Chapter 13, "Backing Up and Recovering Database Files" for a list of tools to back up the database.

      The Oracle7 database has now been migrated to the Oracle8 database and is ready for use.

      Note: After a migration, all objects have the status INVALID, which is the correct status at this time. To check the status of objects, enter the following at the Server Manager prompt. SVRMGR> SELECT * FROM ALL_OBJECTS WHERE STATUS = `INVALID';

  Step 8: Remove Oracle7 Software (Optional)

  You can remove Oracle7 software if you have successfully migrated to Oracle8 Enterprise Edition and have a backup of the Oracle7 software. Oracle Installer warns you of any product dependencies that might cause problems if particular products are removed, and prompts you to confirm the deinstallation.

  To remove Oracle7 software:

  1. Stop all Oracle services. For information on how to stop Oracle services, see "Managing Oracle Services".

  2. Choose Start > Programs > Oracle for Window NT - [HOME_NAME] > Oracle Installer to start Oracle Installer.

     The Software Asset Manager window appears.

  3. Select the Oracle7 product(s) you want to remove from the Installed Products window of the Software Asset Manager window.

  4. Click Remove.

  Upgrading an Oracle8 Database Release 8.0.x to 8.0.6

  This section describes how to upgrade an Oracle8 database release 8.0.x to release 8.0.6. You can choose either of the following database tools to upgrade:

  • Oracle Data Migration Assistant

  • SQL scripts

  Oracle Corporation recommends that new users use Oracle Data Migration Assistant to upgrade databases because it is the easiest and quickest method to perform an upgrade. If you already have upgrade scripts from a previous Oracle database release, you can edit them to include the new upgrading scripts.

  Upgrading Using Oracle Data Migration Assistant

  Oracle Data Migration Assistant helps you upgrade data from an Oracle8 database release 8.0.x to release 8.0.6. During installation of Oracle8 Enterprise Edition, you are prompted to upgrade a database with this assistant if Oracle Installer detects that a release 8.0.x database exists on your system. If you do not want to upgrade during the installation process, you can just install this assistant and use it later.

  Note: Oracle Data Migration Assistant cannot be used to upgrade the following product releases: Oracle8 Enterprise Edition release 8.0.1 and 8.0.2 Beta releases. Oracle8 Enterprise Edition software developer kit (SDK) releases 8.1.1 and 8.1.2. Oracle7 releases. For example, you cannot use the assistant to upgrade from release 7.1.3.3.6 to release 7.3.3.0.0. If you need to upgrade version 7 releases, see Oracle7 Server Migration Guide and the upgrading documentation that came with your Oracle7 software. Oracle Parallel Server

  Before you use this assistant, ensure the Oracle8 database to be upgraded meets these requirements:

  • the database you want to upgrade is at least release 8.0.3.0.0

  • the service for the database instance is present in the Services window of the Control Panel

  • SQL*Net Server release 2.x or later is installed

  To upgrade a database using Oracle Data Migration Assistant:

  1. Install Oracle Data Migration Assistant from the Oracle8 Enterprise Edition for Windows NT CD-ROM. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

  2. Choose Start > Programs > Oracle for Windows NT - [HOME_NAME] > Oracle Data Migration Assistant.

     The Oracle Data Migration Assistant welcome window appears:

     
     
  3. Respond to instructions in each Oracle Data Migration Assistant window, then click Next when you are ready to continue to the next window. When you get to the last window, click Finish to start the upgrade of the database. More documentation on this product is included with the Help.

  Upgrading Using SQL Scripts

  You can run SQL scripts in Server Manager to upgrade an Oracle8 database release 8.0.x to release 8.0.6.

  Warning: If you are using mutually referencing types, downgrading back to your current release may not be supported after you upgrade to release 8.0.6. See the section "Downgrading From Release 8.0.6 to Release 8.0.x" of the READMEMIG.DOC located in the ORACLE_HOME\RDBMS80 directory for more information.

  Before Using SQL Scripts to Upgrade

  Review the following documents:

  • Read Chapter 8, "Upgrading and Downgrading" in Oracle8 Migration for background information.

  • Read the READMEMIG.DOC located in the ORACLE_HOME\RDBMS80 directory for upgrading information that is new to this release.

  Upgrading consists of the following tasks:

  Step 1: Shut Down the Release 8.0.x Database

  Step 2: Back Up the Release 8.0.x Database

  Step 3: Edit the COMPATIBLE Parameter in the 8.0.x INITSID.ORA File

  Step 4: Install Oracle8 Enterprise Edition Release 8.0.6

  Step 5: Run the SQL Scripts

  Step 1: Shut Down the Release 8.0.x Database

  1. Start Server Manager at the MS-DOS command prompt:

     C:\> SVRMGR30
     

  2. Connect to the release 8.0.x database as INTERNAL, where PASSWORD is the password of the database you want to migrate.

     SVRMGR> CONNECT INTERNAL/PASSWORD
     

     The message Connected appears if you successfully connected to the database.

  3. Shut down the database in NORMAL mode. Do not use SHUTDOWN IMMEDIATE or SHUTDOWN ABORT. If the database is not cleanly shutdown, any backup you make may be useless as it was taken while data was being written to the data files. Enter the following at the Server Manager prompt:

     SVRMGR> SHUTDOWN
     

  Step 2: Back Up the Release 8.0.x Database

  Perform a full offline backup of the database.

  1. Back up the entire Oracle home directory and all of its subdirectories.

     Warning: If anything goes wrong with the release 8.0.x database during upgrade, you will need to restore the database from the backup. Back up your database now as a precaution!

     Ensure the database is cleanly shutdown before you back up. Ensure you back up the database files in the following list (and any other database files you may have created). Also, back up any scripts you may have created.

     Data files	SYS1SID.ORA, USR1SID.ORA, RBS1SID.ORA, TMP1SID.ORA
     Initialization parameter file	INITSID.ORA
     Redo log files	LOG1SID.ORA, LOG2SID.ORA
     Control files	CTL1SID.ORA

     To obtain the list of database files you must back up:

     1. Create a spool file called V8DBFILES.LOG. Enter the following at the Server Manager prompt:

        SVRMGR> SPOOL V8DBFILES.LOG
        

     2. Enter the following commands at the Server Manager prompt, where the WHERE clause equals control_files, DB_FILES, or LOG_FILES. Note that control_files must be lowercase. The list of database files is output to V8DBFILES.LOG.

        SVRMGR> SELECT MEMBER FROM V$LOGFILE;
        
        SVRMGR> SELECT NAME FROM V$DATAFILE;
        
        SVRMGR> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';    
        

     3. Turn off the SPOOL command:

        SVRMGR> SPOOL OFF
        

     See Chapter 13, "Backing Up and Recovering Database Files", Oracle8 Concepts, Oracle8 Backup and Recovery, and Oracle8 Administrator's Guide for information on how to back up a database.

  Step 3: Edit the COMPATIBLE Parameter in the 8.0.x INITSID.ORA File

  Ensure the COMPATIBLE parameter is set to 8.0.0.0.0 or higher in the release 8.0.x INITSID.ORA file.

  If you use the default setting (8.0.0.0.0) or higher, you cannot use new features of releases 8.0.4 and later such as Propagation in Advanced Queuing (AQ) and Improved SCN Generation. To use these new features, set the COMPATIBLE parameter to the following:

  COMPATIBLE=8.0.4.0.0
  

  See Appendix C "Version 8 INIT.ORA Changes" of Oracle8 Migration for more information on COMPATIBLE parameter values.

  Step 4: Install Oracle8 Enterprise Edition Release 8.0.6

  1. Ensure all Oracle services are stopped. See "Managing Oracle Services" for information on how to stop services.

  2. Insert the Oracle8 Enterprise Edition CD-ROM into the mapped CD-ROM drive and install Oracle8 Enterprise Edition. See Oracle8 Enterprise Edition Installation for Windows NT for complete installation instructions.

     When the Oracle Installation Settings dialog box appears:

     Using...	Do the Following...
     One Oracle home directory	Accept the default Oracle Home Name, DEFAULT_HOME in the Name field. Ensure the same directory where the Oracle7 database to be upgraded is already installed is entered in the Location field.
     Two or more Oracle home directories	Enter the name you want to use for the additional Oracle home directory in the Name field. Enter another directory location where you want to put Oracle8 Enterprise Edition release 8.0.6 in the Location field.

     The Select Installation Options dialog box appears.

  3. Select Oracle8 Enterprise Edition, then click OK.

     The Select Oracle8 Cartridge dialog box appears.

  4. Select any cartridges you are licensed to install, then click OK.

     The Previous Version of Oracle Database dialog box appears indicating that Oracle Installer has detected an earlier version of the database. You are asked if you want to upgrade your Oracle8 database to release 8.0.6 using Oracle Data Migration Assistant.

  5. Click No. If you click Yes, Oracle Data Migration Assistant is launched at the end of installation. Do not click Yes to run Oracle Data Migration Assistant while you are performing a manual upgrade using SQL scripts.

     The Select a Starter Database Configuration dialog box appears.

  6. Choose None when prompted to install a database in the Starter Database Installation Options dialog box.

  7. After installation is complete, if you installed release 8.0.6 into another Oracle home, you must copy the release 8.0.x INITSID.ORA file from the release 8.0.x ORACLE_HOME\DATABASE directory to the release 8.0.6 ORACLE_HOME\DATABASE directory. If you have installed Oracle8 Enterprise Edition into the same Oracle home as Oracle7 release 7.x, there is no need to do this.

  8. Shut down and restart the computer if you have installed Oracle8 Enterprise Edition release 8.0.6 into another Oracle home. If you have installed Oracle8 Enterprise Edition into the same Oracle home as Oracle7 release 7.x, there is no need to do this.

  Step 5: Run the SQL Scripts

  1. Start the Oracle8 services of the release 8.0.x database you want to upgrade. For example, enter the following at the MS-DOS command prompt to start the services of the starter database with a SID of ORCL:

     C:\> NET START ORACLESERVICEORCL
     

  2. Set ORACLE_SID to the SID of the release 8.0.x database you want to upgrade. For example, if the database you are upgrading is the starter database with a SID of ORCL, enter the following at the MS-DOS command prompt. Note there are no spaces around the equal sign (=) character.

     C:\> SET ORACLE_SID=ORCL 
     

  3. Start Server Manager at the MS-DOS command prompt:

     C:\> SVRMGR30 
     

  4. Connect to the release 8.0.x Oracle8 instance as INTERNAL:

     SVRMGR> CONNECT INTERNAL/PASSWORD
     

  5. Run STARTUP RESTRICT:

     SVRMGR> STARTUP RESTRICT 
     

     Note: STARTUP RESTRICT only applies to a single instance, not to the database. If you are using Oracle Parallel Server, either use STARUP RESTRICT to start up one instance with PARALLEL_SERVER=FALSE, or start up all instances using STARTUP RESTRICT.

  6. Create a spool file called UPGRADE.LOG:

     SVRMGR> SPOOL UPGRADE.LOG
     

  7. Run the following scripts:

     To Upgrade...	Run Script1	Enter at the Server Manager Prompt...
     8.0.1	Not supported
     8.0.2 to 8.0.6	Not supported
     8.0.3 to 8.0.6	U0800030.SQL	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\U0800030.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory.
     8.0.4 to 8.0.6	U0800040.SQL	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\U0800040.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory.
     8.0.4S	Not supported
     8.0.5 to 8.0.6	U0800050.SQL	SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\U0800050.SQL where %ORACLE_HOME% represents your drive letter and release 8.0.6 Oracle home directory.

     1 When you run any of these U*.SQL scripts, the CATALOG.SQL and CATPROC.SQL scripts, which create the system catalog views and all the necessary packages for using PL/SQL, are also run.

     Note: You must use the version of the script supplied with the release 8.0.6 installation. You must run the script in the release 8.0.6 environment. You only need to run one script, even if your upgrade spans several releases. For example, if your current release is 8.0.3, then you only need to run U0800030.SQL.

     Oracle Corporation supplies other scripts with Oracle8 Enterprise Edition that create additional structures you can use in managing your database and creating database applications. These scripts are also located in ORACLE_HOME\RDBMS80\ADMIN. See Oracle8 Reference for a complete list and descriptions of available scripts.

  8. Run the UTLRP.SQL script. This is a script that Oracle Corporation recommends you run to compile all existing PL/SQL modules that were previously in an INVALID state, such as packages, procedures, types, and so on. Doing this at this stage is optional; however, it will ensure that the cost of recompilation is incurred during installation time rather than later on. Enter at the Server Manager prompt:

     SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\UTLRP.SQL
     

  9. Turn off the SPOOL command.

     SVRMGR> SPOOL OFF
     

     Check the spool file UPGRADE.LOG you created in Step 6. and verify that every package and procedure compiled successfully. Correct any problems you find in the file. If you are upgrading from release 8.0.2, also check the UPGRADE2.LOG spool file.

  10. Run ALTER SYSTEM DISABLE RESTRICTED SESSION:

      SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION
      

  11. Run UTLCONST.SQL to check for bad date constraints. If you already ran UTLCONST.SQL after you migrated or upgraded to a previous version 8 release, you do not need to run it again. However, running the script many times will not damage your system; therefore, if you are unsure about whether it has been run on your system, run it now.

      SVRMGR> SPOOL UTLRESULT.LOG
      SVRMGR> @%ORACLE_HOME%\RDBMS80\ADMIN\UTLCONST.SQL
      SVRMGR> SPOOL OFF
      

      A bad date constraint involves invalid date manipulation. An invalid date manipulation is one that implicitly assumes the century in the date, causing problems at the year 2000. The UTLCONST.SQL script runs through all of the check constraints in the database and sets constraints as bad if they include any invalid date manipulation. UTLCONST.SQL selects all the bad constraints at the end. After you run the script, the UTLRESULT.LOG file includes all the constraints that have invalid date constraints. UTLCONST.SQL does not correct bad date constraints, but it does disable them. Either drop the bad constraints or recreate them after you make the necessary changes.

  12. Exit Server Manager:

      SVRMGR> EXIT 
      

      Additional Information: Read the READMEMIG.DOC located in the ORACLE_HOME\RDBMS80 directory for information on upgrading the Advanced Queuing option.

  Downgrading an Oracle8 Database to Release 8.0.x or Version 7

  Read the READMEMIG.DOC file located in the ORACLE_HOME\RDBMS80 directory for information on how to downgrade.

  Migrating a Microsoft Access Database

  Oracle Migration Assistant for Microsoft Access helps you migrate data from a Microsoft Access database to an Oracle8 database. Specifically, Oracle Migration Assistant for Microsoft Access:

  • Migrates the structure and data of a Microsoft Access database(s) to an Oracle8 database. The Oracle8 database is then used to manage the migrated data and referential integrity.

  • Provides an option that enables your unmodified Microsoft Access forms and reports to work with the newly created Oracle8 database through an Oracle Open Database Connectivity Driver (ODBC) connection.

  • Enables Oracle products such as Oracle Power Objects to work with the newly migrated data.

  Oracle Migration Assistant for Microsoft Access can migrate several types of Microsoft Access databases, including:

  • Single Microsoft Access databases with both fixed and dynamically attached tables.

  • Multiple Microsoft Access databases that share attached tables with other Microsoft Access databases.

  • Microsoft Access databases that contain Object Linking and Embedding (OLE) or MEMO fields.

  Oracle Migration Assistant for Microsoft Access can be used to migrate both 16-bit Access 2.0 databases and 32-bit Microsoft Access 7.0 databases.

  To prepare a Microsoft Access database for migration:

  1. Compact and back up your Microsoft Access database files.

  2. Separate your Microsoft Access data tables and referential integrity into a different .MDB file from the application (forms, reports, macros, and modules) and create attachments. The .MDB file containing the data tables and referential integrity is the .MDB file to migrate to Oracle8 Enterprise Edition.

     Note: Microsoft Access tables with two or more MEMO or OLE datatype columns, which need to be mapped to a LONG or LONGRAW in Oracle8 Enterprise Edition, are not converted. The Oracle Migration Assistant for Microsoft Access tries to convert these datatypes to a VARCHAR2(2000) so the table can be converted. However, if the existing data does not permit this, the Microsoft Access table is not converted. Change the Microsoft Access structure to move the additional MEMO or OLE columns to a separate table. Oracle8 Enterprise Edition does not support two LONG columns in one table.

  To migrate a database using Oracle Migration Assistant for Microsoft Access:

  1. Choose Start > Programs > Oracle for Windows NT - [HOME_NAME] > Oracle Migration Assistant for Microsoft Access.

     The Oracle Migration Assistant for Microsoft Access welcome window appears:

     
     
  2. Respond to instructions in each Oracle Migration Assistant for Microsoft Access window, then click Next when you are ready to continue to the next window. When you get to the last window, click Finish to complete the migration of the database. More documentation on this product is included with the Help.

  Known Issues, Restrictions and Workarounds

  This section lists known issues and restrictions with Oracle Migration Assistant for Microsoft Access.

  • Can only be used to migrate to Oracle database releases 7.3.3, 7.3.4, 8.0.3, 8.0.4, 8.0.5 and 8.0.6.

  • Does not support Microsoft Access 97 or Access dynasets.

  • Supports only migrating schemas that have English or ISO Latin 1 object names; that is, table names, index names, column names, and so on.

  • Cannot migrate a Microsoft Access 2.0 database on Windows NT 4.0 or a database that has reference to the attached database.

  • If you do not have a default printer selected, the assistant successfully migrates your Microsoft Access database to Oracle. However it will not give you any feedback about the progress of the migration.

  • The Oracle account's password created after the migration is oracle.

  • Takes the name of the .MDB file and creates a user with the same name for Oracle. Do not use names for the .MDB files that are Oracle reserved words.

  • When using Query mapping layer and attachments, a table t1 is attached from database db1 to database db2 as attachment t2. The databases are migrated to Oracle and the query mapping layer is built. In this case, the backup attachment t2_L that is created in database db2 for the original attachment t2 does not point to the proper table in database db1.

  • When you create the backup attachment t2_L in database db2, it still points to table t1 in database db1. But since table t1 in database db1 no longer exists (a query is created with the same name for the table instead), the attachment is no longer valid. To avoid the problem, manually delete and re-create the backup attachment t2_L in database db2 pointing to table t1_L instead of table t1 in database db1.

  • When generating reports, if you select File as the destination for your report, you create a Crystal Reports viewable file format. If you want to create a text file, select Window as the destination of your report. After generating the report, select the briefcase icon at the bottom of the report window. Choose text as the format and disk file as the destination to create a text file of the report.

  • Use Windows NT or Windows 95 when migrating the AutoNumber column with the Structured Only option. The Oracle sequence number starts with the last number of the Microsoft Access auto number.