2
Migrating or Upgrading to Release 8.1
This chapter details the required steps for migrating or
upgrading to Release 8.1. Specific topics include:
Migrating
or Upgrading to Release 8.1
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 Migrate an
Existing Database check box, as the Oracle Data Migration Assistant
does not support Oracle Parallel Server. Instead, use the Migration utility
to migrate or upgrade after installation, as described in the Oracle8i
Migration guide.
In addition to the procedures in the Oracle8i
Migration guide, perform these tasks
Additional
Migration Steps
This section covers the following Windows NT-specific instructions
for Oracle Parallel Server migrations.
Pre-Installation
Steps
Prior to installing the release 8.1 Oracle8i Enterprise
Edition software, as described in "Install the Release 8.1 Oracle Software"
in Chapter 3, "Migrating Using the Migration Utility" of the Oracle8i
Migration guide, the following must be performed:
-
The Oracle7 database, Oracle7 services and version
7 OSD layer must be shut down.
-
The release 8.1 OSD layer must be installed and started.
To ready 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.
SHUTDOWN IMMEDIATE
-
Ensure all Oracle7 services are shut down, including
the OraclePGMSService 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 the OraclePGMSService service to Manual startup:
-
Double-click the OraclePGMSService service.
-
The Service dialog box appears.
-
Click Manual in the Startup Type group box.
-
Click OK to dismiss the Service dialog box.
-
Click Close in the Services dialog box.
-
Shut down 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.
OSD73 will act as a temporary storage for the version
7 OSD layer, which will be used later in migration process.
-
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.
Post-Installation
Steps
After installing the release 8.1 software, as described in
"Install the Release 8.1 Oracle Software" in Chapter 3, "Migrating Using
the Migration Utility" of the Oracle8i
Migration guide, the following must be performed:
-
The version 8.1 OSD layer must be shut down.
-
The version 7 OSD layer and Oracle7 services must
be started in order to perform migration steps on the Oracle7 database.
To ready the cluster for the Oracle7 migration process, perform
the following steps:
-
Shut down the release 8.1 OSD layer on each node
in the cluster, as described in your vendor documentation.
-
Perform the following steps on the node from which
you intend to run the Migration Utility:
a. Rename the
OSD key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD81 using the Save
Subtree As option under the File menu.
OSD81 will act as a temporary storage for the release
8.1 OSD layer while the Oracle7 database is being migrated.
b. Rename the
OSD73 key under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD using the Save
Subtree As option under the File menu.
c. Start the version 7
OSD layer, as described in your vendor documentation.
d. Start the OraclePGMSService
and the OracleService
SID 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.
e. Set the Oracle home
path to the Oracle7 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 Oracle7 home from the drop-down list.
Post Oracle7
Migration Steps
After running the Migration utility in Oracle7 environment,
as described in "Migration Steps in the Oracle7 Environment" in Chapter
3, "Migrating Using the Migration Utility" of the Oracle8i
Migration guide, the following must be performed:
-
The version 7 services and version 7 OSD layer must
be shut down and de-activated.
-
The release 8.1 services must be created.
To ready the cluster for the Oracle8i migration process,
perform the following steps:
-
Perform the following steps on the node from which
you ran the Migration Utility:
a. Stop the OraclePGMSService
and the OracleService
SID services:
1. Double-click the Services icon in the Control Panel
window. The Services dialog box appears.
2. Select an Oracle service.
3. Click Stop.
4. Click Close to dismiss Services dialog box.
b. Stop the version 7 OSD
layer, as described in your vendor documentation.
c. Rename the OSD key under
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE to OSD73 using the Save Subtree As option
under the File menu.
This effectively disables the version 7 OSD layer.
d. 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.
e. Set the Oracle home
path to the Oracle8
i 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.
From the Oracle7 Oracle home command line, enter:
C:> CD ORACLE7_HOME/BIN
ORADIM73 -DELETE - SID SID
-
Create an Oracle8i OracleServiceSID
service for each instance
C:> ORADIM -NEW -SID SID -INTPWD INTERNAL_PWD
Oracle8i
Migration Steps
Prior to starting the database, as described in "Migration
Steps in the Oracle8i Environment" in Chapter 3, "Migrating Using
the Migration Utility" of the Oracle8i
Migration guide, set the PARALLEL_SERVER parameter to FALSE in
the INITSID.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 node, which is required to run
the Oracle8i migration scripts.
After the migration is complete, set the PARALLEL_SERVER
parameter back to TRUE.
Additional
Upgrade Steps
This section covers the following Windows NT-specific instructions
for Oracle Parallel Server upgrades.
Pre-Installation
Steps
Prior to installing the release 8.1 Oracle8i Enterprise
Edition software, as described in "Upgrade the Database Manually" in Chapter
7, "Upgrading to the New Oracle8i Release" of the Oracle8i
Migration guide, the following must be performed:
-
The Oracle7 database, Oracle7 services and version
7 OSD layer must be shut down.
-
The release 8.1 OSD layer must be installed and started.
To ready 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.
SHUTDOWN IMMEDIATE
-
Ensure all Oracle7 services are shut down, including
the OraclePGMSService service:
-
Double-click the Services icon in the Control
Panel window.
The Services dialog box appears.
-
Select an Oracle service.
-
Click Stop to stop the service.
-
Disable the OraclePGMSService service:
-
Double-click the OraclePGMSService service.
-
The Service dialog box appears.
-
Click Disabled in the Startup Type group box.
-
Click OK to dismiss the Service dialog box.
-
Click Close in the Services dialog box.
-
Shut down the version 7 OSD layer, as described in
your vendor documentation.
-
Delete the Oracle7 OracleServiceSID service.
From the Oracle7 Oracle home command line, enter:
C:> CD ORACLE7_HOME/BIN
ORADIM73 -DELETE - SID SID
-
Backup the database raw partitions.
-
Install the version 8.1 OSD layer, as described in
your vendor documentation.
-
Start the version 8.1 OSD layer, as described in
your vendor documentation.
Post-Installation
Steps
Prior to starting database and running the upgrade scripts,
as described in "Upgrade the Database Manually" in Chapter 7, "Upgrading
to the New Oracle8i Release" of the Oracle8i
Migration guide, the following must be performed:
-
The release 8.1 services must be created.
-
The database must be started in exclusive mode.
To ready the cluster for the Oracle8i upgrade process,
perform the following steps:
-
Continue to use the logical partition links used
for release 8.0. There should not be a need to modify the *.TBL file or
re-rerun the SETLINKS utility.
-
Create an Oracle8i OracleServiceSID
service for each instance in the cluster:
C:> ORADIM -NEW -SID SID -INTPWD INTERNAL_PWD
-
On the node from which you intend to run the upgrade
scripts, set the PARALLEL_SERVER parameter to FALSE in the INITSID.ORA
file. Setting this parameter to FALSE ensures the database will be started
in exclusive node, which is required to run the Oracle8i upgrade
scripts.
After the migration is complete, set the PARALLEL_SERVER
parameter back to TRUE
Coexistence
and Rolling Upgrades
Coexistence of different versions of the Oracle Parallel
Server database is not supported
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.
Multiple
Oracle Homes
The Oracle Parallel Server Option on Windows NT supports
multiple Oracle homes, but all the Oracle homes must contain the same release
of the Oracle8i Enterprise Edition and the Oracle Parallel Server
Option.
Windows NT requires that each node have only one copy of
the vendor-supplied Operating System Dependent layer active.