2
Migrating or Upgrading to Release 8.1

This chapter describes how to migrate from Oracle7 or upgrade an Oracle8 database to the present Oracle8i release on Windows NT.

Specific topics discussed are:


For more information on...	See...
Installing the Oracle Parallel Server on Windows NT	Oracle8i Installation Guide for Windows NT Oracle8i Parallel Server Setup and Configuration Guide
Migrating and upgrading	Oracle8i Migration guide: Chapter 4, "Migrating from Oracle7 Using the Migration Utility". Chapter 7, "Upgrading from a Previous Version 8 Release to the New Oracle8i Release". Chapter 8, "After Migrating or Upgrading the Database".
Configuration issues	Oracle8i Parallel Server Setup and Configuration Guide

New Features in Release 8.1

The new features in Oracle Parallel Server for Windows NT release 8.1 are described in the table below. These features are described in detail in your Oracle8i documentation set.

New Feature Description

Optimal Flexible Architecture (OFA)

Provides a structured method for installing the Oracle8i database and applications in a manner which helps promote ease of maintenance, improved performance, and reliability.

Oracle Universal Installer

The new installer is based on a Java engine that provides an extensible environment able to handle advanced software installation requirements. Oracle Universal Installer provides users with a consistent interface across all platforms on which Oracle is available.
Note: Versions of the Installer previous to release 8.1 are referred to as "Oracle Installer".

Easy configuration

Configuration was a manual process in Oracle8. While this manual process is still available for this release, Oracle Database Configuration Assistant can be run to create an Oracle Parallel Server database. The Oracle Database Configuration Assistant can be run automatically after installation or at a later time in stand-alone mode.

OSD Performance and Management (P&M) component implemented in Oracle Parallel Server Manager Option

The P&M component was a vendor-supplied component installed with the OSD layer. This component interacted with the Oracle Enterprise Manager tools. Because P&M must be implemented in a precise manner, this component is now installed with Oracle Parallel Server rather than as an OSD module.

Initialization parameter file name changes

The initialization parameter file that contains common parameters shared from node-to-node was called INIT_COM.ORA in prior releases. This file name has been replaced by INITDB_NAME.ORA. Each instance still has its own initialization file, typically named INIT.ORA.

New Feature	Description
Optimal Flexible Architecture (OFA)	Provides a structured method for installing the Oracle8i database and applications in a manner which helps promote ease of maintenance, improved performance, and reliability.
Oracle Universal Installer	The new installer is based on a Java engine that provides an extensible environment able to handle advanced software installation requirements. Oracle Universal Installer provides users with a consistent interface across all platforms on which Oracle is available. Note: Versions of the Installer previous to release 8.1 are referred to as "Oracle Installer".
Easy configuration	Configuration was a manual process in Oracle8. While this manual process is still available for this release, Oracle Database Configuration Assistant can be run to create an Oracle Parallel Server database. The Oracle Database Configuration Assistant can be run automatically after installation or at a later time in stand-alone mode.
OSD Performance and Management (P&M) component implemented in Oracle Parallel Server Manager Option	The P&M component was a vendor-supplied component installed with the OSD layer. This component interacted with the Oracle Enterprise Manager tools. Because P&M must be implemented in a precise manner, this component is now installed with Oracle Parallel Server rather than as an OSD module.
Initialization parameter file name changes	The initialization parameter file that contains common parameters shared from node-to-node was called INIT_COM.ORA in prior releases. This file name has been replaced by INITDB_NAME.ORA. Each instance still has its own initialization file, typically named INIT.ORA.

Rolling Upgrades

Rolling upgrades--where different databases, or different instances of the same database in Oracle Parallel Server, are upgraded to a new version of Oracle one at a time--are not supported. All software upgrades must be upgraded at the same time on all nodes of the cluster, to maintain version consistency.

Migrating from Oracle7

If the Oracle Universal Installer detects an earlier version of an Oracle database on your hard drive, you will be prompted to migrate or upgrade the database to release 8.1. Do not click the Upgrade or Migrate... check box, as the Oracle Data Migration Assistant does not support Oracle Parallel Server. Instead, use the Migration utility to migrate after installation.

Migrating on Windows NT involves disabling the OracleCMService and starting and shutting down the Operating System Dependent (OSD) layer at a specific point during migration.

See:

Oracle8i Migration guide, Chapter 4, "Migrating from Oracle7 Using the Migration Utility" page 4-9, for considerations on using the Migration Utility and system requirements.

Prepare the Oracle7 Source Database for Migration

Complete the following steps before you migrate your Oracle7 database to Oracle8i:

Start with an Oracle7 database supported by the Migration Utility. If your database release number is lower than the release supported by the Migration utility on Windows NT, then upgrade or migrate the database to a supported release.

See:

Oracle8i Installation Guide for Windows NT for the Oracle7 database releases supported by the Migration Utility.

If the Procedural Option is not installed, then use your Oracle7 installation media to install it. To determine if it is installed, start Server Manager or SQL*DBA, depending on the version of Oracle7 you are migrating from.

See:

Oracle8i Installation Guide for Windows NT for the Oracle7 database releases supported by Server Manager or SQL*DBA.

The following is an example of the messages you will see when Server Manager starts:

Oracle Server Manager Release 2.3.3.0.0 - Production

Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.

Oracle7 Server Release 7.3.4.0.0 - Production
With the distributed, replication, parallel query, Parallel Server
and Spatial Data options
PL/SQL Release 2.3.4.0.0 - Production

If you see "PL/SQL" in the messages, as in the last line in the preceding example, then the Procedural Option is installed. Otherwise, it is not installed.

The messages you see may be slightly different, based on the options you have installed and their release numbers.

Make sure all data files and tablespaces are either online or offline normal.

To determine whether any data files require recovery, issue the following SQL statement:

SELECT * FROM V$RECOVER_FILE;

You should see a "0 rows selected" message, which indicates that all data files are either online or offline normal. If any data files are listed, then you must restore the data files before you migrate the database. You can use the V$DATAFILE dynamic performance view to find the data file name based on the data file number. The Oracle8i Migration utility will not proceed, and will display an error, if any data files require media recovery.

Tablespaces that are not taken offline cleanly must be dropped or brought online before migration. Otherwise, these tablespaces will not be available under Oracle8i after the migration. Typically, tablespaces that are taken offline by using an ALTER TABLESPACE OFFLINE IMMEDIATE or ALTER TABLESPACE OFFLINE TEMPORARY statement require media recovery.

After migration, tablespaces that are offline when you open the Oracle8i database remain in Oracle7 database file format. The offline tablespaces can be brought online at any time after migration, and the file headers are converted to Oracle8i format at that time. In addition, if you want to avoid large restores in the event of a failure, then you can make all tablespaces except SYSTEM and ROLLBACK offline normal; then, you can restore only the data files for SYSTEM and ROLLBACK if you need to run another migration.

Make sure no user or role has the name OUTLN, because this schema is created automatically when you install Oracle8i. If you have a user or role named OUTLN, then you must drop the user or role and recreate it with a different name.

To check for a user with the name OUTLN, issue the following SQL statement:

SELECT USERNAME FROM DBA_USERS WHERE USERNAME = 'OUTLN';

If you do not have a user named OUTLN, then zero rows are selected.

To check for a role with the name OUTLN, issue the following SQL statement:

SELECT ROLE FROM DBA_ROLES WHERE ROLE = 'OUTLN';

If you do not have a role named OUTLN, then zero rows are selected.

Make sure no user or role has the name MIGRATE, because the Oracle8i Migration utility creates this schema and uses it to replace any pre-existing user or role with this name, and finally drops it from the system.

To check for a user with the name MIGRATE, issue the following SQL statement:

SELECT USERNAME FROM DBA_USERS WHERE USERNAME = 'MIGRATE';

If you do not have a user named MIGRATE, then zero rows are selected.

To check for a role with the name MIGRATE, issue the following SQL statement:

SELECT ROLE FROM DBA_ROLES WHERE ROLE = 'MIGRATE';

If you do not have a role named MIGRATE, then zero rows are selected.

Make sure the SYSTEM rollback segment does not have an OPTIMAL setting. An OPTIMAL setting may cause errors during migration.

To check the OPTIMAL setting for the SYSTEM rollback segment, issue the following SQL statement:

SELECT A.USN, A.NAME, B.OPTSIZE
    FROM V$ROLLNAME A, V$ROLLSTAT B
    WHERE A.USN = B.USN AND NAME = 'SYSTEM';

Your output should be similar to the following:

USN        NAME                           OPTSIZE   
---------- ------------------------------ ----------
         0 SYSTEM                                   
1 row selected.

If there is a value in the OPTSIZE column, then issue the following SQL statement to set optimal to NULL:

ALTER ROLLBACK SEGMENT SYSTEM STORAGE (OPTIMAL NULL);

You can reset OPTIMAL when migration is complete.

Increase the maximum number of extents for your SYSTEM rollback segment by altering the MAXEXTENTS parameter in the STORAGE clause of the ALTER ROLLBACK SEGMENT statement (optional).

The following is an example of the ALTER ROLLBACK SEGMENT statement:

ALTER ROLLBACK SEGMENT system
   STORAGE (MAXEXTENTS 121);

You may need more space in the SYSTEM rollback segment to complete the migration successfully. If there is not enough space in your SYSTEM rollback segment, then you may encounter errors when you run the Migration utility in the Oracle7 environment.

Make sure you have the required release of SQL*Net installed.

Migrating From Required SQL*Net Release

Oracle release 7.3.2

SQL*Net release 2.3.2.1.12 or higher
Note: If your release of SQL*Net is below release 2.3.2.1.4, you must first install release 2.3.2.1.4 before you can upgrade to release 2.3.2.1.12. Contact Oracle Support Services to obtain the patch that includes release 2.3.2.1.4.

Oracle release 7.3.3

SQL*Net release 2.3.3.0.3 or higher

Migrating From	*Required SQLNet Release**
Oracle release 7.3.2	SQLNet release 2.3.2.1.12 or higher Note:* If your release of SQL*Net is below release 2.3.2.1.4, you must first install release 2.3.2.1.4 before you can upgrade to release 2.3.2.1.12. Contact Oracle Support Services to obtain the patch that includes release 2.3.2.1.4.
Oracle release 7.3.3	SQL*Net release 2.3.3.0.3 or higher

If the required release of SQL*Net is not installed, complete the following steps to install it:

Obtain the year 2000-compliant Oracle Installer for release 7.3 from Oracle Corporation.
Start the Oracle Installer you obtained in Step a. Respond to the Oracle Installer screens until you reach the Software Asset Manager window.
At the Software Asset Manager window, click the From button.
Navigate to the drive containing the CD-ROM for the current 8.1 release of Oracle.
Navigate to the appropriate directory on the CD-ROM:

If you are installing SQL*Net release 2.3.2.1.12, navigate to the following directory on the CD-ROM:

\PATCHES\SQLNET\232112\NT_X86\INSTALL

If you are installing SQL*Net release 2.3.3.0.3, navigate to the following directory on the CD-ROM:

\PATCHES\SQLNET\23303\NT_X86\INSTALL

Open the NT.PRD file.
Complete the installation.
Exit the Oracle Installer.

Note:

If you cannot install the required SQL*Net release, contact Oracle Support Services.

Prepare the Cluster for Installation

To prepare the cluster for the Oracle8i Enterprise Edition software, perform the following steps on each node in the cluster:

Shut down the Oracle7 database cleanly using the SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE command; do not use SHUTDOWN ABORT. The Oracle7 source database must be shut down cleanly; therefore, no redo information or uncommitted transactions can remain.

C:> SVRMGR23
SVRMGR> CONNECT INTERNAL
SVRMGR> SHUTDOWN IMMEDIATE

Ensure all Oracle7 services are shutdown, including the OracleCMService service:

Double-click the Services icon in the Control Panel window.

The Services dialog box appears.

Select an OracleServiceSID.
Click Stop to stop a service.

Change all the version 7 OSDs including the OracleCMService service to Manual startup:

Double-click the corresponding version 7 OSD and the OracleCMService service. The Services dialog box appears.
Click Manual in the Startup Type group box.
Click OK to dismiss the Services dialog box.
Click Close in the Services dialog box.

Shut down the version 7 OSD layer, as described in your vendor documentation. In most cases, you can use the same procedure as stopping an Oracle service, described in Step 2.
Rename the OSD key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD73 using the registry editor, REGEDIT. OSD73 acts as a temporary storage for the version 7 OSD layer, which will be used later in the migration process.

To start the registry:

Choose Start > Run, enter REGEDIT in the Open field, and click OK.

The Registry Editor window appears.

Right-click to rename the OSD key.

Install the version 8.1 OSD layer, being sure not to overwrite the version 7 OSD files. See your vendor documentation for further information.
Start the version 8.1 OSD layer, as described in your vendor documentation. Perform diagnostics on the clusterware as described in your vendor documentation.
Backup raw partitions using OCOPY. Enter the following syntax:

C:\> OCOPY \\.\PHYSICALDRIVEN NEW_FILE

where:

PHYSICALDRIVE is the physical drive that holds a single raw database file
N is the number(s) representing each of the physical drives in the system
NEW_FILE is the name and location of the backup copy

For example, to backup the logical partition for a system tablespace to a file, enter:

C:\> OCOPY \\.\OPS_SYSTEM1 OPS_SYSTEM1

Use your existing partitions and symbolic link names. Oracle Corporation recommends you backup logical partitions to files with the same name. For example, backup \\.\OPS_SYSTEM1 to a file named OPS_SYSTEM1.

See::

Oracle8i Administrator's Guide for Windows NT, Chapter 11, Backing Up and Recovering Database Files, on using OCOPY.

Install the Release 8.1 Oracle8i Enterprise Edition

During installation, software components are installed on the node from which Oracle Universal Installer is run and pushed to the selected nodes in the cluster. The Oracle Universal Installer installs Oracle Parallel Server only if a cluster is detected.

Perform the following step before running Oracle Universal Installer:

From the node where you intend to run the installer, verify you have administrative privileges to the other nodes. Enter the following command for each node that is a part of the cluster:

NET USE \\HOST_NAME\C$

where host_name is the host name defined in the DefinedNodes registry value for Cluster Manager.

A successful connection results in the following message:

The command completed successfully.

Oracle Corporation recommends using the same user name and password on each node in a cluster or use a domain user name. If you use a domain user name, log on under a domain with username and password which has administrative privileges on each node.

To install Oracle8i Enterprise Edition on one node in the cluster:

See :

Oracle8i Installation Guide for Windows NT to prepare for installation and start the Oracle Universal Installer.

At the Welcome screen of the Oracle Universal Installer, click Next. The File Locations screen appears.

If you need help at any screen or want to consult more documentation about the Oracle Universal Installer, then click the Help button to open the online help.

At the File Locations screen, complete the following steps:

Do not change the text in the Source field. This is the location of files used for installation.
If there is a Destination Name field, enter the name of a new Oracle home in this field.
Enter the complete path of the Oracle home directory where you want to install the new release in the Destination Path field. Click the Browse button to navigate to the directory. Click Next.

Note:

You must install the new 8.1 release in an Oracle home separate from the Oracle7 release.

The Available Products screen appears.

Select Oracle8i Enterprise Edition from the Available Products page. Click Next.
Select either Typical or Custom from the Installation Types page. Minimal is not supported for Oracle Parallel Server.


Typical Installation Type	Custom Installation Type
Net8 Configuration Assistant and Oracle Database Configuration Assistant run after software installation with no user input. Net8 Configuration Assistant creates the network configuration. Oracle Database Configuration Assistant creates a starter database and adds necessary information to the network configuration.	Oracle Universal Installer prompts you with a choice to create a database by using one of the following methods: Oracle Database Configuration Assistant during installation Oracle Database Configuration Assistant or manual methods sometime after installation

After you make your selection, click Next.

If you chose Custom, the Available Product Components screen appears. Complete the following steps:

Ensure Oracle Parallel Server under the Oracle Database Options folder is selected in the Available Product Components screen. Click Next.

Make sure you install Oracle Utilities to install the Migration utility.

Make sure you install all of the options you installed with the Oracle7 database, assuming you do not want to discontinue use of a particular option. For example, if you installed Oracle replication in Oracle7, then you should install it in Oracle8i.

Select the nodes to which you want the software installed from the Cluster Node selection page. Click Next.

The node on which you are running the installation is selected whether or not you select it.

If the list of nodes does not include nodes you expect, the vendor-supplied clusterware is either not running, or not properly configured.

In the Database Identification page, enter an appropriate global database name, a name comprised of the database name and database domain, such as OP.US.ACME.COM, and accept or change the common prefix that is to be used for the SID for each instance.

Each instance has a SID that is comprised of the common prefix entered here and a thread ID that is automatically generated. For example, if OP is entered, the first instance in the cluster is given a SID of OP1, and the second instance is given a SID of OP2.

Respond to the remaining screens that enable you to specify your custom installation settings, until you reach the Upgrading or Migrating an Existing Database page.

At the Upgrading or Migrating an Existing Database page, leave the Upgrade or Migrate an Existing Database check box unselected. Click Next.

Attention:

If you select the Upgrade or Migrate an Existing Database check box, then the Oracle Data Migration Assistant is started automatically after installation. The Oracle Data Migration Assistant does not support Oracle Parallel Server migrations. Do not start the Oracle Data Migration Assistant.

At the Create Database page, select the No option, indicating that you do not want to create a database, because you are migrating an existing database. Click Next.

Complete any remaining screens until you reach the Summary page. Click the Help button if you need help for a certain screen.

At the Summary screen, make sure all of the settings and choices are correct for your installation. Then, click Install. The Oracle Universal Installer performs the installation, which may take some time.

During installation no message appears to indicate components are installed to the other nodes.

When installation is completed successfully, click the Exit button to close the Oracle Universal Installer.

Perform Post-Installation Steps

To prepare the cluster for the Oracle7 migration process, perform the following steps:

Shut down and restart your computer.
Change the OracleCMService and the OracleServiceSID services to Manual startup:

Double-click the Oracle8i service. The Services dialog box appears.
Click Manual in the Startup Type group box.
Click OK to dismiss the Services dialog box.
Click Close in the Services dialog box.

Shut down the release 8.1 OSD layer on each node in the cluster, as described in your vendor documentation.
On the node from which you intend to run the Migration utility, rename the OSD key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD81 using the Registry Editor, REGEDIT. OSD81 acts as a temporary storage for the release 8.1 OSD layer while the Oracle7 database is being migrated or upgraded.

To start the registry:

Choose Start > Run, enter REGEDIT in the Open field, and click OK.

The Registry Editor window appears.

Right-click to rename the OSD key.

On the node from which you intend to run the Migration utility, start the version 7 OSD layer, as described in your vendor documentation.
On the node from which you intend to run the Migration utility, start the OracleCMService and the OracleServiceSID services:

Double-click the Services icon in the Control Panel window. The Services dialog box appears.
Select an Oracle service.
Click Start.
Click Close to dismiss Services dialog box.

On the node from which you intend to run the Migration utility, set the Oracle home path to the Oracle7 Oracle home path with a tool such as the Oracle Home Selector:

Choose Start > Programs > Oracle Installation Products > Oracle Home Selector.
Select the Oracle7 home from the drop-down list.

Migrate the Oracle7 Source Database

Complete the steps in the Oracle7 environment to migrate an Oracle7 source database to Oracle8i using the Migration utility.

Start up your Oracle7 database:

C:> SVRMGR23
SVRMGR> CONNECT INTERNAL
SVRMGR> STARTUP

Make sure the NLS_LANG environment variable is set to the character set you are using for your database.

To check your character set, issue the following SQL statement:

SELECT * FROM V$NLS_PARAMETERS 
   WHERE PARAMETER = 'NLS_LANGUAGE'   
      OR PARAMETER = 'NLS_TERRITORY'
      OR PARAMETER = 'NLS_CHARACTERSET';

You use all three values returned by this query to set NLS_LANG. For example, suppose your output for the query above is the following:

PARAMETER                   VALUE                                                           
---------------------  --------------------------- 
NLS_LANGUAGE               AMERICAN                                                        
NLS_TERRITORY              AMERICA                                                         
NLS_CHARACTERSET          US7ASCII

In this case, set NLS_LANG to the following at an MS-DOS command prompt:

AMERICAN_AMERICA.US7ASCII

See:

Oracle8i National Language Support Guide for information about setting NLS_LANG.

Make sure you have DBA privileges, which are required to run the Oracle8i Migration utility.

To check if you have DBA privileges, query the DBA_ROLE_PRIVS static data dictionary view. For example, if you are connected as user SYSTEM, then enter the following SQL statement:

SELECT * FROM DBA_ROLE_PRIVS WHERE GRANTEE = 'SYSTEM';

You have DBA privileges if 'DBA' is listed in the GRANTED_ROLE column for the user. If you do not have DBA privileges, then connect as a user who does.

Make sure no other DBA with RESTRICTED SESSION privilege connects to the database while the Migration utility is running. Also, "Normal" users should not connect to the database during migration.
Determine the files that you will back up in Step 8 by issuing the following SQL statements:

SPOOL V7FILES.LOG;
SELECT MEMBER FROM V$LOGFILE;

SELECT NAME FROM V$DATAFILE;

SELECT VALUE FROM V$PARAMETER WHERE NAME = 'CONTROL_FILES';
SPOOL OFF;

The V7FILES.LOG spool file lists all of the files that you must back up in Step 8.

Shutdown the Oracle7 database cleanly using the SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE statement; do not use SHUTDOWN ABORT. The Oracle7 source database must be shut down cleanly; therefore, no redo information or uncommitted transactions can remain.

C:> SVRMGR23
SVRMGR> CONNECT INTERNAL
SVRMGR> SHUTDOWN IMMEDIATE

Note:

If you do not shut down the Oracle7 database before migration starts, then the Migration utility will stop and display an error message.

Shutdown all Oracle Parallel Server services.

Double-click the Services icon in the Control Panel window. The Services dialog box appears.
Select an Oracle Parallel Server OracleServiceSID.
Click Stop.
Click Close to dismiss Services dialog box.

Make a complete backup of your Oracle7 database. Make sure you back up the files listed in the V7FILES.LOG spool file that you generated in Step 5.

Caution:

If you encounter any problems with the migration, you will need to restore the database from this backup. Make sure you back up your database now as a precaution.

See:

The Oracle7 Server Administrator's Guide for information about backing up your Oracle7 database.

Run the Migration Utility

Complete the following steps to run the Migration Utility:

In the new Oracle8i Oracle home, run the Migration utility by entering the Migration utility command at the MS-DOS command line with the PFILE option included:

C:\> MIG PFILE=ORACLE7_HOME\DATABASE\INIT_PARAM_FILE

Replace the ORACLE7_HOME variable with the complete path to the Oracle7 Oracle home directory. Also, replace the INIT_PARAM_FILE variable with the full name of the initialization parameter file for the Oracle7 database.

For example, if the ORACLE7_HOME is C:\ORANT and the INIT_PARAM_FILE is INITORCL.ORA, then enter the following:

C:\> MIG PFILE=C:\ORANT\DATABASE\INITORCL.ORA

You can enter MIG with the PFILE option only to run the Migration utility with a default set of options, or you can enter MIG followed by more selected options.

See:

Oracle8i Migration guide, "Review Migration Utility Command-Line Options" for information about MS-DOS command line options. Oracle Corporation recommends using the spool option, because it makes it easier to check your migration results when the migration is complete.

If the Oracle7 Password dialog box appears when you run the Migration utility, then enter the password for the INTERNAL user on the Oracle7 database. This prompt appears because the DBA_AUTHORIZATION registry parameter is set improperly or is not set at all.
After the Migration utility has run successfully, stop the Oracle7 service OracleServiceSID. For example, if your SID is OP1:

Double-click the Services icon in the Control Panel window. The Services dialog box appears.
Select OracleServiceOP1.
Click Stop.
Click Close to dismiss Services dialog box.

Delete the Oracle7 service at the MS-DOS command prompt using ORADIM7x. The following table lists the MS-DOS command to run for each Oracle7 release:

Oracle7 Release... Enter at the MS-DOS Command Prompt...

7.1

C:\> ORADIM71 -DELETE -SID SID

7.2

C:\> ORADIM72 -DELETE -SID SID

7.3

C:\> ORADIM73 -DELETE -SID SID

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

For example, if your Oracle7 release is release 7.3.4 and your SID is ORCL, then enter the following at the MS-DOS command prompt:

C:\> ORADIM73 -DELETE -SID ORCL

Restart your computer.
Create the Oracle8i database service at the MS-DOS command line:

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

This syntax includes the following variables:

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 database instance. This is the password for INTERNAL user. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.

USERS

is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.

ORACLE_HOME

is the release 8.1 Oracle home directory. Ensure that you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory.

For example, if your SID is ORCL, your PASSWORD is TWxy579, the maximum number of USERS is 10, and the ORACLE_HOME directory is C:\ORA81, then enter the following command:

C:\> ORADIM -NEW -SID ORCL -INTPWD TWxy579 -MAXUSERS 10 -STARTMODE AUTO 
     -PFILE C:\ORA81\DATABASE\INITORCL.ORA

Check the Migration Results

Check the results after running the Migration utility. The Migration utility generates informational messages and echoes its progress as it runs the MIGRATE.BSQ script.

See:

If the Migration utility exits with an ORA- error, check the Oracle8i Migration guide, Appendix A, "Troubleshooting Migration Problems" for information about the error and the actions to perform to resolve the problem.

The Migration utility creates a convert file that contains the information of the Oracle7 control file. Later in the migration process, the convert file is used by ALTER DATABASE CONVERT to create a new control file in Oracle8i.

The default location is ORACLE_HOME\RDBMS in the Oracle8i environment, and the default file name in this directory is CONVERT.ORA.

Caution:

Do not open the Oracle7 database, which was shut down by the Oracle8i Migration 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 Oracle8i. If the Oracle7 database is opened after running the Migration utility, then the SCN check will fail when the database is converted to Oracle8i, and an ORA-1211 error will be displayed, stating "Oracle7 data file is not from migration to Oracle8". Therefore, if the Oracle7 database is opened, then you must rerun the Migration utility, starting at Step 6.

Preserve the Oracle7 Source Database

After you successfully run the Migration utility, perform a cold backup of the Oracle7 database. This backup serves the following purposes:

If you wish to return to the Oracle7 database after executing the ALTER DATABASE CONVERT statement on Oracle8i, then you can restore the backup, start the Oracle7 database, and complete procedures in abandoning migration.

See::

Oracle8i Migration guide, "Abandoning the Migration".

It can be used as the first Oracle8i backup for an Oracle8i recovery.
If an error occurs at Oracle8i database convert time (ALTER DATABASE CONVERT or ALTER DATABASE OPEN RESETLOGS), then you can restore this backup, fix the problems, and continue the conversion process. However, if you restore a backup that was performed before you ran the Migration utility, then you must rerun the Migration utility.

See:

The Oracle7 Server Administrator's Guide for information about performing backup and restore operations on your Oracle7 database.

In addition, perform a backup of the entire Oracle7 software distribution, including the Oracle7 home directory. Make sure the backup includes the following:

all of the subdirectories
control files
data files and online redo log files (in case any data files in the Oracle7 database are lost or unreadable), although these files should not contain any outstanding redo information.
parameter files
convert file
scripts that create objects in the Oracle7 database
scripts that could restore the original database, if necessary

Perform Post-Oracle7 Migration Steps

To complete the Oracle Parallel Server migration, perform the following steps:

On the node from which you ran the Migration utility:

Stop the OracleCMService and the OracleServiceSID services:


Double-click the Services icon in the Control Panel window. The Services dialog box appears.
Select an Oracle service.
Click Stop.
Click Close to dismiss Services dialog box.

Stop the version 7 OSD layer, as described in your vendor documentation.
Rename the OSD key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD73 using the Save Subtree As option under the File menu.

This disables the version 7 OSD layer.

Rename the OSD81 key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD using the Save Subtree As option under the File menu.

This enables the release 8.1 OSD layer.

Set the Oracle home path to the Oracle8i Oracle home path with a tool such as the Oracle Home Selector:

1. Choose Start > Programs > Oracle Installation Products > Oracle Home Selector.

2. Select the Oracle8i home from the drop-down list.

Perform the following on each node in the cluster:

Delete the Oracle7 OracleServiceSID service using the appropriate version of ORADIM. From the Oracle7 Oracle home MS-DOS command prompt, enter:

C:> CD ORACLE7_HOME/BIN
C:> ORADIM73 -DELETE - SID SID

Create an Oracle8i OracleServiceSID service for each instance

C:> ORADIM -NEW -SID SID -INTPWD INTERNAL_PWD -STARTMODE AUTO -PFILE
DRIVE:\PATH\INITSID.ORA

Perform Migration Steps in the Oracle8i Environment

Complete the following migration steps in the Oracle8i environment:

On all nodes, either remove or rename the database's control files, or use the CONTROL_FILES initialization parameter to specify new control file names. The CONTROL_FILES initialization parameter typically is set in the initialization parameter file, but it may be set in the INITDB_NAME.ORA file instead.

You will issue the ALTER DATABASE CONVERT statement in Step 10. This statement automatically creates new control files. If you do not use the CONTROL_FILES parameter, then this statement uses the control file names of your pre-migration database (derived from the CONVERT file) and returns an error if the control files already exist. Therefore, in this case, you must remove or rename the control files.

However, if you use the CONTROL_FILES initialization parameter to specify new control file names, then the ALTER DATABASE CONVERT statement creates the new control files with the names you specify, and you do not need to remove the old control files. For a complete list of your existing control files, check the V7FILES.LOG spool file you created.

Control files are considerably larger in Oracle8i than in Oracle7. For example, Oracle7 control files in the hundreds of kilobytes may expand into tens of megabytes in Oracle8i. The larger size in Oracle8i results from the storage of more information in the control file, such as backup and tablespace records. This size increase could be important if a control file is on a raw device or if its available disk space is restricted.

Note:

The CONTROL_FILES initialization parameter specifies one or more names of control files, separated by commas. Oracle Corporation recommends using multiple files on different devices or mirroring the file at the operating system level. See Oracle8i Administrator's Guide for more information.

On all nodes, copy files that are important for migration to a location outside of the Oracle7 Oracle home:

The convert file, CONVERT.ORA, should reside in ORACLE_HOME\RDBMS in the Oracle8i environment. It is placed in this directory automatically by the Migration utility, and you do not need to move it.
If you have a password file that resides within the Oracle7 Oracle home, then move or copy the password file to the Oracle8i Oracle home directory.

The default password file is ORACLE_HOME\DATABASE\PWDSID.ORA. where SID is your Oracle instance ID.

If your initialization parameter file resides within the Oracle7 Oracle home, then move or copy it to a location outside of the Oracle7 Oracle home. By default Oracle looks for the initialization parameter file in ORACLE_HOME\DATABASE. The initialization parameter file can reside anywhere you wish, but it should not reside in the Oracle7 Oracle home after you migrate to Oracle8i.
If the initialization parameter file contains an IFILE (include file) entry that resides within the Oracle7 Oracle home, then move or copy the file specified in the IFILE entry to a location outside of the Oracle7 Oracle home.
If your INITDB_NAME.ORA file resides within the Oracle7 Oracle home, then move or copy the INITDB_NAME.ORA file to a location outside of the Oracle7 Oracle home.

On all nodes, adjust the initialization parameter file in the Oracle8i environment for use with Oracle8i. Specifically, complete the following steps:

Set the COMPATIBLE initialization parameter in your initialization parameter file to a valid version 8 setting, such as 8.0.6 or 8.1.6. Make sure the COMPATIBLE parameter is not set to any Oracle7 release, because if it is, then you will not be able to start the Oracle8i database.

See :

Oracle8i Migration guide,"Setting the COMPATIBLE Initialization Parameter" for information.

Remove obsolete parameters and adjust changed parameters. Certain Oracle7 initialization parameters are obsolete in version 8. Remove all obsolete initialization parameters from any initialization parameter file that will start an Oracle8i instance; obsolete parameters may cause errors in Oracle8i. Also, alter any parameter whose syntax has changed in version 8.

See:

Oracle8i Migration guide, Appendix B, "Changes to Initialization Parameters" for lists of new, renamed, and obsolete parameters, andOracle8i Parallel Server Concepts and Administration for more information about obsolete Oracle Parallel Server initialization parameters.

If you are updating snapshots automatically by using the JOB_QUEUE_PROCESSES initialization parameter, set JOB_QUEUE_PROCESSES to 0 (zero) during migration. After migrating your database, you can reset it to use this parameter.
Set the PARALLEL_SERVER parameter to FALSE in the INIT.ORA file. This only needs to be set on the node from which you ran the Migration utility. Setting this parameter to FALSE ensures the database will be started in EXCLUSIVE mode, which is required to run the Oracle8i migration. You can change it back to TRUE after migration is complete.
Make sure your DB_DOMAIN initialization parameter is set properly.

See:

Oracle8i Migration guide, "The DB_DOMAIN Parameter" for more information about setting this initialization parameter.

Change the BACKGROUND_DUMP_DEST and USER_DUMP_DEST initialization parameters that point to RDBMS71, RDBMS72, or RDBMS73 to point to the following directories instead (optional):

Initialization Parameter Change Setting To

BACKGROUND_DUMP_DEST

ORACLE_BASE\ORADATA\DB_NAME

USER_DUMP_DEST

ORACLE_BASE\ORADATA\DB_NAME\ARCHIVE

In the settings, substitute the complete ORACLE_BASE path for ORACLE_BASE and substitute the database name for DB_NAME.

Make sure all path names in the initialization parameter file are fully specified. You should not have relative path names in the initialization parameter file.
If the initialization parameter file contains an IFILE entry, then change the IFILE entry in the initialization parameter file to point to the new location you copied it to in Step 2. Then, edit the file specified in the IFILE entry in the same way that you edited the initialization parameter file in sub-steps a to g.
Modify the INITDB_NAME.ORA file in the same way that you modified the initialization parameter file, steps a to g.

Make sure you save all of the files you modified after making these adjustments.

If the Oracle8i DB_NAME is different from the Oracle7 DB_NAME, then complete the following step. Otherwise, skip to Step 5.

Set the DB_NAME initialization parameter in the initialization parameter file to the Oracle8i database name.

Make sure all online data files are accessible and in the correct directories. If you are using a raw disk, then log files also must be accessible.
Change to the ORACLE_HOME\RDBMS\ADMIN directory. You should be in the Oracle8i Oracle home.
Start Server Manager. Enter SVRMGRL at the MS-DOS command prompt to start Server Manager in Oracle8i.
Connect to the database instance as user INTERNAL.

SVRMGR> CONNECT INTERNAL

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

SVRMGR> STARTUP NOMOUNT

Caution:

Starting the database instance in any other mode might corrupt the database.

You may need to use the PFILE option to specify the location of your initialization parameter file.

You may see error messages listing obsolete initialization parameters. If so, then make a note of the obsolete initialization parameters and continue with the migration normally. Then, remove the obsolete initialization parameters the next time you shut down the database (Step 18).

Create a new Oracle8i database control file and convert the file headers of all online tablespaces to Oracle8i format by issuing the following statement:

SVRMGR> ALTER DATABASE CONVERT;

Successful execution of this statement is the "point of no return" to Oracle7 for this database. However, if necessary, you can restore the Oracle7 database from backups.

If errors occur during this step, then correct the conditions that caused the errors and rerun the Migration utility. Restart at Step 1, "Startup your Oracle7 database:" Otherwise restore the backup you performed after you ran the Migration utility.

See:

Oracle8i Migration guide, "Problems at the ALTER DATABASE CONVERT Statement" for information about common errors encountered at this step and the actions required to resolve them.

Open the Oracle8i database with the following statement:

SVRMGR> ALTER DATABASE OPEN RESETLOGS;

When the Oracle8i database is opened, all rollback segments that are online are converted to the new Oracle8i format.

If you encounter errors when you issue this statement, then start the migration process over from the beginning, ensuring the database is not opened in the Oracle7 environment after the Migration utility completes. Make sure you completed all of the pre-migration steps.

Set the system to spool results to a log file for later verification of success:

SVRMGR> SPOOL CATOUTM.LOG

If you want to see the output on your screen of the scripts you will run, then you also can issue a SET ECHO ON statement:

SVRMGR> SET ECHO ON

Run the Oracle8i database conversion script U0703040.SQL:

SVRMGR> @U0703040.SQL

The U0703040.SQL script is the database conversion script for all 7.1, 7.2, and 7.3 releases supported by the Migration utility. The U0703040.SQL script creates and alters certain system tables and drops the MIGRATE user. It also runs the CATALOG.SQL and CATPROC.SQL scripts, which create the system catalog views and all the necessary packages for using PL/SQL.

If you encounter any problems when you run this script, or any of the scripts in the remaining steps, then correct the cause(s) of the problems and rerun the script. You can rerun any of the scripts described in this chapter as many times as necessary.

See:

Oracle8i Migration guide, "Running Scripts" for information about the types of errors to look for when you run a script.

If the Oracle system has Oracle replication installed, then complete the following steps:

Run CATREP.SQL:

SVRMGR> @CATREP.SQL

Run R0703040.SQL:

SVRMGR> @R0703040.SQL

This R0703040.SQL script performs a post-CATREP.SQL Oracle replication related upgrade.

Run CATPARR.SQL:

SVRMGR> @CATPARR.SQL

Run UTLRP.SQL (optional):

SVRMGR> @UTLRP.SQL

The UTLRP.SQL script recompiles all existing PL/SQL modules that were previously in an INVALID state, such as packages, procedures, types, and so on. These actions are optional; however, they ensure that the cost of recompilation is incurred during installation rather than in the future.

Oracle Corporation highly recommends performing this optional step.

Turn off the spooling of script results to the log file:

SVRMGR> SPOOL OFF

Then, check the spool file and verify that the packages and procedures compiled successfully. You named the spool file in Step 12; the suggested name was CATOUTM.LOG.

You should look for errors that alert you to insufficient space, and for errors that alert you that a script failed to run. If you see these types of errors, then your migration may not be completely successful. However, you typically can ignore errors about the failure to alter or drop an object that does not exist.

If you specified SET ECHO ON, then you may want to SET ECHO OFF now:

SVRMGR> SET ECHO OFF

Run SHUTDOWN on the Oracle8i database:

C:> SVRMGRL
SVRMGR> CONNECT INTERNAL
SVRMGR> SHUTDOWN IMMEDIATE

Caution:

Use SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE. Do not use SHUTDOWN ABORT.

Executing this clean shutdown flushes all caches, clears buffers, and performs other DBMS housekeeping activities. These measures are an important final step to ensure the integrity and consistency of the newly migrated Oracle8i database.

The COMPATIBLE initialization parameter controls the compatibility level of your database. Set the COMPATIBLE initialization parameter in your initialization parameter file based on the compatibility level you want for your migrated database.

See:

Oracle8i Migration guide, "Setting the COMPATIBLE Initialization Parameter" for information.

Also, if you encountered a message listing obsolete initialization parameters when you started the database in Step 9, then remove the obsolete initialization parameters from the initialization parameter file now.

Set the PARALLEL_SERVER parameter back to TRUE in the INIT.ORA file.

Perform Post-Migration Tasks

Complete the post-migration procedures listed in the table below. These are described in Oracle8i Migration guide, Chapter 8, "After Migrating or Upgrading the Database".

Post-Migration Tasks

Perform a complete backup of the production database.

Change the password for the OUTLN user.

Copy LONGs to LOBs.

Check for bad date constraints.

Adjust the initialization parameters SHARED_POOL_SIZE and LARGE_POOL_SIZE in your initialization parameter file to avoid problems with parallel execution.

If you installed the Java option, install ODCI.JAR AND CARTRIDGESERVICES.JAR files.

Modify your LISTENER.ORA file.

Migrate or upgrade your standby database to Oracle8i release 8.1.

Add new features as appropriate. It is not necessary to make any immediate changes to begin using your Oracle8i database. You may prefer to introduce these enhancements into your database and corresponding applications gradually.

Develop new administrative procedures as needed.

Adjust your initialization parameter file for the new release.

Rebuild unusable bitmap indexes.

Migrate partition views to partition tables.

Migrate or upgrade to the new release of Net8 (optional).

Test the database and compare results.

Tune the migrated database.

Upgrading the Previous Version 8 Database to the New Oracle8i Release

This section guides you through the process of upgrading your database to the new Oracle8i release.

See:

Oracle8i Migration guide for important information on upgrade paths.

Prepare to Upgrade

Perform the following steps on one node only:

Review upgrade issues relating to SQL*Net and Net8.

See:

Oracle8i Migration guide, Appendix F, "SQL*Net and Net8 Considerations for Migrations and Upgrades" for information.

Make sure your DB_DOMAIN initialization parameter is set properly.

See:

Oracle8i Migration guide, "The DB_DOMAIN Parameter" for more information about setting this initialization parameter.

Start Server Manager and connect to the database instance as INTERNAL user.

C:> SVRMGRL
SVRMGR> CONNECT INTERNAL

If you are upgrading from an 8.0 release, then make sure no user or role has the name OUTLN, because this schema is created automatically when you install Oracle8i. If you have a user or role named OUTLN, then you must drop the user or role and recreate it with a different name.

Note:

If you are upgrading from an 8.1 release, then you do not need to perform this check because the OUTLN user should have been created when you installed the previous 8.1 release. Therefore, if you are upgrading from an 8.1 release, then go to Step 5 now. Do not drop the OUTLN user if you are upgrading from a previous 8.1 release.

To check for a user with the name OUTLN, enter the following SQL statement:

SELECT USERNAME FROM DBA_USERS WHERE USERNAME = 'OUTLN';

If you do not have a user named OUTLN, then zero rows are selected.

To check for a role with the name OUTLN, enter the following SQL statement:

SELECT ROLE FROM DBA_ROLES WHERE ROLE = 'OUTLN';

If you do not have a role named OUTLN, then zero rows are selected.

Add space to your SYSTEM tablespace and to the tablespaces where you store rollback segments, if necessary.

Upgrading to a new release requires more space in your SYSTEM tablespace and in the tablespaces where you store rollback segments. If you have enough space on your system, then consider adding more space to these tablespaces. In general, you need at least 20 MB of free space in your SYSTEM tablespace to upgrade. If you run out of space during the upgrade, then you will need to perform the upgrade again.

The following SQL statement illustrates how to add more space to a tablespace:

ALTER TABLESPACE SYSTEM
   ADD DATAFILE 'C:\PATH/HOME/USER1/MOUNTPOINT/ORADATA/DB1/SYSTEM02.DBF'
   SIZE 20M;

Determine the files that you will back up in Step 9 in the next section (when performing a full backup) by issuing the following SQL statements:

SPOOL V8FILES.LOG;
SELECT MEMBER FROM V$LOGFILE;

SELECT NAME FROM V$DATAFILE;

SELECT VALUE FROM V$PARAMETER WHERE NAME = 'CONTROL_FILES';
SPOOL OFF;

The V8FILES.LOG spool file lists all of the files that you must back up in Step 9 in the next section.

Prepare the Cluster for Upgrade

To prepare the cluster for the new version of the Oracle8i Enterprise Edition software, perform the following steps on each node in the cluster:

Shut down the Oracle8 database cleanly using the SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE command; do not use SHUTDOWN ABORT. The Oracle8 source database must be shut down cleanly; therefore, no redo information or uncommitted transactions can remain.

C:> SVRMGRL
SVRMGR> CONNECT INTERNAL
SVRMGR> SHUTDOWN IMMEDIATE

Ensure all version 8 services are shutdown, including the OracleCMService service:

Double-click the Services icon in the Control Panel window.

The Services dialog box appears.

Select an Oracle service.
Click Stop to stop a service.

Change all the version 8 OSDs including the OracleCMService service to Manual startup:

Double-click the corresponding version 8 OSD and the OracleCMService service. The Services dialog box appears.
Click Manual in the Startup Type group box.
Click OK to dismiss the Services dialog box.
Click Close in the Services dialog box.

Shut down the version 8 OSD layer, as described in your vendor documentation. In most cases, you can use the same procedure as stopping an Oracle service, described in Step 2
Rename the OSD key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD80 using the registry editor, REGEDIT. OSD80 acts as a temporary storage for the version 8 OSD layer, which will be used later in the upgrade process.

To start the registry:

Choose Start > Run, enter REGEDIT in the Open field, and click OK.

The Registry Editor window appears.

Right-click to rename the OSD key.

Install the version 8.1 OSD layer, being sure not to overwrite the old version 8 OSD files. See your vendor documentation for further information.
Start the version 8.1 OSD layer, as described in your vendor documentation. Perform diagnostics on the clusterware as described in your vendor documentation.
Backup raw partitions using OCOPY. Enter the following syntax:

C:\> OCOPY \\.\PHYSICALDRIVEN NEW_FILE

where:

PHYSICALDRIVE is the physical drive that holds a single raw database file
N is the number(s) representing each of the physical drives in the system
NEW_FILE is the name and location of the backup copy

For example, to backup the logical partition for a system tablespace to a file, enter:

C:\> OCOPY \\.\OPS_SYSTEM1 OPS_SYSTEM1

See::

Oracle8i Administrator's Guide for Windows NT, Chapter 11, Backing Up and Recovering Database Files, on using OCOPY.

Perform a full offline backup of the database. Make sure you back up the files listed in the V8FILES.LOG spool file that you generated in Step 6.

Caution:

If you encounter any problems with the upgrade, then you will need to restore the database from this backup. Therefore, make sure you back up your database now as a precaution.

See:

Oracle8i Backup and Recovery Guide for more information about backing up a release 8.1 database, or see Oracle8 Backup and Recovery Guide for information about backing up a release 8.0 database.

Exit Server Manager.
Deinstall your current release of Oracle if both of the following conditions are true:

You are upgrading from a previous 8.1 release.
You plan to use the same Oracle home for your current release and the new release to which you are upgrading.

If you plan to use separate Oracle home directories for your current release and the new release to which you are upgrading, then you do not need to deinstall your current release.

Note:

If you are upgrading from an 8.0 release, then you must install the new 8.1 release in an Oracle home separate from the 8.0 release. However, if you are upgrading from a previous 8.1 release, then this restriction does not apply, and you can install the new release into the same Oracle home as the previous release if you wish.

Install Release 8.1 Oracle8i Enterprise Edition

To install, perform the following steps:

On one node, follow from Step 1,, to Step 8, to install the Release 8.1 Oracle8i Enterprise Edition.

Perform Post-Installation Steps

To prepare the cluster for the upgrade process, perform the following steps:

Shut down and restart your computer.
Change the OracleCMService and the OracleServiceSID services to Manual startup:

Double-click the Oracle service. The Services dialog box appears.
Click Manual in the Startup Type group box.
Click OK to dismiss the Services dialog box.
Click Close in the Services dialog box.

Make sure the new release 8 OSD layer is running on each node in the cluster.
Perform the following steps on the node from which you intend to run the upgrade scripts:

Start the OracleCMService and the OracleServiceSID services:

1. Double-click the Services icon in the Control Panel window. The Services dialog box appears.

2. Select an Oracle service.

3. Click Start.

4. Click Close to dismiss Services dialog box.

Set the Oracle home path to the new Oracle8i Oracle home path with a tool such as the Oracle Home Selector:

1. Choose Start > Programs > Oracle Installation Products > Oracle Home Selector.

2. Select the Oracle8i home from the drop-down list.

Upgrade the Database Manually

Complete the following steps to upgrade:

Stop the Oracle8 service OracleServiceSID of the database you are upgrading, where SID is the instance name. For example, if your SID is ORCL:

Double-click the Services icon in the Control Panel window.

The Services dialog box appears.

Select OracleServiceORCL.
Click Stop.
Click Close to dismiss Services dialog box.

Delete the Oracle service at the MS-DOS command prompt using ORADIM. The following table lists the MS-DOS command to run for each Oracle8i release:

Oracle Release... Enter at the MS-DOS Command Line...

8.0

C:\> ORADIM80 -DELETE -SID SID

8.1

C:\> ORADIM -DELETE -SID SID

For example, if your Oracle release is release 8.1.5 and your SID is ORCL, then enter the following at the MS-DOS command prompt:

C:\> ORADIM -DELETE -SID ORCL

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

This syntax includes the following variables:

SID

is the same SID name as the SID of the database you are upgrading.

PASSWORD

is the password for the new release 8.1 database instance. This is the password for the INTERNAL user. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.

USERS

is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.

ORACLE_HOME

is the release 8.1 Oracle home directory. Ensure that you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory.

For example, if your SID is ORCL, your PASSWORD is TWxy579, the maximum number of USERS is 10, and the ORACLE_HOME directory is C:\ORA81, then enter the following command:

C:\> ORADIM -NEW -SID ORCL -INTPWD TWxy579 -MAXUSERS 10 
     -STARTMODE AUTO -PFILE C:\ORA81\DATABASE\INITORCL.ORA

On all nodes, copy configuration files to a location outside of the old Oracle home:

If your initialization parameter file resides within the old environment's Oracle home, then copy it to a location outside of the old environment's Oracle home. By default Oracle looks for the initialization parameter file in ORACLE_HOME\DATABASE. The initialization parameter file can reside anywhere you wish, but it should not reside in the old environment's Oracle home after you upgrade to the new release.
If your initialization parameter file has an IFILE (include file) entry and the file specified in the IFILE entry resides within the old environment's Oracle home, then copy the file specified by the IFILE entry to a location outside of the old environment's Oracle home. The file specified in the IFILE entry has additional initialization parameters.
If you have a password file that resides within the old Oracle home, then move or copy the password file to the Oracle8i Oracle home. The default password file is ORACLE_HOME\DATABASE\PWDSID.ORA. Edit the file specified in the IFILE entry in the same way you edited the initialization parameter file in the previous steps a and b.
If your INITDB_NAME.ORA file resides within the old environment's Oracle home, then move or copy the INITDB_NAME.ORA file to a location outside of the old environment's Oracle home.

On all nodes, adjust the initialization parameter file for use with the new release.

Remove obsolete parameters and adjust changed parameters. Certain initialization parameters are obsolete in the new 8.1 release. Remove all obsolete parameters from any initialization parameter file that will start a new release 8.1 instance. Obsolete parameters may cause errors. Also, alter any parameter whose syntax has changed in the new 8.1 release.

See::

Oracle8i Migration guide, Appendix B, "Changes to Initialization Parameters" for lists of new, renamed, and obsolete parameters, and Oracle8i Parallel Server Concepts and Administration for more information about obsolete Oracle Parallel Server initialization parameters.

If you are updating snapshots automatically by using the JOB_QUEUE_PROCESSES initialization parameter, set JOB_QUEUE_PROCESSES to 0 (zero) during upgrading. Also, if you are using Advanced Queuing and have propagation schedules, then set both the JOB_QUEUE_PROCESSES and AQ_TM_PROCESSES initialization parameters to 0. After upgrading your database, you can reset it to use these parameters.
If the initialization parameter file contains an IFILE entry, then change the IFILE entry in the initialization parameter file to point to the new location you copied it.
Modify the INITDB_NAME.ORA file in the same way that you modified the initialization parameter file.

Make sure you save all of the files you modified after making these adjustments.

Set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete.

At the MS-DOS command prompt, change to the ORACLE_HOME\RDBMS\ADMIN directory.
Start Server Manager and connect to the database instance as INTERNAL user.

C:> SVRMGRL
SVRMGR> CONNECT INTERNAL

Run STARTUP RESTRICT:

SVRMGR> STARTUP RESTRICT

You may need to use the PFILE option to specify the location of your initialization parameter file.

You may see error messages listing obsolete initialization parameters. If so, then make a note of the obsolete initialization parameters and continue with the upgrade normally. Then, remove the obsolete initialization parameters the next time you shut down the database (Step 14).

Set the system to spool results to a log file for later verification of success:

SVRMGR> SPOOL CATOUTU.LOG

If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement:

SVRMGR> SET ECHO ON

Run UOLD_RELEASE.SQL where OLD_RELEASE refers to the release you had installed prior to upgrading. See the table below to choose the correct script. Each script provides a direct upgrade from the release specified in the "Old Release" column. The "Old Release" is the release from which you are upgrading.

To run a script, enter the following:

SVRMGR> @UOLD_RELEASE.SQL

See:

Oracle8i Migration guide,"Upgrade Paths" for more information on the upgrade paths and scripts.


Old Release	Run Script
8.0.1	Direct upgrade is not supported.
8.0.2	Direct upgrade is not supported.
8.0.3	`U0800030.SQL`
8.0.4	`U0800040.SQL`
8.0.4S	Direct upgrade is not supported.
8.0.5	`U0800050.SQL`
8.0.6	`U0800060.SQL`
8.1.1	Upgrading to the new release is not supported.
8.1.2	Upgrading to the new release is not supported.
8.1.3	Direct upgrade is not supported.
8.1.4	Direct upgrade is not supported.
8.1.5	U0801050.SQL

Note:

If the old release you had installed prior to upgrading is not listed, see the README files in the new installation for the correct upgrade script to run.

Make sure you follow these guidelines when you run the script:

You must use the version of the script supplied with new release 8.1 installation.
You must run the script in the new release 8.1 environment.
You only need to run ONE script, even if your upgrade spans several releases. For example, if your old release was 8.0.4, then you need to run only U0800040.SQL.

The script you run creates and alters certain dictionary tables. It also runs the CATALOG.SQL and CATPROC.SQL scripts that come with the release to which you are upgrading, which create the system catalog views and all the necessary packages for using PL/SQL.

If you encounter any problems when you run the script, or any of the scripts in the remaining steps, then correct the causes of the problems and rerun the script. You can rerun any of the scripts described in this chapter as many times as necessary.

See:

Oracle8i Migration guide, "Running Scripts" for information about the types of errors to look for when you run a script.

You may encounter a series of messages similar to the following during the upgrade:

ORA-00604: error occurred at eecursive SQL level 1
ORA-00001: unique constraint (SYSTEM.AQ$_QUEUES_CHECK) violated
ORA-06512: at "SYS.DBMS_AQADM", line 2023
ORA-06512: at line 2

You can ignore these messages.

Run CATPARR.SQL:

SVRMGR> @CATPARR.SQL

Set the PARALLEL_SERVER initialization parameter to TRUE.
Turn off the spooling of script results to the log file:

SVRMGR> SPOOL OFF

Then, check the spool file and verify that the packages and procedures compiled successfully. You named the spool file CATOUTU.LOG. Correct any problems you find in this file.

If you specified SET ECHO ON, then you may want to SET ECHO OFF now:

SVRMGR> SET ECHO OFF

Run SHUTDOWN on the Oracle8i database:

SVRMGR> SHUTDOWN IMMEDIATE

Caution:

Use SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE. Do not use SHUTDOWN ABORT.

Also, if you encountered a message listing obsolete initialization parameters when you started the database in Step 8, then remove the obsolete initialization parameters from the initialization parameter file now.

Your database and Oracle Parallel Server are now upgraded to the new 8.1 release.

Caution:

If you retain the old Oracle software, then never start the upgraded database with the old software. Only start the database with the executables in the new release 8.1 installation directory. Also, before you remove the old Oracle environment, make sure you relocate any data files in that environment to the new Oracle8i environment. See the Oracle8i Administrator's Guide for information about relocating data files.

Perform Post-Oracle8i Upgrade Steps

Perform the following steps to complete the upgrade for Oracle Parallel Server:

On the node from which you ran the upgrade scripts:

Stop the OracleCMService and the OracleServiceSID services:

1. Double-click the Services icon in the Control Panel window. The Services dialog box appears.

2. Select an Oracle8i service.

3. Click Stop.

4. Click Close to dismiss Services dialog box.

Set the Oracle home path to the new Oracle8i Oracle home path with a tool such as the Oracle Home Selector:

Choose Start > Programs > Oracle Installation Products > Oracle Home Selector.
Select the Oracle8i home from the drop-down list.

See::

To upgrade additional components, such as Java and the Advanced Queuing (AQ) option, see "Upgrading Specific Components" in Oracle8i Migration guide.

Perform Post-Upgrade Tasks

Complete the post-upgrade procedures listed in the table below. These are described in the Oracle8i Migration guide, Chapter 8, "After Migrating or Upgrading the Database".

Post-Upgrade Tasks Additional Task Performed after Upgrading from Version 8.0 or Version 8.1

Perform a complete backup of the production database.

Change the password for the OUTLN user.

Copy LONGs to LOBs.

Check for bad date constraints.

Adjust the initialization parameters SHARED_POOL_SIZE and LARGE_POOL_SIZE in your initialization parameter file to avoid problems with parallel execution.

If you installed the Java option, install ODCI.JAR AND CARTRIDGESERVICES.JAR files.

Modify your LISTENER.ORA file.

Migrate or upgrade your standby database to Oracle Release 8.1.

Add new features as appropriate. It is not necessary to make any immediate changes to begin using your Oracle8i database. You may prefer to introduce these enhancements into your database and corresponding applications gradually.

Develop new administrative procedures as needed.

Adjust your initialization parameter file for the new release.

Normalize filenames.

Rebuild unusable function-based indexes.

Multiple Oracle Homes

Oracle Parallel Server for Windows NT supports multiple Oracle homes, but all the Oracle homes must contain the same release of the Oracle8i Enterprise Edition and Oracle Parallel Server.

Windows NT requires that each node have only one copy of the vendor-supplied Operating System Dependent layer active.

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 database instance. This is the password for INTERNAL user. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.
USERS	is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.
ORACLE_HOME	is the release 8.1 Oracle home directory. Ensure that you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory.

Initialization Parameter	Change Setting To
BACKGROUND_DUMP_DEST	`ORACLE_BASE\ORADATA\DB_NAME`
USER_DUMP_DEST	`ORACLE_BASE\ORADATA\DB_NAME\ARCHIVE`

Oracle Release...	Enter at the MS-DOS Command Line...
8.0	`C:\> ORADIM80 -DELETE -SID SID`
8.1	`C:\> ORADIM -DELETE -SID SID`

SID	is the same SID name as the SID of the database you are upgrading.
PASSWORD	is the password for the new release 8.1 database instance. This is the password for the INTERNAL user. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.
USERS	is the maximum number of users who can be granted SYSDBA and SYSOPER privileges.
ORACLE_HOME	is the release 8.1 Oracle home directory. Ensure that you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory.

2 Migrating or Upgrading to Release 8.1

New Features in Release 8.1

Rolling Upgrades

Migrating from Oracle7

Prepare the Oracle7 Source Database for Migration

Prepare the Cluster for Installation

Install the Release 8.1 Oracle8i Enterprise Edition

Perform Post-Installation Steps

Migrate the Oracle7 Source Database

Run the Migration Utility

Check the Migration Results

Preserve the Oracle7 Source Database

Perform Post-Oracle7 Migration Steps

Perform Migration Steps in the Oracle8i Environment

Perform Post-Migration Tasks

Upgrading the Previous Version 8 Database to the New Oracle8i Release

Prepare to Upgrade

Prepare the Cluster for Upgrade

Install Release 8.1 Oracle8i Enterprise Edition

Perform Post-Installation Steps

Upgrade the Database Manually

Perform Post-Oracle8i Upgrade Steps

Perform Post-Upgrade Tasks

Multiple Oracle Homes

2
Migrating or Upgrading to Release 8.1