Professional Documents
Culture Documents
Guide Ux Ora Upgrade To 10g
Guide Ux Ora Upgrade To 10g
PUBLIC
.S"n,*
% qc$ ;jhsy{Sz j>+G
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location:
http://service.sap.com/instguides Database Upgrades Oracle
The following table provides an overview of the most important document changes.
Version
Date
Description
3.0
2.11
2009-08-25
2007-02-21
2.1
2006-08-28
2.0
2006-08-01
Major update
Error correction in section Disabling Database User Locking Mechanism For Failed Logins:
command line connect / as sysdba inserted
Various changes including new section Disabling Database User Locking Mechanism for
Failed Logins
Various changes including new section Installing Oracle Critical Patch Updates
2/48
PUBLIC
2009-08-25
Table of Contents
Chapter 1
1.1
1.2
1.3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
2.1
2.2
2.3
2.4
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Checking the Original Version of Your Database . . . . . . . . . . . . . . . . . . . . . . . . 9
Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 10
Reviewing the Oracle-Specified Kernel Parameters and Shell
Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 11
Chapter 3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Correct UNIX Users, Groups, and Authorizations . . . . . . . . . . .
Checking the Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Pre-Upgrade Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Prerequisites for the Oracle Universal Installer . . . . . . . . . . . . .
Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating to Automatic Undo Management . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping Statspack Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the SYSTEM and SYSAUX Tablespace for Freespace . . . . . . . . . . . .
Checking for Invalid Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Oracle Instant Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
15
16
17
18
18
19
19
20
Chapter 4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
21
21
22
23
24
24
26
27
2009-08-25
PUBLIC
5
6
6
7
3/48
4.1.7
4.1.8
4.1.9
4.2
4.2.1
4.2.2
27
28
29
29
29
30
Chapter 5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finalizing the Environment of the ora<dbsid>User . . . . . . . . . . . . . . . . . . . .
Checking the Upgraded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Oracle Critical Patch Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the oratab Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Listener Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Renaming the Old $ORACLE_HOME/bin Directory . . . . . . . . . . . . . . . . . . . .
Checking the Read Authorization of the <sapsid>adm User . . . . . . . . . . . . .
Changing the Environment for the <sapsid>adm user . . . . . . . . . . . . . . . . . .
Checking SAP Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Location of the JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling Database User Locking Mechanism For Failed Logins . . . . . . . . . . . .
Checking the National Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the New Features for Oracle Database 10g Release 2
(10.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
33
34
35
36
36
38
38
39
39
40
40
40
41
43
43
43
4/48
PUBLIC
44
2009-08-25
Introduction
1 Introduction
This documentation explains how to upgrade the Oracle database for the SAP system on the UNIX
operating system:
z From Oracle version 9.2.0 or Oracle Database 10g Release 1 (10.1.0.4)
z To Oracle Database 10g Release 2 (10.2)
CAUTION
SAP certifies Oracle 10.2 only from release 10.2.0.2. SAP does not certify nor support Oracle
10.2.0.1.
Make sure that your target release is Oracle 10.2.0.2 or later.
This documentation only covers the upgrade from Oracle 9.2.0.4 or later including Oracle 10.1.0.4
to Oracle Database 10g Release 2 (10.2).
NOTE
Oracle offers and supports direct database upgrades from Oracle 8.1.7 to Oracle 10.2 although we
do not recommend this.
We do not describe direct upgrades in this documentation. SAP has not tested and validated the
direct upgrade path from Oracle 8.1.7 to Oracle 10.2. If you intend to perform a direct upgrade
from Oracle 8.1.7 to Oracle 10.2, see the Oracle Database 10g Release 2 (10.2) upgrade
documentation.
You can obtain the Oracle documentation at the Oracle Technology Network (OTN) website.
You use the tools Oracle Universal Installer (OUI), Oracle SQL*Plus, and Oracle Database Upgrade
Assistant (DBUA) to perform the upgrade.
CAUTION
Make sure you have the latest version of this document. You can always find this as follows:
http://service.sap.com/instguides Database Upgrades Oracle .
NOTE
In this document we use <DBSID> for the database instance identifier and <SAPSID> for the SAP
system identifier. These can be different if your:
z Database system uses Oracle Real Application Cluster (RAC)
z SAP system uses Multiple Components in One Database (MCOD) Implementation
Considerations
2009-08-25
PUBLIC
5/48
Introduction
1.1
New Features
Implementation Considerations
lZd& For more information about implementation considerations, including the most important SAP
Notes for the upgrade, see Planning [page 9].
lZd& Be sure to read the relevant SAP Notes before beginning the upgrade. These notes contain the most
recent information about the upgrade, as well as corrections to the documentation. You can find
the most recent version of the SAP Notes at http://service.sap.com/notes
lZd& Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for
Oracle Database 10g Release 2 (10.2).
We recommend that you check the most important new features in the Oracle documentation
since some new features might affect the operation of your production system.
Title
Remarks
819830
720886
828268
830576
841728
839187
6/48
PUBLIC
2009-08-25
Introduction
1.3
Number
Title
Remarks
871735
871096
1137346
850306
134592
834917
819829
839182
306408
868681
Internet Address
Title
SAP Notes
Oracle Database
Administration
http://service.sap.com/notes
None
SAP Database Guide: Oracle
SAP Software
Distribution Center
Oracle Database Upgrade
Guide
that is, the guide you are
now reading
Oracle upgrade
documentation in Oracle
Metalink or My Oracle
Support
2009-08-25
www.sdn.sap.com/irj/sdn/
SAP ON ORACLE
KNOWLEDGE CENTER
Documentation
ora
SAP
http://service.sap.com/swdc
http://service.sap.com/
instguides
None
Upgrade to Oracle Database <Version>: UNIX
Database Upgrades
Oracle
http://download.oracle.com
/docs/cd/B19306_01/server.
102/b14238/toc.htm
http://metalink.oracle.com
PUBLIC
7/48
Introduction
1.3
Description
Oracle Technology
Network (OTN) forum
Internet Address
Title
http://forums.oracle.com/
forums/forum.jspa?
forumID=583&start=0
8/48
PUBLIC
2009-08-25
Planning
2.1
2 Planning
RECOMMENDATION
Before the production upgrade, make sure that you perform a test upgrade on your backup system,
either with database upgrade assistant (DBUA) (recommended) or manually.
1.
2.
3.
4.
This SAP upgrade documentation only covers the standard upgrade from Oracle 9.2.0.4 or later
to Oracle Database 10g Release 2 (10.2) using the Oracle Database Upgrade Assistant (DBUA).
Process
If the source database is Oracle 10.1 we strongly recommend that it is at least version Oracle 10.1.0.4.
2009-08-25
PUBLIC
9/48
Planning
2.2
To make sure that the checks complete successfully, you must complete this procedure before
running the Oracle Universal Installer [page 24].
Prerequisites
You can access the complete Oracle documentation referred to below as a member of the Oracle
Technology Network (OTN).
Procedure
1.
2.
3.
If you have access to Oracle Metalink we strongly recommend that you read document
169706.1. This document provides information on all operating system prerequisites and is
regularly updated.
Obtain the full and updated list of hardware and software requirements from the relevant Oracle
database installation guide for your operating system, which you can find at the Oracle website.
Select the appropriate documentation for Oracle Database 10g Release 2 (10.2).
CAUTION
If your database resides on Network Attached Storage (NAS) you need to review and
implement the Oracle NAS guidelines. You need to mount network file systems with specific
mount options, which you can find in the Oracle installation guide.
10/48
PUBLIC
2009-08-25
Planning
2.3
Obtain the recommended shell limits and kernel parameters from the relevant Oracle database
installation guide for your operating system, which you can find at:
www.oracle.com/technology/documentation
Select the appropriate documentation for Oracle Database 10g Release 2 (10.2).
1.
Make sure you have read the SAP Notes for the upgrade [page 6], which you can find at
http://service.sap.com/notes
2.
3.
Make sure your operating system and initial database version meets SAP requirements. We approve
specific combinations of operating system version, database version, SAP release, and SAP kernel
release:
k SAP Release 4.6x, see SAP Note 156548
k SAP Release 6.x, see SAP Note 407314
To upgrade from a remote PC, you need X-Windows software on the PC, as described in SAP
Note 432861.
RECOMMENDATION
4.
In some situations the OUI and DBUA screens are not displayed correctly when started
remotely. In such cases we recommend you to start the OUI and the DBUA directly from the
console.
Download the Oracle Database 10g Release 2 (10.2) installation guide for your operating system
from the Oracle Technology Network (OTN).
You need this document to review the hardware and software requirements and to configure the
kernel parameters and shell limits.
2009-08-25
PUBLIC
11/48
Planning
2.4
5.
If you have access to Oracle Metalink we strongly recommend that you read document
169706.1. This document provides information on all operating system prerequisites and is
regularly updated.
Download the Oracle Database 10g Release 2 (10.2) software and the latest patch sets and required
patches or patch collection.
The list of patches is described in SAP Notes 1137346 and 1137346. You can download the patches
from:
http://service.sap.com/swcenter-3pmain
CAUTION
6.
P% The patches listed in SAP Note 1137346 are mandatory. To avoid severe database
problems, make sure that you install all these patches.
P% SAP certifies Oracle 10.2 only from release 10.2.0.2. SAP does not certify nor support
Oracle 10.2.0.1.
Make sure that your target release is Oracle 10.2.0.2 or later.
Download the latest version of the Oracle 10.2 Instant Client software from:
http://service.sap.com/swcenter-3pmain
7.
Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the
database upgrade from:
http://service.sap.com/swdc
12/48
PUBLIC
2009-08-25
Preparation
3.1
3 Preparation
1.
If the user ora<dbsid> does not have write authorization, log on to your system with the user
root and enter the command:
chgrp dba /oracle
chmod 775 /oracle
2.
Check if you are able to start an XTERM as the Oracle user since this is the user who starts the
OUI.
Enter the following command with the user ora<dbsid>:
umask 022
2009-08-25
PUBLIC
13/48
Preparation
3.2
1.
After you have finished the extraction of all the RDBMS CDs, the following subdirectories
exist under /oracle/stage/102_64:
^5
^5
^5
^5
^5
database
client
clusterware
companion
gateways
NOTE
4.
14/48
For some platforms Disk1 and Disk2 might be created as subdirectories of database,
client, clusterware, companion, and gateways.
The gateways subdirectory is not created for the following platforms:
^5 Linux on Power
^5 HP_UX on Itanium
^5 Solaris x86_64
After extraction of the Oracle software to /oracle/stage/102_64 do the following:
1. Rename the original SAP folder by performing one of the following:
PUBLIC
2009-08-25
Preparation
3.3
8*
mv /oracle/stage/102_64/database/SAP /oracle/stage/102_64/database/
SAP_ORIG
8*
mv /oracle/stage/102_64/database//Disk1/SAP /oracle/stage/102_64/
database//Disk1/SAP_ORIG
2.
3.
Download the file RDBMS_SAP_32.zip (for 32-bit platforms) or RDBMS_SAP_64.zip (for 64bit platforms) attached to SAP Note 819830 and copy it to a temporary location such
as /tmp.
Extract the zip file by performing one of the following for 64-bit platforms (replace 64
with 32 for 32-bit platforms):
8*
cd /oracle/stage/102_64/database
unzip /tmp/RDBMS_SAP_64.zip
8*
cd /oracle/stage/102_64/database/Disk1
unzip /tmp/RDBMS_SAP_64.zip
2.
You now see the directory SAP extracted with the updated version of SAP-specific files.
Check the Oracle inventory directory.
The Oracle inventory directory maintains the inventory of all Oracle software installed on the
system. The path to the Oracle inventory directory is mentioned in the file oraInst.loc, which
you can find under /var/opt/oracle or under /etc.
One of the entries of oraInst.loc or inventory_location points to the location of the Oracle
inventory. When you execute the OUI for the first time on the system, the OUI prompts you for
the path to the inventory directory. The default location for the Oracle inventory is $ORACLE_BASE/
oraInventory.
NOTE
3.
This applies only to systems where the OUI has been executed for the first time. The OUI
automatically creates theoraInst.loc and the inventory directory. You do not need to create
these directories manually.
Create the empty Oracle home directory before starting the OUI.
You need to create the Oracle home directory before you can start the Oracle software installation.
The Oracle Home directory is normally /oracle/<DBSID>/102_64.
You always execute this script as the ora<dbsid> user connected to the database as sysdba in the
Oracle 9i environment.
2009-08-25
PUBLIC
15/48
Preparation
3.4
Prerequisites
You are logged on as user ora<dbsid> in the Oracle 9i environment with the database also started up.
For more information about how to extract the script from the Oracle 10.2.0.4 patchset software without
installing the patchset software, see SAP Note 1237838.
Procedure
or:
SQL> @/oracle/stage/102_64/database/Disk1/SAP/utlu102i.sql
SQL> spool off
SQL> exit
Result
You can check the results of the pre-upgrade script by looking at the log file /tmp/pre_upgrade.log.
CAUTION
Make the changes listed in the log file, otherwise you might have problems during the upgrade.
If the log file from the pre-upgrade script reports stale optimizer statistics for the Oracle 9.2 database,
you need to execute the script gather_optimizer_statistics.sql attached to SAP Note 819830. This
applies only to the Oracle 9.2 database.
1.
2.
16/48
PUBLIC
2009-08-25
Preparation
3.5
x
cd /oracle/stage/102_64/database/Disk1
./runInstaller executeSysPrereqs
If the OUI complains that the operating system version is not certified or supported, you can ignore
this.
If OUI reports missing OS patches, you need to apply these before you can continue.
1.
Download the latest version of dbsl (dboraslib.so, dboraslib.sl, or dboraslib.o) for your
release from:
http://service.sap.com/swdc
2.
Check the level of your Basis support package using this table:
SAP Release (SAP_BASIS)
46B
46C
46D
6.10
6.20
6.40
SAPKB46B57
SAPKB46C48
SAPKB46D38
SAPKB61041
SAPKB62044
SAPKB64009
xx If the level of your Basis support package is higher than or equal to that shown above, no
additional corrections are necessary.
xx If the level of your Basis support package is lower than the one shown in the table above, you
need to apply an additional transport correction to your system as described in SAP Note
868681.
2009-08-25
PUBLIC
17/48
Preparation
3.6
3.
Download the latest version of the Oracle Client software OCL92064.SAR or OCL92032.SAR
from:
http://service.sap.com/swcenter-3pmain
4.
If you cannot update the client software because there are several other application servers
running on the same host, see SAP Note 964783.
Execute the SQL script sapconn_role.sql as follows:
cp /oracle/stage/102_64/database/SAP/sapconn_role.sql $ORACLE_HOME/dbs
or:
cp /oracle/stage/102_64/database/Disk1/SAP/sapconn_role.sql $ORACLE_HOME/dbs
cd $ORACLE_HOME/dbs
sqlplus /nolog @sapconn_role
1.
2.
Read SAP Note 600141, which is the central note describing automatic undo management. This
note also gives you an overview of the concepts involved.
Follow the step-by-step instructions in the note to migrate to automatic undo management.
This step is only relevant if the Statspack package has been activated on the database for monitoring
purposes. For more information about Statspack, see SAP Note 717484.
Procedure
1.
Log on as the user under which the statspack jobs run (usually PERFSTAT):
18/48
PUBLIC
2009-08-25
Preparation
3.8
2.
This displays a list of the jobs that are currently entered under the user PERFSTAT.
Delete all jobs with the print job number <jobnr>:
SQL> connect PERFSTAT/<pwd>
SQL> execute dbms_job.remove( <jobnr> );
The SYSAUX tablespace is available only if the source database is already Oracle 10.1.
If your source database is Oracle 9.2, there is no SYSAUX tablespace. In this case, you can ignore
references to the SYSAUX tablespace in this section.
Procedure
For systems that use raw devices for the datafiles, the AUTOEXTEND option might not work
because of the fixed size of the raw devices. In this case you might need to add another datafile
by adding a new volume or partition on the operating system.
2009-08-25
PUBLIC
19/48
Preparation
3.10
Procedure
1.
2.
If there is a table called PLAN_TABLE either in the SYS or SYSTEM schema, you must drop it with
the following commands before starting the database upgrade:
SQL> drop table "SYS"."PLAN_TABLE";
SQL> drop table "SYSTEM"."PLAN_TABLE";
Install the Oracle Database 10g Instant Client for UNIX as described in SAP Note 819829.
20/48
PUBLIC
2009-08-25
4.1
You have completed the upgrade. Now perform the post-upgrade steps [page 21].
You can upgrade the database software while the SAP system is still running with the existing
database (that is, Oracle 8.1.7 or Oracle 9.2). Therefore, to reduce downtime you can perform the
following steps before you stop your system. The exception to this is for AIX where you need to
run an additional script as the root user, as described in Adapting the AIX Kernel (AIX only) [page
24]. You need to shut down all Oracle instances on the host before running this script.
Process Flow
1.
2.
3.
You perform steps for the AIX operating system [page 24].
G} G/*EVNt
4.
5.
6.
7.
2009-08-25
PUBLIC
21/48
4.1
8.
9.
For more information about changes to the environment of the SAP user <sapsid>adm, see Changing
the Environment for the <sapsid>adm User [page 40].
Prerequisites
You set the environment variables below by editing the files .dbenv_<host>.sh
and .dbenv_<host>.csh in the home directory of ora<dbsid>.
CAUTION
Do not make the changes to the environment permanent as long as the old database is still
running. You make them permanent in the post-upgrade phase. We recommend you to back up
the old environment files before making the changes permanent.
Procedure
1.
2.
;|ua TWO_TASK
;|ua ORA_NLS
;|ua ORA_NLS32
;|ua ORA_NLS33
Set the following environment variables:
Environment Variable
Value
DISPLAY
<hostname>:0.0
NOTE
<hostname>:0.0 is the host on which the
Oracle Universal Installer (OUI) is to be
displayed.
ORACLE_BASE
/oracle
ORACLE_SID
<DBSID>
ORACLE_HOME
NLS_LANG
22/48
PUBLIC
2009-08-25
4.1
Value
/oracle/stage/102_64/database/Disk1/SAP
or
/oracle/stage/102_64/database/SAP
NOTE
$ORACLE_HOME/nls/data
SAPDATA_HOME
/oracle/<DBSID>
The setting of the DISPLAY environment variable is described in SAP Note 432861.
To make sure that the OUI screen can be displayed correctly on your system, you might have to
start an X terminal (xterm) session and run the command:
$ xhost +
3.
4.
Environment Variable
Value
AIX
Solaris, HP Tru64 UNIX, Linux
HP-UX
LIBPATH
$ORACLE_HOME/lib:$LIBPATH
LD_LIBRARY_PATH
$ORACLE_HOME/lib:$LD_LIBRARY_PATH
SHLIB_PATH
$ORACLE_HOME/lib:$SHLIB_PATH
This makes sure that dynamic libraries are loaded first from $ORACLE_HOME/lib.
Include $ORACLE_HOME/bin in your PATH or path variable, where $ORACLE_HOME is the variable that
you set in step 2 above.
NOTE
5.
Make sure there is only one $ORACLE_HOME/bin in your PATH or path variable. Make sure that
the path variable does not contain the old $ORACLE_HOME/bin.
Check if the temporary directory (usually /tmp) has at least 400 MB of free space. If not, set up the
TEMP or TMPDIR environment variables to specify a temporary directory on the filesystem.
RECOMMENDATION
You can check the correctness of the new environment with the UNIX env command. Or you
can run the UNIX umask command and check that the returned value is 22.
1.
If the Oracle inventory exists, check its location by looking at the entry in one of the following
files:
2009-08-25
PUBLIC
23/48
4.1
NTeZ /var/opt/oracle/oraInst.loc
NTeZ /etc/oraInst.loc
The location is shown as follows:
inventory_loc=<path to Oracle inventory>
2.
Make a backup of your existing Oracle inventory before you start the Oracle Database 10g Release
2 (10.2) software installation.
NT[Z('s-<"DkKL1?r<lzA
If several Oracle instances run on one computer, you must shut these down before adapting the kernel.
Procedure
1.
3.
Make sure that the user root is assigned the environment of ora<dbsid>:
su root
4.
5.
2.
Remove any currently unused modules in kernel and library memory by entering the following
command as user root:
# /usr/sbin/slibclean
NT[Rq7sa"iK_
1.
24/48
PUBLIC
2009-08-25
4.1
2.
3.
Since you are already logged on as user root, you can switch to user ora<dbsid> by entering the
following command:
su ora<dbsid>.
If you install Oracle database software with Release 10.2.0.1 or 10.2.0.x on a new operating system
or a new operating system version, the Oracle Universal Installer might not yet recognize or support
this operating system. Follow the instructions in SAP Note 980426.
Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where
<host_name> is the host on which you want to display the GUI of the Oracle Universal Installer
(OUI).
Shell Used
Command
DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh)
Korn shell (ksh)
4.
Cy9
cd /oracle/stage/102_64/database/SAP
./RUNINSTALLER
5.
You see a message that a response file is being generated. It might take several minutes before you
see the OUI screen.
Respond to the OUI as follows:
Prompt or Condition
Action
When you run the OUI for the first time on this host,
a dialog box, Specify File Locations Destination..., appears.
This dialog box proposes the inventory location as /
oracle/oraInventory and the installation group as
dba.
Available Product Components
Product-Specific Prerequisite Checks
This phase checks if all necessary requirements for
installing and running the database have been met.
2009-08-25
PUBLIC
25/48
4.1
Action
Summary page
6.
7.
At the end of the installation, in case there are any Configuration Assistants that have been started
automatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant. You
can ignore messages that some of the config assistants failed to complete successfully.
The Installer finishes, reporting that the Oracle installation was successful. It also informs you
about the services that it started. You can find the port numbers for these services in the
$ORACLE_HOME/install/portlist.ini file.
To exit the OUI, choose Exit and confirm the dialog box that appears.
NOTE
You can now access the Oracle 10.2 online documentation, which was installed during the
last step. You can find the entry point to the Oracle online documentation at $ORACLE_BASE/
doc/index.htm.
eE For more information on the latest patch set available for Oracle 10.2 see SAP Note 839187.
eE For more information about how to install the patch set, see the patch set README file.
CAUTION
Do not perform any of the post-installation steps mentioned in the patch set README file. The
post-installation steps are to be performed only on an existing Oracle 10.2 database.
At this stage you have only installed the Oracle 10.2 software. The database itself is still not
Oracle 10.2. Therefore, make sure that you do not perform the post-installation steps
mentioned in the README file.
eE You only have to install the latest (that is, the current) patch set.
Procedure
1.
26/48
PUBLIC
2009-08-25
4.1
2.
Install the patch set as described on the patch set README file.
For more information, see SAP Note 839187.
You can install all the required interim patches in a single step using the Oracle tool MOPatch,
which you can find at SAP Note 1027012.
MOPatch can also download patches directly from SAP Service Marketplace and check for any
potential patch conflicts.
Prerequisites
k#Vg Make sure you have already installed the current patch set [page 26].
k#Vg Check SAP Notes 871096 and 1137346 to find the list of required patches to be installed.
k#Vg Check SAP Note 839182 for instructions on how to use OPatch.
Procedure
1.
2.
3.
This command lists all the patches that have been applied to the software installation.
1.
2.
2009-08-25
PUBLIC
27/48
4.1
1.
3.
4.
Choose a new location for the new SQL*Net parameter files and set TNS_ADMIN to point to the
new location <new_TNS_ADMIN>.
2. Copy the SQL*Net parameter files from the old location <old_TNS_ADMIN> to
<new_TNS_ADMIN>.
3. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt the
value of ORACLE_HOME in the listener.ora file.
If ora<dbsid> has not set the TNS_ADMIN environment variable, Oracle first searches in /etc, in
$ORACLE_HOME/network/admin for the SQL*Net parameter files. Choose which of the following
applies to your installation:
Bcx The SQL*Net parameter files are located in directory /etc:
1. Make a backup copy of the files.
2. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt
the value of ORACLE_HOME in the listener.ora file.
Bcx The SQL*Net parameter files are located in <old_ORACLE_HOME>/network/admin:
1. Copy the SQL*Net parameter files from <old_ORACLE_HOME> to <new_ORACLE_HOME>.
2. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt
the value of ORACLE_HOME in the listener.ora file.
Since your database is still running in the old environment, do not start the listener with the new
listener.ora file at this point.
1.
Create a complete database backup and back up any archive logs from Oracle 9i.
RECOMMENDATION
Before backing up the archive logs, switch the log files with the following SQL command:
alert system switch logfile
2.
3.
Make sure that you do a log file switch for all online redo log files.
Check that the backup is usable. If for any reason you have problems during the upgrade you must
be able to restore the database from this backup.
If you want to separate the alert log file of Oracle 9i from that of Oracle Database 10g Release 2
(10.2), you can move the alert log file to a different name with the following command:
28/48
PUBLIC
2009-08-25
4.2
1.
Stop the SAP application server by entering the following command as user <sapsid>adm:
stopsap r3
2.
Stop the Oracle listener by entering the following command as user ora<dbsid>:
lsnrctl stop
NOTE
Make sure that processes that log on to the database, such as CRON jobs, are not active during
the upgrade. Make sure that you reschedule these processes when the upgrade has finished.
1.
2.
Result
2009-08-25
PUBLIC
29/48
4.2