5
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 Oracle8i Enterprise Edition. In particular, it describes how to coexist different database releases using multiple Oracle homes on your computer, and how to migrate an Oracle7 database or upgrade an earlier Oracle8 database release to the current release of Oracle8i Enterprise Edition.

Specific topics discussed are:

• Intended Audience
• What To Do With Previous Oracle Database Releases
• Multiple Oracle Homes Overview
• Migrating, Upgrading, and Downgrading Overview
• Export/Import Overview
• Version 8 and Version 7 Client/Server Configurations
• Installing an Oracle 8.1 Database Where Version 7.x Already Exists
• Migrating an Oracle7 Database to Oracle8i
• Upgrading an Oracle8 Database Release 8.0.x to 8.1.5
• Migration Issues for Net 8 and SQL*Net
• Moving Database Files to an OFA-Compliant Directory

 

Intended Audience

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

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

Note: The generic Oracle8i Migration guide is the primary source of migration and upgrading information in the Oracle documentation set. You are frequently referred to the generic guide throughout this chapter, in particular to obtain information on what you must do before and after migrating or upgrading. 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.

Note: The directory path examples in this chapter follow Optimal Flexible Architecture (OFA) guidelines (for example, ORACLE_BASE\ORACLE_HOME\RDBMS\ADMIN). If you specified non-OFA compliant directories during installation, your directory paths will differ. See section "OFA and Multiple Oracle Home Configurations" for information.

What To Do With Previous Oracle Database Releases

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

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

 

 

Note: It is not possible to install release 8.1.5 products into an existing Oracle home created using the pre-8.1.5 Oracle Installer.

• Migrate release 7.x to release 8.1.5.
• Upgrade release 8.0.x to release 8.1.5.
• Use Export/Import utilities to physically copy data in the previous database release to a new release 8.1.5 database.

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

• Multiple Oracle Homes Overview
• Migrating, Upgrading, and Downgrading Overview
• Export/Import Overview

Multiple Oracle Homes Overview

An Oracle home is a directory location where you can install software. Multiple Oracle homes functionality enables you to preserve your previous release 7.x or 8.0.x databases in locations separate from where you will install release 8.1.5. Installing a new database release in a separate Oracle home allows you to test it before migrating or upgrading your production databases to the new release. There have been modifications to multiple Oracle home functionality since it was introduced in release 8.0.4. If you have multiple Oracle homes on your computer from previous releases, see "Multiple Oracle Home Functionality in Different Releases" to become familiar with the new Oracle home functionality for release 8.1.5. In particular, note:

• You cannot install release 8.1.5 into an existing Oracle home that was created using the old Oracle Installer.
• You cannot install releases of Oracle8i Enterprise Edition prior to release 8.1.4 into an Oracle home that was created by release 8.1.5.
• Releases 8.1.5 and later must be installed in separate Oracle homes. You cannot have more than one release per Oracle home.

 

 

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 an installed version of an Oracle database into a later version. For example, transforming an Oracle7 database to an Oracle8i database is migrating the database system.

Additional Information: See "Migrating an Oracle7 Database to Oracle8i".

What is Upgrading?

Upgrading is the process of transforming an installed version of an Oracle database release into another release of the same version. For example, transforming an Oracle8 database release 8.0.4 to release 8.1.5 is upgrading the database system.

Additional Information: See "Upgrading an Oracle8 Database Release 8.0.x to 8.1.5".

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.1.5 back into release 8.0.3 is downgrading, and transforming an Oracle database from version 8 back into version 7 is downgrading.

Additional Information: Chapter 10, "Downgrading to an Older Version 8 Release" for information about downgrading to release 8.0, or Chapter 11, "Downgrading to Version 7" for information about downgrading to version 7 of Oracle8i Migration.

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 tool MIG 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.

Additional Information: See "You can change the value of PATH by using one of the following methods:".

Checklist of Database Release Numbers

Check that your Oracle database release can be migrated or upgraded directly to Oracle8i 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 MIG or Oracle Data Migration Assistant to migrate it to release 8.1.5. 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 a later 7.1.x release	MIG can migrate databases that are Oracle7, release 7.1.x or later to release 8.1.5.  Oracle Data Migration Assistant migrates from release 7.1.3.3.6 or later to release 8.1.5.
Release 8.0.2.0.0 to 8.1.x	SQL scripts executed in SQL*Plus can upgrade databases release 8.0.2.0.0 to 8.0.5.x to release 8.1.5. Oracle Data Migration Assistant upgrades from release 8.0.3.0.0 or later to release 8.1.5.
Release 8.1.3 to 8.1.5	SQL scripts executed in SQL*Plus can upgrade databases release 8.1.3 to release 8.1.5.

Export/Import Overview

An alternative method of migrating or upgrading is to:

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

2. Create the Oracle8i database into which you will import the exported data.
3. Import the exported data into the new Oracle8i database using the Import Utility (IMP).

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 Oracle8i Migration for information on when to use the Export/Import utilities for migrating a database. See "Export Utility (EXP)" and "Import Utility (IMP)" for information on how to start these utilities. See "Exporting an Existing Database" and "Importing a Database" for information on using these tools on Windows NT.

Version 8 and Version 7 Client/Server Configurations

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

• Install Oracle7 and Oracle8i Databases in Multiple Oracle Homes
• Install Oracle7 and Oracle8i Databases on Separate Computers
• Migrate an Oracle7 Database to an Oracle8i Database
• Upgrade an Oracle8 Database to the Current Oracle8i Database Release
• Migrate Oracle7 Clients to Oracle8i Clients

 

 

Note: It is not possible to install release 8.1.5 products into an existing Oracle home created using the pre-8.1.4 Oracle Installer.

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

• Oracle7 Database Applications
• Different Client and Database Release Considerations
• Multi-Versioning

Oracle7 Database Applications

Can all my Oracle7 applications run on an Oracle8i database?

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

Additional Information: See Chapter 8, "Upgrading Your Applications" of Oracle8i Migration

Different Client and Database Release Considerations

Consider the following client to database connection issues before you decide if upgrading or migrating is appropriate for your environment:

• Oracle8i Client Release 8.1 to Oracle8i Database Release 8.1
• Oracle8 Client Release 8.0/Oracle7 Client to Oracle8i Database Release 8.1
• Oracle8i Client Release 8.1 to Oracle8 Release 8.0/Oracle7 Databases

Oracle8i Client Release 8.1 to Oracle8i Database Release 8.1

As the following diagram depicts, an Oracle8i Client release 8.1 requires Net8 Client release 8.1, and Oracle8i release 8.1 database requires Net8 Server release 8.1.

The Oracle8 Client release 8.1 and clients must be configured with a service name, as described in "Using the Local Naming Method" in Chapter 5, "Configuring the Network" of Net8 Administrator's Guide.

Oracle8 Client Release 8.0/Oracle7 Client to Oracle8i Database Release 8.1

As the following diagram depicts, an Oracle8 Client release 8.0 requires a compatible release of Net8 Client, an Oracle7 Client requires SQL*Net Client, and an Oracle8 database release 8.1 requires Net8 Server release 8.1 to connect successfully to an Oracle8i database release 8.1.

While it is not necessary to reconfigure release 8.0 and release 7.x clients with a service name, Oracle Corporation recommends doing so to take advantage of new functionality. For example, in the TNSNAMES.ORA file:

net_service_name = 
(DESCRIPTION= 
  (ADDRESS =...)
  (ADDRESS =...)
  )
  (CONNECT_DATA=
   (SERVICE_NAME=SALES)
  )

This effect may be accomplished by manually replacing SID=SID with SERVICE_NAME=SERVICE_NAME or using the Net8 Assistant's compatibility mode. See "Using the Release 8.0/2.x Compatibility Mode" in Chapter 3 "Upgrading and Migrating" of Net8 Administrator's Guide.

Consider the following questions for an environment with Oracle7 clients connecting to an Oracle8 release 8.1 database:

• Will my third party Oracle7 applications be able to take advantage of Net8 features?

 

No. You must rebuild or upgrade applications to work with Net8 libraries.

• Do my Oracle7 clients require Net8 Client to connect to a remote Oracle8i database?

No. If an Oracle7 client needs to connect to a remote Oracle8i database, only SQL*Net Client release 2.x has to be configured on the Oracle7 client. Net8 is backward compatible with SQL*Net release 2.x. The only limitation is that the new network features available with Net8 are unavailable with this connection type.

• Do my Oracle7 clients require Net8 Client to connect to a local Oracle8i database?

Yes. If the Oracle7 client needs to connect to a local Oracle8i database, you have SQL*Net Client release 2.x, Net8 Client, and Net8 Server in the same system. Note that Net8 Client and Net8 Server are already installed during the installation of Oracle8i Enterprise Edition or Oracle8.

If you are using Oracle7 release 7.3.4 and SQL*Net release 2.3.4, you can connect to the local Oracle 8 database without specifying a service name. Oracle 7 client automatically uses the Bequeath Protocol Adapter when connecting to an Oracle 8 database.

If you are using 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 SQL*Net Client version 2.x.

Oracle8i Client Release 8.1 to Oracle8 Release 8.0/Oracle7 Databases

An Oracle8 Client release 8.1 requires Net8 Client release 8.1, an Oracle7 Server requires SQL*Net Server, and an Oracle8 Server release 8.0 requires Net8 Server release 8.0.

The release 8.1 clients must be configured with the SID of the database. For example, the TNSNAMES.ORA would have the following effect:

net_service_name = 
(DESCRIPTION= 
  (ADDRESS =...)
  (ADDRESS =...)
  )
  (CONNECT_DATA=
   (SID=SALES)
  )

This effect may be accomplished by manually editing the TNSNAMES.ORA file or using the Net8 Assistant's compatibility mode. See "Using Release 8.0/7.x Features and Connecting To a Release 8.0/7.x Service" in Chapter 3, "Upgrading and Migrating" of Net8 Administrator's Guide.

Additionally, the LISTENER.ORA on the database server must still be configured with the description of the SID, as described in "Statically Configuring a Listener" in Chapter 5, "Configuring the Network" of Net8 Administrator's Guide.

Consider the following questions for an environment with Oracle8 clients release 8.1 connecting to an Oracle7 database.

• Do my Oracle8 clients require SQL*Net Client release 2.x to connect to a remote Oracle7 database?

No. If an Oracle8 client needs to connect to a remote Oracle7 database, only Net8 Client needs to be configured on the Oracle8 client. SQL*Net release 2.x is upwards compatible with Net8. The only limitation is that the new network features available with Net8 are unavailable with this connection type.

• Do my Oracle8 clients require SQL*Net release 2.x to connect to a local Oracle7 database?

Yes. If the Oracle8 client needs to connect to a local Oracle7 database, you need both SQL*Net Server release 2.x and Net8 Client on the same system.

Additional Information: For more detailed information on installing, migrating, and upgrading SQL*Net and Net8, see: Chapter 4, "Installing, Upgrading, and Migrating Net8" in Oracle Net8 Administrator's Guide.

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.

Install Oracle7 and Oracle8i Databases in Multiple Oracle Homes

WARNING: It is not possible to install release 8.1.5 products into an existing Oracle home. This functionality was only available for certain previous releases and has not been continued. Releases of 8.1.5 and later must be installed in separate Oracle homes. You cannot have more than one release per Oracle home. Oracle Corporation recommends you adopt an Optimal Flexible Architecture (OFA) when creating multiple Oracle homes. See "Directory Tree of a Sample OFA-Compliant Database" for more information.

You can install Oracle7 and Oracle8i databases in multiple (separate) Oracle homes and have both Oracle7 and Oracle8i clients connecting to Oracle7 and Oracle8i databases. Multiple Oracle homes functionality currently only works with releases 8.0.4 and later releases. 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. The following figure gives an example of this network configuration:

Install Oracle7 and Oracle8i Databases on Separate Computers

You can install Oracle7 and Oracle8i databases on separate computers and have both Oracle7 and Oracle8 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 Oracle homes.

Migrate an Oracle7 Database to an Oracle8i Database

You can migrate your Oracle7 database to an Oracle8i database and have both Oracle7 and Oracle8i clients connecting to the Oracle8i database. You can not migrate your Oracle7 database to an Oracle8i database in the same Oracle home. See "Migrating an Oracle7 Database to Oracle8i" for instructions. The following figure illustrates this network configuration:

Upgrade an Oracle8 Database to the Current Oracle8i Database Release

You can upgrade your Oracle8 database, for example, release 8.0.4, to release 8.1.5 and have both Oracle7 and Oracle8 clients connecting to the release 8.1.5 Oracle8i 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.1.5" for instructions. The following figure illustrates this network configuration:

Migrate Oracle7 Clients to Oracle8i Clients

You can migrate some or all of your Oracle7 clients to Oracle8i Enterprise Edition release 8.1.5. You can also migrate your Oracle7 database to an Oracle8i database or upgrade your Oracle8 release to the current Oracle8i database at a later date.

Additional Information: For detailed information on migrating SQL*Net and upgrading Net8, see: Chapter 3, "Upgrading and Migrating" of Net8 Administrator's Guide. Chapter 4, "Installing, Upgrading, and Migrating Net8" in Oracle Net8 Administrator's Guide.

The following figure illustrates this network configuration.

Installing an Oracle 8.1 Database Where Version 7.x Already Exists

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.1.5 starter database in a separate Oracle home directory called TEST81 in the C:\ORACLE\ORA81 directory. In this example, ORCL is the first and only database on the computer. The second database you install will be called ORCL0 by default.

Additional Information: See "Starter and Custom Database Overview" for more information on conventions used for database naming.

To install an Oracle8i 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 Oracle8i Enterprise Edition and Oracle7 Server to determine the total system requirements. See Oracle8i 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 Oracle8i Enterprise Edition for Windows NT from the CD-ROM. See Oracle8i Enterprise Edition Installation for Windows NT for complete installation instructions.

 

The Oracle8i Enterprise Edition Autorun dialog box appears and prompts you to make a selection:

• Add/Remove Products
• Explore CD
• Browse Information

4. Click Add/Remove Products.

The Oracle Universal Installer Welcome dialog box appears.

5. Click Next. The Oracle License Terms dialog box appears.
6. Click "I accept the License Terms and Export Restrictions." If you do not accept the terms, you cannot proceed with the installation.

The File Locations dialog box appears. Do not change the text in the Source... field. This is the location of files for installation.

1. Enter the name of a new Oracle home in the Destination Name:field. In this example, enter TEST81.

 

1. Enter the location of the Oracle home directory where you want to install release 8.1.5. In this example, enter C:\ORACLE\ORA81 in the Path: field. You must install the release 8.1 software into a directory that is separate from your release 8.0 Oracle home. Installing the release 8.1 software into the same Oracle home as the release 8.0 software is not supported in release 8.1.
2. Click Next.

 

The Available Products dialog box appears.

7. Select Oracle8i Enterprise Edition, then click Next.

The Installation Types dialog box appears.

8. Select Minimal to install a standard set of components for an Oracle database server, then click Next.

The Available Product Components dialog box appears.

9. Select the Oracle products you want to install.
10. Click Next.

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

11. Click None. Then click Next to continue installation of the 8.1.5 database.

If you click ORCL or any other database that resides on your computer, Oracle Data Migration Assistant is launched at the end of installation and migrates the Oracle7 database to release 8.1.5.

The Starter Database dialog box appears and prompts you to create a starter database.

12. Choose No, then click Next.

 

The Summary window appears.

13. Click Install.

The Configuration Tools window appears.

14. Click Next.

The End of Installation window appears.

15. Click Exit to quit Oracle Universal Installer.

 

You now have an Oracle7 database located in C:\ORANT\DATABASE and an Oracle8 database located in C:\ORACLE\ORADATA\ORCL0.

Note that if you decided to invoke Oracle Data Migration Assistant at Step 11. and migrated the Oracle7 database to release 8.1.5, you only have one Oracle8 database on your computer.

After installation is complete, modify the release 8.1.5 LISTENER.ORA file to resolve possible conflicts in listening addresses, and then restart the listener. This is required to enable the release 8.1.5 database to accept connections from clients. See Migration Issues for Net8 and SQL*Net and Net8 Administrator's Guide for information on how to modify the LISTENER.ORA file.

Migrating an Oracle7 Database to Oracle8i

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

• Oracle Data Migration Assistant
• MIG

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

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

Ten Issues That Can Affect Oracle7 to Oracle8i Migration

The following table lists and describes the ten issues you should be aware of that can affect Oracle7 to Oracle8i 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 Oracle8i 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 Oracle8i 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 Oracle8i 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 Oracle8i 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 Oracle8i. See "Supported Operating Systems" for the list of supported Windows operating systems and versions. See "List of Oracle8i Enterprise Edition Products" 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 Oracle8i and do not require any conversion. But to prevent Oracle8i 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 Oracle8i Migration.

Installing Appropriate Versions of SQL*Net

When migrating from Oracle7 Server release 7.3.x to Oracle8i release 8.1.5, install the appropriate version of SQL*Net in the 7.3.x Oracle home before using Oracle Data Migration Assistant or MIG. Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net.

Migrating from...	Install...
Oracle7 release 7.3.2.x to Oracle8i	SQL*Net release 2.3.2.1.4 and SQL*Net release 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 release 2.3.2.1.12. SQL*Net release 2.3.2.1.4 is not available on the release 8.1.5 CD-ROM. It is only available on the release 7.3.2.2.0 CD-ROM.
Oracle7 release 7.3.3.x to Oracle8i	SQL*Net release 2.3.3.0.3
	To install SQL*Net release 2.3.2.1.12 or 2.3.3.0.3: Start Oracle Installer from the CD-ROM. See Oracle8i 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 release 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 release 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 release 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 Oracle8i database. During installation of Oracle8i Enterprise Edition, you are prompted to migrate a database with this assistant if Oracle Universal 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 Chapter 4, "Migration Using the Oracle Data Migration Assistant" in Oracle8i Migration for background information before starting the migration process.

 

 

IMPORTANT: 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.

• Ensure the Oracle7 database to be migrated is at least release 7.1.3.3.6.
• Ensure the service for the Oracle7 database instance is present in the Services window of the Control Panel.
• Ensure SQL*Net Server release 2.x or later is installed.

 

To migrate a database using Oracle Data Migration Assistant:

1. Choose Start > Programs > Oracle - HOME_NAME > Migration Utilities > Oracle Data Migration Assistant.

 

The Oracle Data Migration Assistant welcome window appears:

2. 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 Next to start the migration of the database. More documentation on this product can be accessed by clicking Help.

 

Migrating Using MIG

This section describes how to use MIG to migrate your Oracle7 database to an Oracle8i database.

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

To migrate an Oracle7 database using MIG:

Step 1: What To Do Before Using MIG

Step 2: Shut Down the Oracle7 Database

Step 3: Back Up the Oracle7 Database

Step 4: Install MIG From Oracle8i Enterprise Edition CD-ROM

Step 5: Run MIG

Step 6: Create Oracle8i Services and Database Files

Step 7: Remove Oracle7 Software (Optional)

Step 1: What To Do Before Using MIG

Complete the following steps before you use MIG:

• Review Migration Concepts
• Use Appropriate SQL*DBA or SQL*Plus Versions
• Check Database To Be Migrated Version Number
• Check Character Set

 

Review Migration Concepts

• Read Chapter 1, "Overview" and Chapter 2, "Preparing to Migrate" in Oracle8i 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 Oracle8i Migration for information on tasks you must perform before using MIG.

 

 

IMPORTANT: 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.

Use Appropriate SQL*DBA or SQL*Plus Versions

When you are asked to enter commands at the SQL*DBA or SQL*Plus 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 Oracle8i Enterprise Edition. MIG 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 Oracle8i 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).

2. Start SQL*Plus 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 SQLPLUS Command Prompt...
7.1.x	SQLDBA> CONNECT INTERNAL/PASSWORD
7.2.x	SQLDBA> CONNECT INTERNAL/PASSWORD
7.3.x	SQL> CONNECT INTERNAL/PASSWORD

4. Obtain the value of NLS_CHARACTERSET:

 

 




Oracle7 Release...	Enter at the SQLDBA or SQLPLUS 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	SQL> 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 MIG.

If the character sets are different, before you run MIG, 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 MIG will now be in English. After MIG finishes, reset the NLS_LANG environment variable to its original value.

Step 2: 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, MIG 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 SQL*Plus:

 

 




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:\> SQLPLUS

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 SQLPLUS 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	SQL> 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.

3. Shut down the database:

 

 




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

Step 3: 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

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 SQLPLUS Command Prompt...
7.1.x	SQLDBA> SPOOL V7DBFILES.LOG
7.2.x	SQLDBA> SPOOL V7DBFILES.LOG
7.3.x	SQL> SPOOL V7DBFILES.LOG

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

 

 




Oracle7 Release...	Enter at the SQLDBA or SQLPLUS 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	SQL> SELECT MEMBER FROM V$LOGFILE; SQL> SELECT NAME FROM V$DATAFILE; SQL> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';

2. Turn off the SPOOL command:



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

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

Step 4: Install MIG From Oracle8i Enterprise Edition CD-ROM

You can install MIG in either of two ways depending if you want to install the release 8.1.5 software that includes MIG or just MIG.

Note: The following installation steps are a shorter version of the complete installation instructions you can find in Oracle8i Enterprise Edition Installation for Windows NT.

To install the Oracle8i Enterprise Edition including MIG:

1. Run Oracle Universal Installer.

The File Locations dialog box appears.

1. Enter the name of a new Oracle home in the Oracle Home Name: field. For example, enter MIGTO81.

 

1. Enter the location of the Oracle home directory where you want to install the Oracle8i Enterprise Edition product. In this example, enter C:\ORACLE\ORA81 in the Location: field.
2. Click Next.

 

The Available Products dialog box appears.

2. Select Oracle8i Enterprise Edition, then click Next.

The Installation Types dialog box appears.

3. Select the Minimal installation type to avoid the creation of a new database.
4. The Select Starter Database dialog box appears.
5. Click No.

The Summary window appears.

6. Click Install.

The Configuration Tools window appears.

7. Click Next.

The End of Installation window appears.

Click Exit.

MIG has been installed as part of Oracle Utilities.

If you just want to install MIG, perform the following steps:

1. Run Oracle Universal Installer.

The File Locations dialog box appears.

1. Enter the name of a new Oracle home in the Oracle Home Mansfield. For example, enter MIGTO81.

 

1. Enter the location of the Oracle home directory where you want to install MIG. In this example, enter C:\ORACLE\ORA81 in the Location: field.
2. Click Next.

 

The Available Products dialog box appears.

2. Select Oracle8i Enterprise Edition, then click Next.

The Installation Types dialog box appears.

3. Select Custom.

The Available Product Components dialog box appears.

Click Oracle Utilities, of which MIG is a component.

4. Click Next.

The Summary window appears.

5. Click Install.

The Configuration Tools window appears.

6. Click Next.

The End of Installation window appears.

7. Click Exit to quit Oracle Universal Installer.

MIG is located in C:\ORACLE\ORA81\BIN.

Step 5: Run MIG

There are some tasks that you may have to perform before you run MIG.

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

2. Ensure that SQL*Net version 2.x is installed in the Oracle home directory of the database you are migrating. If it is not installed, MIG will be unable to connect to the Oracle7 database. 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 Oracle8i Enterprise Edition CD-ROM. See "Installing Appropriate Versions of SQL*Net" for more information.
3. Ensure that no other DBA (connected as INTERNAL or SYS) with the RESTRICTED SESSION privilege connects to the database while MIG is running. Normal users cannot connect to the database during this phase.
4. Do not start the Oracle7 database. MIG starts the Oracle7 database as part of its processing.
5. Start the Oracle7 service OracleServiceSID at the MS-DOS command prompt:

C:\> NET START OracleServiceSID

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

7. Run MIG. You can enter MIG HELP=YES at the MS-DOS command prompt for a complete list of parameters that can be included with the MIG command. You must include the PFILE parameter to specify the exact location of the version 7 INITSID.ORA file because MIG is in a different directory from the version 7 initialization parameter file. Ensure you specify the complete pathname of ORACLE_HOME including drive letter.

C:\> MIG PFILE=ORACLE_HOME\DATABASE\INITSID.ORA SPOOL=C:\MIG.LOG

The MIG command creates the MIGSID.ORA file that is required in a later step to create Oracle8i Enterprise Edition control files.

8. If the prompt for Oracle7 Password: appears, enter the same password as the INTERNAL password for the Oracle7 database. This prompt displays because the DBA_AUTHORIZATION registry parameter is set properly or not set at all for Oracle7.

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

Check the results after running MIG. If there are error messages, see Appendix A, "Troubleshooting Migration Problems" of Oracle8i Migration for more information before going to Step 9.

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

C:\> NET STOP OracleServiceSID

10. Delete the Oracle7 services at the MS-DOS command prompt using ORADIM7x.

 

 




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

Note: You can receive the error "failed to open service", when attempting to delete services. To avoid this error, reboot your Windows NT computer.

MIG 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_BASE\ORACLE_HOME\RDBMS where ORACLE_HOME is the version 8 Oracle home. The default filename is CONVERT.ORA.

WARNING: Do not open the Oracle7 database, which was shut down by the version 8 MIG 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 MIG, 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 Oracle8i." If the Oracle7 database is opened, you must rerun the Migration Utility, starting at "Step 2: Shut Down the Oracle7 Database".

After successfully running MIG, 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 MIG, you must rerun MIG.

 

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

Step 6: Create Oracle8i Services and Database Files

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

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

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

where:

SID	is the same SID name as the SID of the version 7 database you migrated.
PASSWORD	is the password for the new release 8.1.5 database instance. The -INTPWD option is not required. If you do not specify it, operating system authentication is used, and no password is required. See "Automatically Enabling Operating System Authentication During Installation" for a description of features.
USERS	is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.
ORACLE_HOME	is the release 8.1.5 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 3: Back Up the Oracle7 Database" for the complete list and location of control files you must delete.
4. Before starting SQL*Plus:
1. Ensure all release 7.x data files and log files are accessible and in the correct directories.

 
1. Ensure all release 7.x control files are deleted or renamed.
2. Change any parameters that point to RDBMS71, RDBMS72, or RDBMS73 to point to RDBMS in the release 7.x INITSID.ORA file.
3. 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 Oracle8i Migration for lists of new, changed, and obsolete parameters.
4. Ensure the COMPATIBLE parameter is set to 8.0.5.0.0 in the release 7.x INITSID.ORA file. Set the COMPATIBLE parameter to the following:

COMPATIBLE=8.0.5.0.0

Additional Information: Some new features of Oracle8i release 8.1.x require a compatibility setting of 8.1.0 or higher. See Chapter 8, "Compatibility and Interoperability" of Oracle8i Migration for more information.

5. Start the Oracle8i Enterprise Edition version of SQL*Plus at the MS-DOS command prompt:

C:\> SQLPLUS

6. Connect to the Oracle8i instance as INTERNAL:

SQL> CONNECT INTERNAL/PASSWORD

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

SQL> STARTUP NOMOUNT PFILE=ORACLE_HOME\DATABASE\INITSID.ORA

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

8. Create new version 8 control files:

SQL> 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 3: 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 MIGSID.ORA file that was created earlier when you ran MIG. All data files that are online are converted to Oracle8i 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 Oracle8i database:

SQL> ALTER DATABASE OPEN RESETLOGS;

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

10. Create a spool file called CATOUT.LOG by entering the following at the SQL*Plus prompt:

SQL> SPOOL CATOUT.LOG

11. Run the following scripts in sequence:

 

 




Script	Required by...	Enter at the SQL*Plus Prompt...
U0703040.SQL	All databases	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0703040.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 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. U0703040.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\RDBMS\CONVERT.ORA) that is used as part of the conversion process.  U0703040.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.  Note: If the U0703040.SQL script runs for an inordinately long time, it may be caused by a setting for LARGE_POOL_SIZE that is too large for your installation. Use the V$PARAMETER view to check the setting for LARGE_POOL_SIZE, and if it is too large, set it to a smaller value in your INITSID.ORA file.
CATREP.SQL	Advanced Replication	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\CATREP.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.  Run this script only if you have Advanced Replication and want to use it. CATREP.SQL takes over an hour to run.
R0703040.SQL	Advanced Replication	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\R0703040.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.  The R0703040.SQL script performs a post-CATREP.SQL Advanced Replication related upgrade.
CATPARR.SQL	Oracle Parallel Server	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\CATPARR.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory. Run this script only if you have Oracle Parallel Server and want to use it.
UTLRP.SQL	All databases	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLRP.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 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 Oracle8i 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\RDBMS\ADMIN. See the chapter "SQL*Scripts" in Oracle8i Reference for a complete list and descriptions of available scripts.

12. Turn off the SPOOL command:

SQL> 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 Oracle8i 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.

SQL> 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.1.5 database.

15. Back up the Oracle8i database. See Appendix 12, "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 Oracle8i database and is ready for use.

Note: After a migration, all objects have the status INVALID, unless you have run the UTLRP.SQL script. To check the status of objects, enter the following at the SQL*Plus prompt. SQL> SELECT * FROM ALL_OBJECTS WHERE STATUS = `INVALID';

16. Complete the procedures described in Chapter 5, "After Migrating the Database" of Oracle8i Migration.

 

 

WARNING: If you retain the old version 7 software, never start the migrated database with the old version 7 software. Only start the database with the executables in the new version 8 installation directory.

Step 7: Remove Oracle7 Software (Optional)

You can remove Oracle7 software if you have successfully migrated to Oracle8i 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 Windows NT >ORACLE_HOME > 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.1.5

This section describes how to upgrade an Oracle8 database release 8.0.x to release 8.1.5. 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.1.5. During installation of Oracle8i Enterprise Edition, you are prompted to upgrade a database with this assistant if Oracle Universal 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 releases: Oracle8 Enterprise Edition release 8.0.1 and 8.0.2 Beta releases. MIG can upgrade 8.0.2 releases. Upgrading release 8.0.1 is not supported by either tool. 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. Migration in an OPS environment is not supported.

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

 

To upgrade a database using Oracle Data Migration Assistant:

1. Choose Start > Programs > Oracle - HOME_NAME > Migration Utilities > Oracle Data Migration Assistant.

 

The Oracle Data Migration Assistant welcome window appears:

2. 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 Next to start the upgrade of the database. More documentation on this product can be accessed by clicking Help.

 

Upgrading Using SQL Scripts

You can run SQL scripts in SQL*Plus to upgrade an Oracle8i database release 8.0.x to release 8.1.5.

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

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 Oracle8i Enterprise Edition Release 8.1.5

Step 5: Run the SQL Scripts

Step 1: Shut Down the Release 8.0.x Database

1. Start SQL*Plus at the MS-DOS command prompt:

C:\> SQLPLUS

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

SQL> 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. Note that NORMAL is the default mode. Enter the following at the SQL*Plus prompt:

SQL> 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 SQL*Plus prompt:

SQL> SPOOL V8DBFILES.LOG

1. Enter the following commands at the SQL*Plus 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.

SQL> SELECT MEMBER FROM V$LOGFILE;

SQL> SELECT NAME FROM V$DATAFILE;

SQL> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';

2. Turn off the SPOOL command:

SQL> SPOOL OFF

See Chapter 13, "Developing Applications", Oracle8i Concepts, Oracle8i Backup and Recovery Guide, and Oracle8i 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 left unset if it has not been set in the INITSID.ORA file. Leave the COMPATIBLE parameter unchanged if it has been previously set.

Additional Information: Some new features of Oracle8i release 8.1.x require a compatibility setting of 8.1.0. See Chapter 7 "Compatibility and Interoperability" of Oracle8i Migration for more information.

Step 4: Install Oracle8i Enterprise Edition Release 8.1.5

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

 

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

 

The Oracle8i Enterprise Edition Autorun dialog box appears and prompts you to make a selection:

• Add/Remove Products
• Explore CD
• Browse Information

 

3. Click Add/Remove Products.

 

The Oracle Universal Installer Welcome dialog box appears.

4. Click Next. The Oracle License Terms dialog box appears.
5. Click "I accept the License Terms and Export Restrictions." If you do not accept the terms, you cannot proceed with the installation.

The File Locations dialog box appears. Do not change the text in the Source... field. This is the location of files for installation.

1. Enter the name of a new Oracle home in the Destination Name: field. In this example, enter TEST81.

 

1. Enter the location of the Oracle home directory where you want to install release 8.1.5. In this example, enter C:\ORACLE\ORA81 in the Path: field. You must install the release 8.1 software into a directory that is separate from your release 8.0 Oracle home. Installing the release 8.1 software into the same Oracle home as the release 8.0 software is not supported in release 8.1.
2. Click Next.

 

The Available Products dialog box appears.

6. Select Oracle8i Enterprise Edition, then click Next.

 

The Installation Types dialog box appears.

7. Select the Minimal installation type to avoid the creation of a new database.
8. The Select Starter Database dialog box appears.
9. Click No.

The Summary window appears.

10. Click Install.

The Configuration Tools window appears.

11. Click Next.

The End of Installation window appears.

12. After installation is complete, copy the release 8.0.x INITSID.ORA file from the release 8.0.x ORACLE_HOME\DATABASE directory to the release 8.1.5 ORACLE_BASE\ORACLE_HOME\DATABASE directory.
13. Shut down and restart the computer.
14. Certain release 8.0 initialization parameters are obsolete in release 8.1. Remove all obsolete parameters from any initialization parameter file that will start a release 8.1 instance; obsolete parameters may cause errors in release 8.1. Also, alter any parameter whose syntax has changed in release 8.1. See Appendix B, "Changes to Initialization Parameters" of Oracle8i Migration for lists of new, renamed, and obsolete parameters.
15. If you are updating snapshots automatically by using the JOB_QUEUE_PROCESSES initialization parameter, comment out this parameter in the INITSID.ORA file. After upgrading your database, you can remove the comments to use the parameter normally.

 

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 SQL*Plus at the MS-DOS command prompt:

C:\> SQLPLUS

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

SQL> CONNECT INTERNAL/PASSWORD

5. Run STARTUP RESTRICT:

SQL> 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:

SQL> SPOOL UPGRADE.LOG

7. Run the following scripts:

 

 




To Upgrade...	Run Script1	Enter at the SQL*Plus Prompt...
8.0.1.0	Not supported
8.0.2.0	Not supported
8.0.3.0 to 8.1.5	U0800030.SQL	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0800030.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.
8.0.4.0 or 8.0.4.1 to 8.1.5	U0800040.SQL	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0800040.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.
8.0.5	U0800050.SQL	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0800050.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.
8.1.3	U0801030.SQL	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0801030.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 Oracle home directory.
8.1.4	U0801040.SQL	SQL> @%ORACLE_HOME%\RDBMS\ADMIN\U0801040.SQL where %ORACLE_HOME% represents your drive letter and release 8.1.5 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.1.5 installation. You must run the script in the release 8.1.5 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.0.0, then you only need to run U0800030.SQL. If the old release you had installed prior to upgrading was higher than release 8.0.5.0, see the READMEMIG.doc file in the new installation for the correct upgrade script to run. If the upgrade script runs for an inordinately long time, it may be caused by a setting for LARGE_POOL_SIZE that is too large for your installation. Use the V$PARAMETER view to check the setting for LARGE_POOL_SIZE, and if it is too large, set it to a smaller value in your INIT.ORA file.

8. If you have Advanced Replication installed, run the CATREP.SQL script. If you have Oracle Parallel Server installed, run the CATPARR.SQL script. Otherwise, go to Step 9.

 

Oracle Corporation supplies other scripts with Oracle8i 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\RDBMS\ADMIN. See Oracle8i Reference for a complete list and descriptions of available scripts.

9. 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 SQL*Plus prompt:

SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLRP.SQL

10. Turn off the SPOOL command.

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

11. Run ALTER SYSTEM DISABLE RESTRICTED SESSION:

SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION

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

SQL> SPOOL UTLRESULT.LOG
SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLCONST.SQL
SQL> 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.

13. Exit SQL*Plus:

SQL> EXIT

14. Ensure the COMPATIBLE parameter is left unset if it has not been set in the INITSID.ORA file. Leave the COMPATIBLE parameter unchanged if it has been previously set.

 

 

Additional Information: Some new features of Oracle8 release 8.1.x require a compatibility setting of 8.1.0. See Chapter 7 "Compatibility and Interoperability" of Oracle8i Migration for more information.

Your database is upgraded to release 8.1.5.

Migration Issues for Net8 and SQL*Net

During migration from Oracle 7.x or Oracle 8.0.x to Oracle 8i, the following issues need to be addressed:

• Location of Network Configuration Files
• Listener Configuration in Multiple Oracle Home Installations
• Changing Listener.ora for Migrated Databases
• Changes in Handling of TCP/IP Listening Address
• Enabling NT Native Authentication
• NT Authenticated Users in the Database
• Connection using Multi-threaded Server Mode
• Installing Appropriate Versions of SQL*Net
• Installation of Oracle Names

 

Location of Network Configuration Files

SQL*Net and Net8 8.1 use configuration files from ORACLE_HOME\network\admin by default, while Net8 8.0 uses configuration files from ORACLE_HOME\net80\admin by default. If you want all the Oracle products to use configuration files from the same location, you can set the registry variable TNS_ADMIN.

Additional Information:  Please refer to Appendix D. Net8 Configuration Parameters, Services and Port Numbers for more information.

Listener Configuration in Multiple Oracle Home Installations

Before installing an Oracle8i server ensure that any existing Net8 or SQL*Net listeners on the same computer are stopped. An existing listener may prevent the Net8 8.1 listener from starting during the Oracle8i install due to listener endpoint conflicts with an existing listener.

Once Oracle8i is installed, Oracle recommends that you use the new Net8 8.1 listener for all of your Oracle databases of Oracle8i release 8.1 and previous releases (such as an Oracle8 8.0 database). Even if you install Oracle 8i on multiple Oracle Homes on the same computer, you should only use one listener for all your databases on the same computer.

If you want to continue to use multiple listeners (such as a Net8 8.0 listener and Net8 8.1 listener) on the same computer, verify that there are no listener endpoint conflicts between the two listeners before starting both listeners. For information on listener endpoint configuration please refer to the Net8 Administrators guide included in the online Oracle8i documentation.

Additionally, on Windows NT platforms, the new Net8 8.1 listener will be set to start automatically at system reboot. If you intend to use only the Net8 8.1 listener for all of your databases you should ensure that only the Windows NT service for the Net8 8.1 listener, as listed in the Windows NT services control panel, is set to start automatically.

If you want to use multiple listeners on the same computer, you need to reconfigure one of the listeners to make sure that you use different listening endpoints for all protocols. To resolve conflicts, you may need to make the following changes in listener configuration:

• PORT number for TCP/IP,
• SERVICE name for SPX,
• PIPE name for Named Pipes, and
• KEY for IPC.

If you need to change the IPC key used by External Procedure, you also need to change the KEY for the alias EXPROC_CONNECTION_DATA in tnsnames.ora to match the KEY value in listener.ora.

If Net8 8.1 listener service is not created during Oracle 8i installation due to conflicts in listening endpoints, you can start your Net8 8.1 listener by using the listener control program:

From a command prompt:

lsnrctl start <listener_name>

where <listener_name> is LISTENER for typical install or the name given during custom install.

This command also creates the NT service for the listener if the service does not already exist.

Changing Listener.ora for Migrated Databases

When you migrate Oracle 7 or Oracle 8.0 database to an Oracle8i database, the SID of the database needs to be removed from the Oracle 7/8.0 homeís listener.ora and added to Oracle 8i homeís listener.ora file.

Changes in Handling of TCP/IP Listening Address

In Oracle 8i, when the LISTENER.ORA or CMAN.ORA contains the TCP/IP system name in ADDRESS, the Listener or Connection Manager listens on all addresses for the system. Therefore, even if a system has multiple interface cards with different TCP/IP host names, listening using any of the host names ensures that the Listener or Connection Manager will listen on all interface cards. It is an error to configure multiple addresses for the same port in LISTENER.ORA.

For Oracle 7 or Oracle 8.0, the Listener or Connection Manager only listened for the TCP/IP host name specified in LISTENER.ORA or CMAN.ORA and you had to specify listening addresses for multiple TCP/IP host names of a system. The default LISTENER.ORA created for Oracle 7/Oracle 8.0 contained multiple addresses, e.g.

LISTENER = (ADDRESS_LIST=
        (ADDRESS=(PROTOCOL=TCP)(HOST=system1)(PORT=1521))
        (ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521))
)

The above addresses are invalid for Oracle 8i and the ADDRESS line containing 127.0.0.1 must be removed.

Enabling NT Native Authentication

For Oracle 7 and Oracle 8.0 default installation, NT native authentication is turned off. In order to allow Oracle client to use NT native authentication, the parameter sqlnet.authentication_services must be set to NTS in sqlnet.ora for Oracle client and Oracle server, i.e.

sqlnet.authentication_services = (NTS)

This can be done using Net8 Assistant or through manual editing.

NT Authenticated Users in the Database

For Oracle 8i, Database Configuration Assistant sets the parameter OS_AUTHENT_PREFIX="" in init.ora during database creation. Therefore, Oracle users in the database should be created without the prefix OPS$ for Oracle 8i. The prefix OPS$ is needed for Oracle 7 or Oracle 8.0 default installation, where OS_AUTHENT_PREFIX parameter is not set in init.ora by default.

In Oracle 7.3.3, Oracle 7.3.4 and Oracle 8.0.x, the external users created in the database were not prefixed with the domain name. For example, the Oracle user in the database was NTUSER1 for an NT user DOMAIN1\NTUSER1 (assuming that init.ora parameter OS_AUTHENT_PREFIX=""). If you wished to create the Oracle user prefixed with domain name, you needed to set the registry value OSAUTH_PREFIX_DOMAIN in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME_ID to TRUE.

For better security in a domain environment, we have changed the default for Oracle 8i so that external users created in the database are prefixed with domain name. For example, for an NT user DOMAIN1\NTUSER1, the Oracle user created in the database should be DOMAIN1\NTUSER1. But you can set the registry value OSAUTH_PREFIX_DOMAIN in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME_ID to FALSE if you do not want to prefix the domain name. Please note that it is less secure if you do not prefix the domain name. Therefore, if you migrate a database with external users to Oracle 8i, you have two options:

• Set the registry value OSAUTH_PREFIX_DOMAIN in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME_ID to FALSE, or
• Delete the existing external users and create the new OS authenticated users in the database using Oracle Administration Assistant for Windows NT.

 

Connection using Multi-threaded Server Mode

For Oracle 8i, if the database is configured for multi-threaded server mode, it is recommended that you specify the service name of the database in the Net Service Name to ensure that the connection is in multi-threaded server mode. If the Net Service Name contains the SID of the database, the client will connect to the database in dedicated server mode if listener.ora contains the statically configured SID of the database but not the GLOBAL_DBNAME of the database.

This behavior is different from Oracle 8.0. In Oracle 8.0, if the database is configured for multi-threaded server mode, the clients connected to the database in multi-threaded server mode even if the Net Service Name contained the SID of the database.

If Net Service Names of your clients contain the SID of the database and you want them to connect to the Oracle 8i database in multi-threaded server mode, you should configure the GLOBAL_DBNAME of the database in listener.ora. For example, for a database with SID as orcl, DB_NAME as orcl and DB_DOMAIN as us.oracle.com, the listener entry for Oracle 8i should be:

SID_LIST_LISTENER =  (SID_LIST = 
       (SID_DESC=(SID_NAME=orcl)(GLOBAL_DBNAME=orcl.us.oracle.com))
)

Installing Appropriate Versions of SQL*Net

When migrating from Oracle7 Server release 7.3.x to Oracle8i release 8.1.5, install the appropriate version of SQL*Net in the 7.3.x Oracle home before using Oracle Data Migration Assistant or MIG. Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net.

Migrating from...	Install...
Oracle7 release 7.3.2.x to Oracle8i	SQL*Net release 2.3.2.1.4 and SQL*Net release 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 release 2.3.2.1.12. SQL*Net release 2.3.2.1.4 is not available on the release 8.1.5 CD-ROM. It is only available on the release 7.3.2.2.0 CD-ROM.
Oracle7 release 7.3.3.x to Oracle8i	SQL*Net release 2.3.3.0.3
	To install SQL*Net release 2.3.2.1.12 or 2.3.3.0.3: Start Oracle Installer from the CD-ROM. See Oracle8i 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 release 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 release 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 release 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.

Installation of Oracle Names

During installation of Oracle Names in Oracle 8i, the NT service for the default Names Server is not created. You need to invoke Net8 Assistant to create the Names Server.

Moving Database Files to an OFA-Compliant Directory

The Oracle Optimal Flexible Architecture (OFA) is a feature of Oracle8i Enterprise Edition for Windows NT release 8.1.5. It has been available for Oracle on UNIX for some years. OFA is a set of file naming and placement guidelines recommended by Oracle Corporation for Oracle software and databases. It can also be thought of as a set of "good habits" to adopt when organizing Oracle directories and files on your computer. All Oracle products on the Oracle8i Enterprise Edition for Windows NT are OFA-compliant; that is, Oracle Universal Installer places Oracle products in directory locations that follow the OFA guidelines.

One of the many benefits of OFA is that you can separate Oracle software executables from database files. Previously, database files were placed in ORACLE_HOME\DATABASE, (for example, C:\ORANT\DATABASE) a subdirectory of the Oracle home directory that also contained Oracle software. Using OFA, you can put Oracle software in X:\ORACLE_BASE\ORACLE_HOME and database files in X:\ORACLE_BASE\ORADATA\DB_NAME.

Additional Information: For more information on OFA and the type of directory structure where you should place your database files after migration or upgrade, see "Optimal Flexible Architecture Overview".

---