Win Ora Upgrade v50

8/8/2019 Win Ora Upgrade v50

1/58

Upgrade GuideUpgrade to Oracle Database 10g Release 2 (10.2): Windows

Target Audience

Technology Consultants

System Administrators

PUBLICDocument version: 5.0 2009-08-25


2/58

Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriate

entries to make entries in the system, for example, Enter your .

Example

Example

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the

documentationhttp://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific

content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example Words or characters quoted from the screen. These include field labels, screen titles,

pushbutton labels, menu names, and menu options.

Cross-references to other documentation or published works

Example Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program

File and directory names and their paths, names of variables and parameters, andnames of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, database table names, and key concepts of a programming language

when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2/58 PUBLIC 2009-08-25
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://www.sap.com/


3/58

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

The following table provides an overview on the most important document changes:

Version Date Description5.0 2009-08-25 Major Update

2009-08-25 PUBLIC 3/58
http://service.sap.com/instguideshttp://service.sap.com/instguides


4/58

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2 SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Checking the Original Version of Your Database . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 12

2.3 Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 12

2.4 Using Multiple Oracle Homes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Migrating to Automatic Undo Management . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.3 Stopping Statspack Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.4 Checking the SYSTEM and SYSAUX Tablespace for Freespace . . . . . . . . . . . . 17

3.5 Checking for Invalid Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.6 MSCS Only: Removing the Database from the Cluster Group . . . . . . . . . . . . . 18

3.7 MSCS Only: Upgrading to OFS 3.3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4 Oracle Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1 Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1.1 Installing the Oracle 10g Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1.2 Installing the Current Patch Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.1.3 Installing the Current Patch Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.1.4 Installing the Oracle 10g Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4.2 Copying and Adapting the SQL*Net Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.3 Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.4 Changing the Environment for User adm . . . . . . . . . . . . . . . . . . . . . 30

4.5 Performing the Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4/58 PUBLIC 2009-08-25


5/58

Chapter 5 Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.1 Creating the Oracle TNSListener Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.2 Changing Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.3 MSCS Only: Setting Up a Shared Database Directory in Oracle

Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5.4 Changing the Registry Value of Oracle Autostart . . . . . . . . . . . . . . . . . . . . . . 36

5.5 Starting the Oracle Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.6 Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.7 Deleting the Old Oracle Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.8 Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.9 Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.10 Creating the orapwd File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.11 MSCS Only: Adding the Database to the Cluster Group . . . . . . . . . . . . . . . . . 42

5.12 Changing the Location of the JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.13 Upgrading the SAP Executables to the Latest Version . . . . . . . . . . . . . . . . . . . 45

5.14 Disabling Database User Locking Mechanism For Failed Logins . . . . . . . . . . . . 46

5.15 Checking the National Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.16 Configuring the New Features for Oracle Database 10g Release 2

(10.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 6 Common Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.1 Starting and Stopping the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.1.1 Starting and Stopping the Database in a Standard Configuration . . . . . . . . . . 47

6.1.2 Starting and Stopping the Database in an MSCS Configuration . . . . . . . . . . . . 48

6.2 Checking Oracle Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.3 Starting and Stopping Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.4 Changing or Deleting Oracle Database Parameters . . . . . . . . . . . . . . . . . . . . . 51

6.5 Determining the Value of SAP System Profile Parameters . . . . . . . . . . . . . . . . 51

6.6 Moving Groups for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

6.7 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2009-08-25 PUBLIC 5/58


6/58

This page is left blank for documentsthat are printed on both sides.


7/58

1 Introduction

This documentation explains how to upgrade the Oracle database for the SAP system on the

Windows operating system from Oracle version 9.2.0.6 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 thedirect 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 for the database instance identifier and for the

SAP system identifier. These can be different if your:

Database system uses Oracle Real Application Cluster (RAC)

SAP system uses Multiple Components in One Database (MCOD) Implementation

Considerations

To have a common documentation layout for UNIX and Windows in this documentation,

we use / (slash) in SQL commands. Do not use / (slash) in command prompts.

Implementation Considerations

For more information about implementation considerations, including the most important SAP

Notes for the upgrade, see Planning [page 11].

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

1 Introduction

2009-08-25 PUBLIC 7/58
http://service.sap.com/noteshttp://service.sap.com/instguides


8/58

Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for

Oracle Database 10g Release 2 (10.2).

MSCS only: If your system is configured to run with Microsoft Cluster Service (MSCS) you have

to perform additional steps. These are necessary to include the additional MSCS nodes of the system

in the upgrade procedure and to deal with cluster-specific features. Steps that must be performed

for an MSCS configuration are marked with MSCS only in this documentation.

The cluster nodes that a particular step has to be executed on can be the:

First node, which is the primary node where the database server is located

Additional node for any secondary MSCS node

The database server and database client must be in the same Windows domain. For information

on permitted domain names see SAP Note314671.

1.1 New Features

For the complete list of new features of the Oracle Database 10g Release 2 (10.2), see the New Features

documentation from Oracle.

You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website.

RECOMMENDATION

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.

1.2 SAP Notes for the Upgrade

Make sure that you read the following SAP Notes, which you can find at

http://service.sap.com/notes:

Number Title Remarks

948305 Oracle Upgrade to 10g Release 2

(10.2) on Windows

Information about the upgrade and corrections to this

guide.720886 Oracle Database 10g: Integration

into the SAP environment

Provides information about integration of Oracle

Database 10g products / options within SAP

828268 Oracle Database 10g: New Functions Provides information about the Oracle Database 10g

features that can be used within an SAP environment. In

addition, contains links to notes describing the procedure

to activate some of the new Oracle Database 10g features.

830576 Parameter recommendations for

Oracle 10g

Provides information about Oracle initialization

parameters that need to be reset to their default values

or which need to be removed

841728 10.2: Solutions for installation and

upgrade problems

Describes known software installation problems and

solutions or workarounds

1 Introduction

1.1 New Features

8/58 PUBLIC 2009-08-25
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=830576&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=948305&_NLANG=en&_NVERS=0http://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=841728&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=830576&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=828268&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=720886&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=948305&_NLANG=en&_NVERS=0http://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=314671&_NLANG=en&_NVERS=0


9/58

Number Title Remarks

839187 Oracle 10.2.0: Applying Patch Set /

Patches / Patch Collection

Contains important information about the installation

of the current patch set, patch (UNIX) or patch collection

(Windows), and critical patch update (UNIX) for Oracle

10.2.0.4

871735 Current patch set for Oracle 10.2.0 Describes the current Oracle patch set

1137346 Oracle 10.2.0: Patches/Patch

collections for Oracle 10.2.0.4

Lists the status of Oracle patch sets and interim patches

for 10.2.0.4

134592 Importing the SAPDBA role

(sapdba_role.sql)

Describes how to update the SAPDBA role after the

upgrade

834917 Oracle Database 10g: New database

role SAPCONN

Describes the new SAPCONN role, which replaces the

native CONNECT role from Oracle

839182 Oracle Database 10g: OPatch Describes how to use OPatch with Oracle Database 10g

Release 2 (10.2)

306408 OPatch: Oracle tool for patchinstallation

Describes how to install an Oracle patch with OPatch

868681 Oracle Database 10g: Database

Release Check

Describes some additional transports to be applied to SAP

systems 640 and below before upgrade to Oracle database

10g

1.3 More Information on SAP Service Marketplace

You can find more information as following on SAP Service Marketplace:

Description Internet Address Title

SAP Notes http://service.sap.com/notes None

Oracle Database

Administration

www.sdn.sap.com/irj/sdn/

ora SAP ON ORACLE

KNOWLEDGE CENTER SAP

Documentation

SAP Database Guide: Oracle

SAP Software

Distribution Center

http://service.sap.com/swdc None

Oracle Database Upgrade

Guide

that is, the guide you arenow reading

http://service.sap.com/

instguides Database Upgrades

Oracle

Upgrade to Oracle Database : Windows

Oracle upgrade

documentation in Oracle

Metalink or My Oracle

Support

http://download.oracle.com

/docs/cd/B19306_01/server.

102/b14238/toc.htm

Upgrade: Oracle Database Upgrade Guide 10g Release 2

(10.2)

http://metalink.oracle.com 10g Upgrade Companion

Document ID: 466181.1

Complete Checklist for Manual Upgrades to 10gR2


Complete checklist for manual upgrades of Oracle

databases from any version to any version on any platform


1 Introduction


2009-08-25 PUBLIC 9/58
http://metalink.oracle.com/http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htmhttp://download.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htmhttp://download.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htmhttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/swdchttp://www.sdn.sap.com/irj/sdn/orahttp://www.sdn.sap.com/irj/sdn/orahttp://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=868681&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=306408&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839182&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=834917&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=134592&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1137346&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=871735&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839187&_NLANG=en&_NVERS=0


10/58

Description Internet Address Title

Oracle Technology

Network (OTN) forum

http://forums.oracle.com/

forums/forum.jspa?

forumID=583&start=0

None

1 Introduction


10/58 PUBLIC 2009-08-25
http://forums.oracle.com/forums/forum.jspa?forumID=583&start=0http://forums.oracle.com/forums/forum.jspa?forumID=583&start=0http://forums.oracle.com/forums/forum.jspa?forumID=583&start=0


11/58

2 Planning

RECOMMENDATION

Before the production upgrade, make sure that you perform a test upgrade on your backup system.

1. You check the original version of your database [page 11].

2. You check the hardware and software requirements [page 12].

3. You check additional requirements for the upgrade [page 12].

4. You decide whether you want to use multiple Oracle homes [page 13].

2.1 Checking the Original Version of Your Database

You need to check the original version of the database you want to upgrade.

CAUTION

This SAP upgrade documentation only covers the standard upgrade from Oracle 9.2.0.6 or later

to Oracle Database 10g Release 2 (10.2) using the Oracle Database Upgrade Assistant (DBUA).

Process

In the following special cases you need to obtain more information:

If you are upgrading from Oracle 8.1.7 or an earlier release, read the Oracle Database 10g Release 2

(10.2) upgrade documentation for information on the special steps required. Although Oracle

supports direct upgrades from Oracle 8.1.7 to Oracle 10.2.0, we recommend customers running

Oracle 8.1.7 to first upgrade to Oracle 9.2.0 and then to Oracle 10.2.0.

If you are upgrading from Oracle 9.2.0 to Oracle Database 10g Release 2 (10.2) in manual mode.

If the source database runs Oracle 9.2.0.4, 9.2.0.3, 9.2.0.2, or 9.2.0.1, you need to update the source

database to patch set 9.2.0.6 or later.For more information in these special cases, see the documentation for the Oracle Database 10g Release

2 (10.2) upgrade at the Oracle website.

RECOMMENDATION

If the source database is Oracle 10.1 we strongly recommend that it is at least version Oracle 10.1.0.4.

2 Planning

2.1 Checking the Original Version of Your Database

2009-08-25 PUBLIC 11/58


12/58

2.2 Checking Hardware and Software Requirements

You need to check that you meet the hardware and software requirements for running the new Oracle

release. The complete list of hardware and software requirements for every platform is included in the

Oracle documentation.

Prerequisites

You can access the complete Oracle documentation referred to below as amember of the Oracle

Technology Network (OTN).

Procedure

1. Note the following general hardware requirements:

At least 1024 MB of physical RAM

About 500 MB free space in the %TEMP% directory

At least 10 GB for the Oracle Home directory, consisting of:

3 to 5 GB for the Oracle software

About 5 GB for the patch information stored by OPATCH tool

This high space requirement is necessary due to the large number of patches that must be

applied on top of any given Oracle patch set.

2. Check that your operating system meets the software requirements for running the new Oracle

release, including all required patches. You might need to upgrade your operating system before

you start. The complete list of software requirements for every operating system is included in theOracle documentation.

RECOMMENDATION

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.

3. 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).

2.3 Checking Additional Requirements for the Upgrade

You need to check the additional requirements for the Oracle database upgrade as described in this

section.

Procedure

1. Make sure you have read the SAP Notes for the upgrade [page 8], which you can find at

http://service.sap.com/notes

2 Planning

2.2 Checking Hardware and Software Requirements

12/58 PUBLIC 2009-08-25
http://service.sap.com/noteshttp://service.sap.com/notes


13/58

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

SAP Release 4.6x, see SAP Note156548

SAP Release 6.x, see SAP Note407314

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

RECOMMENDATION

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 isregularly updated.

4. 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 Notes1137346 and 1137346. You can download the patches

from:

http://service.sap.com/swcenter-3pmain

CAUTION

The patches listed in SAP Note1137346 are mandatory. To avoid severe database

problems, make sure that you install all these patches.

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.

5. Download the latest version of the Oracle 10.2 Instant Client software from:

http://service.sap.com/swcenter-3pmain

6. Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the

database upgrade from:

http://service.sap.com/swdc

2.4 Using Multiple Oracle Homes

Before the upgrade or migration, you need to decide whether you want to set up multiple Oracle

Homes as this influences the procedure.

Oracle allows multiple Oracle Homes for specific database versions. This means that more than one

version of the database software can exist in different Oracle Home directories on the same host.

NOTE

MSCS only:

2 Planning


2009-08-25 PUBLIC 13/58
http://service.sap.com/swdchttp://service.sap.com/swcenter-3pmainhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1137346&_NLANG=en&_NVERS=0http://service.sap.com/swcenter-3pmainhttp://service.sap.com/swdchttp://service.sap.com/swcenter-3pmainhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1137346&_NLANG=en&_NVERS=0http://service.sap.com/swcenter-3pmainhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1137346&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1137346&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=407314&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=156548&_NLANG=en&_NVERS=0


14/58

Multiple Oracle Homes are not supported in a MSCS configuration. During the upgrade or

migration there are temporarily two Oracle Homes. However, the old Oracle Home is deleted at

the end of the migration or upgrade procedure. Note however that the Oracle Fail Safe software

is installed in its own Oracle Home.

Multiple Oracle Homes are necessary, if:

Two different databases are installed on the same computer and use different Oracle releases that

cannot be installed in a single Oracle Home directory.

A migration or an upgrade to Oracle 10g is being performed. The new Oracle software must be

installed in a new Oracle Home directory.

2 Planning


14/58 PUBLIC 2009-08-25


15/58

3 Preparation

You have to complete the following preparations:

1. You check the SAP System prerequisites [page 15].

2. If required, you migrate to automatic undo management[page 16].

3. If required, you stop Statspack reports [page 16].

4. You check the SYSTEM and SYSAUX tablespace for freespace [page 17].

5. If required, you check for invalid database objects [page 17].

6. MSCS only: You remove the database from the cluster group [page 18].

7. MSCS only: You upgrade to OFS 3.3.4 [page 19].

3.1 Checking the SAP System Prerequisites

You must check the prerequisites for the SAP system (ABAP) release 6.40 and lower. You need to:

1. Check that the Microsoft C Runtime libraries of version 71 are installed.

2. Update the database library (lib_dbsl.sar) to the latest patch level

3. Apply a correction to the ABAP systemThis is necessary to make the SAP system compatible for the Oracle Database 10g release checks.

4. You need to execute an SQL script that creates a new role on the database. This is necessary due

to changes to the Oracle CONNECT role in Oracle 10.2.

5. You must upgrade Java systems to at least Service Pack 13 before you can upgrade to Oracle Database

10g.

Procedure

1. Make sure that you have installed the latest Microsoft C Runtime dlls of version 71 with

R3DLLINS.EXE.The DLLs and the executable are attached to SAP Note684106.

2. Download the latest version ofdboraslib.dll for your release from:


3. Check the level of your Basis support package using this table:

SAP Release (SAP_BASIS) Basis Support Package Level

46B SAPKB46B57

46C SAPKB46C48

46D SAPKB46D38

6.10 SAPKB61041

3 Preparation

3.1 Checking the SAP System Prerequisites

2009-08-25 PUBLIC 15/58
http://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=684106&_NLANG=en&_NVERS=0


16/58

SAP Release (SAP_BASIS) Basis Support Package Level

6.20 SAPKB62044

6.40 SAPKB64009

If the level of your Basis support package is higher than or equal to that shown above, no

additional corrections are necessary.

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.

4. Execute the SQL script sapconn_role.sql as follows:

cd %ORACLE_HOME%\database

copy :\NT\\SAP\sapconn_role.sql

sqlplus /nolog @sapconn_role

3.2 Migrating to Automatic Undo Management

This step is only relevant if your database still uses manual undo management (rollback tablespace and

rollback segments).

If your database still uses rollback segments for undo management we strongly recommend you to

migrate to automatic undo management before starting the database update to Oracle database 10g.

Otherwise you might run into errors.

Procedure

1. Read SAP Note600141, which is the central note describing automatic undo management. This

note also gives you an overview of the concepts involved.

2. Follow the step-by-step instructions in the note to migrate to automatic undo management.

3.3 Stopping Statspack Reports

This step deletes the Statspack jobs with DBMS_JOB.REMOVE.

Prerequisites

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

Procedure

1. Log on as the user under which the statspack jobs run (usually PERFSTAT):

SQL>connect PERFSTAT/

SQL>select job, what from user_jobs;

This displays a list of the jobs that are currently entered under the user PERFSTAT.

3 Preparation

3.2 Migrating to Automatic Undo Management

16/58 PUBLIC 2009-08-25
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=868681&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=717484&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=600141&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=868681&_NLANG=en&_NVERS=0


17/58

2. Delete all jobs with the print job number :

SQL>connect PERFSTAT/

SQL>execute dbms_job.remove( );

3.4 Checking the SYSTEM and SYSAUX Tablespace forFreespace

You need to make sure that the SYSTEM and SYSAUX tablespaces have at least 750 MB freespace. This is

necessary due to a bug in the Oracle database that can cause the Oracle Database Upgrade Assistant

(DBUA) to underestimate the required freespace.

NOTE

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

Check if the SYSTEM or SYSAUX tablespace have enough freespace.

You can check this by executing one of the following commands as the adm user:

brspace f dbshow c tsinfo s SYSTEM

brspace f dbshow c tsinfo s SYSAUX

If the free space is less than 750 MB, use your preferred database administration tool to increase the size

by using one of the following options:

Setting the AUTOEXTEND option for the existing datafile to ON.

Adding an additional datafile.

Resizing the existing datafile.

3.5 Checking for Invalid Database Objects

This optional step lets you check if there are any invalid database objects before the database upgrade

to Oracle database 10g starts. After the upgrade it helps you distinguish database objects that have

become invalid due to the upgrade process from those that were already invalid to start with.

Procedure

1. Execute the following commands:

SQL>spool invalid_objects

SQL>select unique object_name, object_type, owner from dba_objects where status =

'INVALID';

SQL>@?/rdbms/admin/utlrp.sql

3 Preparation

3.4 Checking the SYSTEM and SYSAUX Tablespace for Freespace

2009-08-25 PUBLIC 17/58


18/58

SQL>select unique object_name, object_type, owner from dba_objects where status =

'INVALID';

SQL>spool off

A list of invalid objects before the upgrade is now generated.

2. Check the list of invalid objects after the upgrade.

If any objects in the list from before the upgrade are also in the list of invalid objects after the

upgrade, you can be sure that this is not due to the upgrade process.

RECOMMENDATION

If possible, delete or compile any invalid objects before the upgrade.

CAUTION

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";

3.6 MSCS Only: Removing the Database from the ClusterGroup

In an MSCS configuration, you have to remove the SAP database from the Oracle cluster group before

you begin the upgrade.

Procedure

NOTE

Perform the steps on the first MSCS node only. The database must be located on the first MSCS

node.

1. In the Cluster Administrator, take the SAP group offline.

2. In the Cluster Administrator, move all groups including the Cluster group to the first MSCS node.

3. Log on to the Oracle Fail Safe Manageras the user under which the Cluster Service is running.4. Choose Groups Oracle Cluster Resources and select .world. Click the right

mouse button and choose Remove from Group.

NOTE

To find out under which account the Cluster Service is running, choose Start Settings Control

Panel Administrative Tools Services . Select the Cluster Service and click Startup ...

The log on account for the service is displayed. Enter this account for Oracle Fail Safe Account/

Password.

For more information about services, see Checking Services [page 49].

5. In the dialog box Confirm Remove Database from Group, choose Yes.

3 Preparation

3.6 MSCS Only: Removing the Database from the Cluster Group

18/58 PUBLIC 2009-08-25


19/58

The Clusterwide operation window displays the steps that are executed to remove the database from

the cluster group. The last line informs you that The clusterwide operation completed successfully.

6. In the Clusterwide operation window, choose Close.

7. Exit the Fail Safe Manager.

3.7 MSCS Only: Upgrading to OFS 3.3.4

If the MSCS configuration is still running with Oracle Fail Safe Software (OFS) version lower than 3.3.4,

you must upgrade to version 3.3.4.

To do this, you first have to deinstall the old Oracle Fail Safe software on all MSCS nodes and then

install the Oracle Fail Safe 3.3.4 software on a local disk on all nodes. The installation procedure differs

depending on whether you install the Oracle Fail Safe software in a 32-bit or a 64-bit system.

CAUTION

For a domain user make sure that you use the syntax \. The

Oracle Fail Safe Software is not able to handle the syntax @.

Make sure that you install the Oracle Fail Safe 3.3.4 software in the same Oracle Home on all

MSCS nodes.

Prerequisites

You are logged on as user adm

.

The Cluster Service is started on all MSCS nodes.

For more information, see Starting and Stopping Services for MSCS [page 50].

Procedure

Deinstalling the Old Oracle Fail Safe Software

NOTE

On 64-bit, you have to deinstall the old client software for Oracle Fail Safe with the 32-bit version

of the Oracle Universal Installer on all MSCS nodes.

1. Make sure that the Oracle Fail Safe Manageris closed.

2. Uninstall the old OFS software on all MSCS nodes, as follows:

NOTE

While you are uninstalling the software on a particular MSCS node, do not reboot the other

node.

1. Start the Oracle Universal Installerfrom the DVD. To do this, double-click setup.exe in the

directory :\OFS\install.

2. In the Welcome screen, choose Installed Products.

3 Preparation


2009-08-25 PUBLIC 19/58


20/58

3. In the Inventory window, expand and select Oracle Fail Safe .

4. Choose Remove.

5. In the Confirmation dialog box, confirm that you wish to delete the selected products.

6. Click Exitto close the Oracle Universal Installer.

3. If you use a 64-bit system, you also have to deinstall the Oracle Fail Safe client software. To do this

you use the 32-bit Oracle Universal Installerfrom the Oracle RDBMS DVD.

1. Start the Oracle Universal Installerby double-clicking the file setup.exe in the directory

:\OFS334I386\Install


3. In the Inventory window, select OFSCLIand choose Remove.

4. In the Confirmation dialog box, confirm that you wish to delete the selected product.Installing the Oracle Fail Safe Software in a 32-Bit System

1. In the Cluster Administratormake sure that the:

Other MSCS node is not set to Pause.

SAP group is offline on the node where you are installing.

2. Make sure that the Cluster Serverservice is started on all MSCS nodes.

3. Start the Oracle Universal Installerfrom the Oracle RDBMS DVD.

To do this, double-click the file setup.exe in the directory :\OFS334I386.

The installer opens and guides you through the installation process in a series of screens.

NOTE

If the installer aborts and an error is displayed in an Application Errorwindow with the text The

exception unknown software exception ..., check the TMP and TEMP variables. In the user environment

ofadm, make sure that these refer to existing files. If not, reset them.

Screen Entry

Welcome Choose Next.

Specify File Locations Source...

For Path:

The path to the Oracle software on the DVD is

displayed. Do not change the path.

Destination...

For Name:

Enter the name of the Oracle Home for the Oracle

Fail Safe software. The Fail Safe software must be

installed in a separate Oracle Home directory, for

example, OFS

NOTE

If the Oracle Fail Safe version 3.3.1 or 3.3.2 was

previously installed, we strongly recommend

that you use the old Oracle Fail Safe Home for

3.3.4.

3 Preparation


20/58 PUBLIC 2009-08-25


21/58

Screen Entry

For Path:

Enter the path of the Oracle Home directory for the

Oracle Fail Safe software. It must be on a local disk,

for example: F:\Oracle\OFS

Available Products Select Oracle Fail Safe 3.3.4.0.0and choose Next.

Installation types Choose Typical.

Reboot Needed After Installation Choose Next.

Summary View the information and choose Install.

Install Wait while the software is installed.

Configuration Tools In the dialog box Oracle Fail Safe Account/Password, enter

the account and password under which the Oracle

Fail Safe software is to run. This must be the same

account as the one under which the Cluster Service is

running.To find out which account must be entered, choose

Start Settings Control Panel Administrative Tools

Services .

Select the Cluster Serviceand click Startup...

End of Installation Click Exitto leave the installer.

4. Reboot and log on again.

CAUTION

Do not reboot an MSCS node, if the installation of the OFS software or the deinstallation of

earlier releases is in progress on another node.

Installing the Oracle Fail Safe Software in a 64-Bit System

NOTE

If you use a 64-bit system you first have to install the 64-bit Fail Safe Server Software, and then the

32-bit Fail Safe Client Software.

1. In the Cluster Administratormake sure that the:

Other MSCS nodes are not set to Pause.

SAP group is offline on the MSCS node where you are installing.

2. Make sure that the Cluster Serverservice is started on all MSCS nodes.

3. Start the Oracle Universal Installerfrom the Oracle RDBMS DVD to install the 64-bit Fail Safe Server

Software.

Double-click the file setup.exe in the corresponding directory for your 64-bit platform:

:\OFS334IA64\install or >:\OFS334AMD64\install

4. Enter the required information as follows:

Screen Entry


File Locations Source...

For Path

3 Preparation


2009-08-25 PUBLIC 21/58


22/58

Screen Entry



Destination...

For NameEnter the name of the Oracle Home for the Fail Safe

software. The Fail Safe software must be installed in

a separate Oracle Home directory, for example

OFSSRV.

NOTE

IfOracle Fail Safe version 3.3.1 or 3.3.2 was

previously installed, we strongly recommend

to use the old Oracle Fail Safe Home for 3.3.4.

For Path


Fail Safe software. It must be on a local disk, for

example:

F:\Oracle\OFS\SRV

Choose Next.

Installation Types Choose Typical.

Reboot Needed After Installation Choose Next.



Configuration Tools In the dialog box Oracle Services for MSCS Account/

Password, enter the account and password under

which the Fail Safe software is to run. This must be thesame account as the one under which the Cluster

Serverservice is running.

To find out which account must be entered, choose

Start < Settings> Control Panel Administrative

Tools Services.

Select the Cluster Service and click Startup

The log on account for the service is displayed. Enter

this account for Oracle Fail Safe Account/Password..


5. Start the Oracle Universal Installerfrom the Oracle RDBMS DVD to install the Oracle Fail Safe 32-bit

client software.

To do this, double-click the file setup.exe in the following directory:

:\OFS334I386\install

6. Enter the required information as follows:

Screen Entry


File Locations Source...

For Path:



3 Preparation


22/58 PUBLIC 2009-08-25


23/58

Screen Entry

Destination...

For Name:

Enter the name of the Oracle Home for the Fail Safe

software. The Fail Safe software must be installed ina separate Home directory, for example OFSCLI.

Use the same Oracle Home for all MSCS nodes.

For Path:


Fail Safe software. It must be on a local disk, for

example:

F:\Oracle\OFS\CLI

Available Products Select Oracle Fail Safe 3.3.4.0.0and choose Next.

Installation Types Choose Client Only.




7. Reboot and log on again.

CAUTION

Do not reboot an MSCS node if the installation of the OFS software is in progress on another

node.

3 Preparation


2009-08-25 PUBLIC 23/58


24/58

This page is left blank for documentsthat are printed on both sides.


25/58

4 Oracle Database Upgrade

The following sections describe how to upgrade the Oracle database.

1. You install the Oracle 10g software [page 25].

2. You copy and adapt the old Oracle SQL*Net files [page 29].

3. You backup the Oracle database [page 30].

4. You change the environment for user adm [page 30].

5. You upgrade the Oracle database [page 31].

4.1 Installing the Oracle Database Software

The following sections describe how to install the Oracle server software and the Oracle client software.

4.1.1 Installing the Oracle 10g Server Software

Procedure

CAUTION

If you copy the files from the DVD to a local disk, do not use directory names containing blanks.

NOTE

You need 2 GB disk space for the Oracle server software.

MSCS only: You have to install the Oracle database server software on all MSCS nodes.

1. On the database server, place the Oracle RDBMS DVD in the DVD drive and change to the directory:

:\NT\2. Start the Oracle Universal Installeras follows:

If you want to install in the same directory where the previous ORACLE_HOME is set, double-

click the file sapserver.cmd.

NOTE

If a dos-box appears, specify the drive letter ofthe local disk where you want to install

the Oracle software, and the . The dos-box only appears if you perform a new

installation (under a different user), or if the ORACLE_HOME and are not set.

If you want to specify another installation directory, delete the ORACLE_HOME as

environment variable, before you double-click sapserver.cmd. This allows you to specify the



2009-08-25 PUBLIC 25/58


26/58

name and the path of the new ORACLE_HOME. When you have finished the database server

installation, do not forget to set ORACLE_HOME to the previous value again.

3. In the Oracle Universal Installer, enter the information as shown in the following table:

Window Entry

Specify File Locations If this screen appears, do the following:

Under Source:

For Path:

Shows the path to the Oracle source software.

Do not change the path.

Under Destination:

For Name:

Enter the name of the new Oracle Home

directory. We recommend that you use the

name, for example,

PRD102

For Path:

Enter the path of a new Oracle Home directory.

We recommend that you use the path:

:\ORACLE\\, for

example,

C:\ORACLE\PRD\102

NOTE

Do not specify an already existing Oracle

Home directory. You must specify a new

directory.

Choose Next.

Summary Choose Install.

Oracle Net Configuration Assistant: Welcome If this dialog appears, select Perform typical configuration.

Configuration Assistants NOTE

If you get an error message, choose OK.

Ignore the upcoming Warning screen and

choose OK.

Choose Next.

End of Installation Choose Exitto close the Oracle Universal Installer.

4. Install the latestpatch set[page 27] andpatch collection [page 27] (if available). For more information,refer to SAP Note839187.

NOTE

MSCS only:

You have to install the current Oracle patch set and patch collection (if available) on all MSCS

nodes.



26/58 PUBLIC 2009-08-25
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839187&_NLANG=en&_NVERS=0


27/58

4.1.2 Installing the Current Patch Set

After the database software installation [page 25], you need to install the current Oracle Database 10g Release

2 (10.2) patch set.

Prerequisites

For more information on the latest patch set available for Oracle 10.2 see SAP Note839187.

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 stepsmentioned in the README file.

You only have to install the latest (that is, the current) patch set.

Procedure

1. Log on as adm user.

2. Install the patch set as described on the patch set README file.

For more information, see SAP Note839187.

NOTE

MSCS only: You have to install the current Oracle patch set on all MSCS nodes.

4.1.3 Installing the Current Patch Collection

On Windows, you can install one patch collection and additional generic patches if required. Windows

patch collections are cumulative and contain the most current CPU. For more information about the

current patch collection and the generic patches, see SAP Note839187.

You use OPatch to install the patch collection and the generic patches. For more information, see SAP

Note839182.

Prerequisites

Make sure you have already installed the current patch set[page 27].

Procedure

1. Log on as adm user.

2. Install the patch collection, following the instructions in the README document of the patch

collection. Make sure that you complete the post-installation steps described in the README

document.



2009-08-25 PUBLIC 27/58
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839182&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839182&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839187&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839187&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=839187&_NLANG=en&_NVERS=0


28/58

NOTE

The README file uses the term bundle patch instead of patch collection.

MSCS only: You have to install the current Oracle patch collection (if available) on all

MSCS nodes.

4.1.4 Installing the Oracle 10g Client Software

To install the Oracle 10g database client software perform one of the following steps on the central and

dialog instance.

If you have an instance-specific exedirectory on the central instance host, you install and replicate

the client software automatically with sapcpe on each application server, every time the system

starts:

If you do not have an instance-specific exe directory on the central instance host, you have to

install the client software manually on the central instance host.

The following describes both procedures.

CAUTION

If you want to upgrade from Oracle 10.1.0 to Oracle 10.2. you have to delete the old Oracle instant

client software before you extract the Oracle 10.2. instant client:

1. Enter the following command in the DIR_CT_RUN[page 51] and all $(DIR_INSTANCE)

\exe-directories:

type dbclient.lst

2. Delete all files and directories listed in dbclient.lst.

Procedure

1. The following step is only relevant on the central instance host:

Extract the platform-specific OCL102.sar archive on the central instance as follows:

NOTE

The archive is located on the Oracle 10g Client Software DVD in the directory

OCL_WINDOWS_.

To unpack the archive, use the latestsapcar.exeprogram, which you find on the Oracle

RDBMS DVD in the directory: NT\\SAP.

In mixed environments (32-bit and 64-bit) you have to extract the archive in the respective

directory on both platforms.

If you have an instance-specificexedirectory on the central instance host, extract the platform-

specific OCL102.sar archive to the DIR_CT_RUN[page 51] directory.

Open a command prompt and enter the following commands in a separate line:

cd

sapcar -xvf \OCL102.SAR



28/58 PUBLIC 2009-08-25


29/58

If you do not have an instance-specific exe directory on the central instance host, extract the

platform-specific OCL102.sar archive to the DIR_EXECUTABLE[page 51] directory.

Open a command prompt and enter the following commands in a separate line:

cd

sapcar -xvf \OCL102.SAR

2. Define the following parameter in all instance profiles:

DIR_CLIENT_ORAHOME=$(DIR_EXECUTABLE)

4.2 Copying and Adapting the SQL*Net Files

After the database software installation, you must copy and modify the old SQL*Net files, that is,

listener.ora, sqlnet.ora, and tnsnames.ora.

Procedure

1. Log on as user adm.

2. Copy the SQL*Net parameter files from the \network\admin-directory to the

\network\admin-directory.

3. Edit the listener.ora in the \network\admin-directory.

Identify the parameter ORACLE_HOME that belongs to the database you want to upgrade (SID_NAME

in section SID_LIST) and change the value of the parameter ORACLE_HOME to point to the new

ORACLE_HOME.

4. Multiple Oracle Homes only: This step is only necessary, if you want to continue using additional

Oracle Homes after the database upgrade.

If you have two or more co-existing Oracle Homes, each has its own Listener and its own

corresponding configuration. Make sure that you do not use the same port number for more than

one listener.

To check existing numbers in the Net Manager:

1. Start the Net Managerthat guides you through the Network configuration process.

To do this, choose Start All Programs Oracle -

Configuration and Migration Tools Net Manager .

2. Choose File Oracle Net Configuration .

3. Select the Listener.

The port number for the Listener is displayed. Keep in mind that when you remove or change

port numbers for a Listener, you must do this for both the client and server using the Net

Manageras described earlier.

4. Carry out the previous steps for each active Oracle Homes and make sure that you do not use

the same port number for more than one listener.


4.2 Copying and Adapting the SQL*Net Files

2009-08-25 PUBLIC 29/58


30/58

4.3 Backing Up the Oracle Database

You must have a complete and usable database backup otherwise you might lose data.

We recommend you to back up all your Oracle 9i archive logs before you start the upgrade. The upgrade

changes the parameter log_archive_format to10.2.0. After the upgrade has completed BRARCHIVE

cannot back up archive files from before the upgrade (that is, from Oracle 9i or earlier) because of this

change to log_archive_format.

Procedure

1. Create a complete database and operating system backup, and back up any archive logs from Oracle

9i.

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

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

cd %SAPTRACE%\background (if the saptrace environment variable exists)

cd %SAPDATA_HOME%\saptrace\background (if the saptrace environment variable does not exist)

move alert_.log alert_.log-SV-9.2.0

4.4 Changing the Environment for User adm

Procedure

1. If you use multiple Oracle Homes, remove from the system environment variable PATH all parts

referring to the Oracle executables (%ORACLE_HOME%\bin) as follows:

1. Start the Oracle Universal Installer with Start All Programs Oracle - Oracle

Installation Products Universal Installer .


3. In the Inventory screen, choose the Environmenttab.

4. Deselect all components and choose Apply.

2. In the environment of the user adm, delete the following variables: ORACLE_HOME

TNS_ADMIN (if it exists)

NOTE

MSCS only: Delete the variables on all nodes.

3. If you use multiple Oracle Homes, update or create, if not available, the user environment

PATH of all users using the Oracle software to refer to the correct %ORACLE_HOME% as follows:

1. Choose My Computer Properties Advanced Environment Variables .

2. Set the value for PATH to


31/58

For more information on how to set parameters, see Changing Oracle Database Parameters [page 51].

5. Log off and log on again to activate the changes.

4.5 Performing the Database Upgrade

CAUTION

Currently you cannot upgrade an Oracle database that uses temporary Tablespaces with

allocation_type=USER. Therefore, before you start the Oracle Database Upgrade Assistant, check

and correct your database according to SAP Note905279.

Also apply this SAP Note if you get the following error message:

upgrade.xml is not a valid XML file.

Procedure

NOTE

MSCS only:

Follow the instructions on the first MSCS node only, where the database is located.

In the Cluster Administratormake sure that the database disks are online on the first MSCS node.

1. Stop the SAP system.

2. Change the registry entry ofORA__AUTOSTART as follows:

Enter the command:oradim -edit sid startmode manual

3. Start the Oracle Database Upgrade Assistantfrom the Startmenu with:

Start All Programs Oracle - Configuration and Migration Tools

Database Upgrade Assistant

The Oracle Database Upgrade Assistant (DUA) opens. A sequence of windows guides you through the

process. You can navigate between the windows by choosing Nextor Back.

NOTE

During the upgrade empty DOS-boxes may appear. Ignore them as long as they disappear

automatically.

Screen Input

DUA: Welcome Choose Next.

DUA: Databases 1. Select the database you want to upgrade.

CAUTION

The following warnings may appear:

If you are asked, to resize the rollback segment

SYSTEM, choose Continue.

If there is not enough space for the SYSTEM

tablespace, increase the space.

2. Choose Next.



2009-08-25 PUBLIC 31/58
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=905279&_NLANG=en&_NVERS=0


32/58

Screen Input

DUA: SYSAUX Tablespace NOTE

We recommend to change the name of the data file to

conform with the SAP file naming conventions for the

Oracle database. Therefore change the sysaux Tablespace

name from :\.\sapdata1\system_1

\sysaux01.dbf into :\sapdata1\sysaux_1

\sysaux.data1

Make sure that there is enough space on the specified

disk.

Note that br*tools can only process one data file per

directory.

Change the increment parameter from 1 MB to 10 MB, and then

choose Next.

DUA: Recompile Invalid Objects Leave selection unchanged and choose Next.

DUA: Backup Select I have already backed up my database, and then choose Next.

DUA: Management Options Leave the default settings and choose Next.

DUA: Database Credentials: Change the default passwords for the database users.

Summary Choose Finish to start the upgrade.

DUA: Progress The screen displays the phases of the data upgrade procedure. When

the upgrade has finished, choose OKto see the upgrade results.

DUA: Upgrade Results Check the results and any errors.

Do not choose Restore Database.

Close Choose Close.



32/58 PUBLIC 2009-08-25


33/58

5 Post-Upgrade Steps

After the Oracle database upgrade, you need to perform the steps described here.

1. You create the Oracle TNSListener service [page 33].

2. You set the user environment variables [page 33].

3. MSCS only: You set up a shared database directory in the Oracle home [page 34].

4. You change the registry value of Oracle Autostart[page 36].

5. You start the Oracle services [page 36].

6. You update BR*Tools [page 36].

7. You delete the old Oracle software [page 37].

8. You back up the database [page 39].

9. Youperform post-upgrade tasks [page 39].

10. You create the orapwd file [page 41].

11. MSCS only: You add the database to the cluster group [page 42].

12. You change the location of the JDBC driver[page 43].

13. You upgrade the SAP executables to the latest version [page 45].

14. You disable the database user locking mechanism on failed logins [page 46].15. If necessary, you change the national character set of your database to UTF8 [page 46].

16. You configure the new features for Oracle Database 10g Release 2 (10.2) [page 46].

5.1 Creating the Oracle TNSListener Service

Prerequisites

Stop the old Oracle listener before you create the Oracle TNSListener Service.

Procedure

Open a command prompt and enter the following command:

\bin\lsnrctl start

5.2 Changing Environment Variables

Procedure

NOTE

MSCS only: Edit the variables on all MSCS nodes.


5.1 Creating the Oracle TNSListener Service

2009-08-25 PUBLIC 33/58


34/58

1. In the user environment and system environment adm, check the PATH variable and, if

required, remove all parts referring to the old Oracle version.

CAUTION

When you modify the user environment, you must be logged on as the corresponding

adm user.

2. In the user environment ofadm, set the ORACLE_HOME variable to the correct value for

Oracle 10g, for example to: :\ORACLE\PRD\102.

3. If you have two or more co-existing Oracle Homes, make sure that the user environment variable

PATH of the adm user points to the corresponding %Oracle_Home%\bin-directory.

4. Copytnsnames.oraandsqlnet.ora from%ORACLE_HOME%\network\admin to\\

\sapmnt\\SYS\profile\oracle.

NOTEThis information is required for all ABAP application server you install on a separate host to

find the correct location of these files.

5. Set the user environment variableTNS_ADMIN to point to the directory\\\sapmnt

\\SYS\profile\oracle.

NOTE

Set TNS_ADMIN on all ABAP application server.

6. Reboot the computer.

5.3 MSCS Only: Setting Up a Shared Database Directory inOracle Home

The following describes how to set up a shared Oracle Home\database-directory with a link or junction

if your database is configured for using a spfile

A central Oracle Home\database-directory has the following advantages:

You can also use sqlplus remotely to make changes to your profile parameters

You have to make the changes in the parameter files only once in the shared Oracle Home\database-

directory.

If your database is not configured for using a spfile, you have to apply all changes in the

init.ora file in the Oracle Home\database-directories on all MSCS nodes.

To check the configuration of your database, see Changing or Deleting Oracle database parameters [page

51].

NOTE

Oracle Fail Safe does not support the direct use of an spfile. Therefore, you have to create a Fail

Safe-specific init_OFS.ora file, and specify it when adding the database to the cluster resource

group [page 42].


5.3 MSCS Only: Setting Up a Shared Database Directory in Oracle Home

34/58 PUBLIC 2009-08-25


35/58

Prerequisites

You have one of the following executables available:

linkd.exe

This executable is part of the Microsoft Windows 2003 Server Resource Kit.You can download the resource kit from www.microsoft.com.

Search for Microsoft Windows 2003 Server Resource Kit.

NOTE

After you have installed the resource kit, you can copy linkd.exe to any directory.

junction.exe

You can download this file from www.sysinternals.com.

Search forjunction.

Procedure1. Stop the Oracle database and the Oracle Service.

2. In the sapdata1 directory, create the directory database.

The sapdata1 directory is located on a shared disk in the cluster.

3. On the first MSCS node, change to the Oracle Home directory, and enter the following command:

move database\* \database

4. Delete the Oracle Home\database-directory with the command:

rd /q /s database

NOTE

You can also use the Windows Explorer to delete the directory.

5. Create the junction or link with the following DOS-command:

For junction, enter:

%Oracle_Home%\database

\database

For linkd, enter:

%Oracle_Home%\database

\database

NOTE

You can also use the 32-bit junction.exe or linkd.exe in a 64-bit Windows operating

system.

6. Move the disk where the \sapdata1\database directory is located to another MSCS node.

7. Repeat step 4 and step 5 on the other MSCS nodes.

8. Edit or create the file init_OFS.ora in the database directory, and enter the following

line:

spfile = \database\SPFILE.ora


5.3 MSCS Only: Setting Up a Shared Database Directory in Oracle Home

2009-08-25 PUBLIC 35/58
http://www.sysinternals.com/http://www.microsoft.com/


36/58

NOTE

If the file init_OFS.ora is not available, create the file in the database directory.

5.4 Changing the Registry Value of Oracle Autostart

Procedure

Change the registry value with the following command:

oradim -edit -sid -startmode manual

NOTE

Make sure that you use oradim of Oracle 10.2.

NOTE

If you have several Oracle Homes, ORA__AUTOSTART, is available in one Oracle Home only.

Set the value for ORA__AUTOSTART from TRUE to FALSE.

5.5 Starting the Oracle Services

Procedure

Start the Oracle services, if not yet started.

In a standard configuration, set the startup type ofOracleService and

OracleTNSListener to automatic to ensure that they are automatically restartedafter booting. For more information on how to start services, see Starting or Stopping Services [page 50].

CAUTION

MSCS only:

Set the startup type ofOracleService and OracleTNSListener to

manual to ensure that they are not automatically restarted after booting.

5.6 Updating BR*ToolsYou update BR*Tools to the latest release, with the latest patch level. After extracting the latest

BR*Tools release you need to update the SAPDBA role using the script sapdba_role.sql. This is

essential so that the new release of BR*Tools works correctly. The script is automatically extracted

when you extract BR*Tools.

Procedure

1. Download the most current version of the BR*Tools from SAP Service Marketplace at:


2. Unpack BR*Tools to the DIR_CT_RUN[page 51] directory.


5.4 Changing the Registry Value of Oracle Autostart

36/58 PUBLIC 2009-08-25
http://service.sap.com/swdchttp://service.sap.com/swdc


37/58

NOTE

MSCS only: Install BR*Tools in the following directories:

DIR_CT_RUN[page 51] on one MSCS node only.

%windir%\SapCluster on all MSCS nodes.3. After you have extracted the newest BR*Tools you also need to copy the BR*Tools configuration

files init.sap and init.utl from the \database directory

to the new one:

cd \database

copy init.sap %ORACLE_HOME%\database

copy init.utl %ORACLE_HOME%\database (this file is only available only if you use a 3rd

party backup solution)

NOTE

init.dba is no longer needed because BR*Tools release 6.40 SAPDBA is no longer

available.

The init.utl file is only available if you use external backup software based on

a backint interface.

4. Update the SAPDBA role as adm user as follows:

1. Copy sapdba_role.sql from the DIR_CT_RUN directory to the %ORACLE_HOME%\database

directory.

2. Execute the following SQL commands:

Only valid for: ABAP |

sqlplus /nolog @sapdba_role

End of: ABAP |

Only valid for: Java |

sqlplus /nolog @sapdba_role DB

End of: Java |

NOTE

If you have an ABAP+Java system, you have to enter both commands.

CAUTION

Make sure that you execute the commands for everySAPSCHEMA_ID in your database.

5.7 Deleting the Old Oracle Software

You use the Oracle Universal Installer to delete the old Oracle software.

CAUTION

MSCS only:

Carry out this procedure only after you have added the database to the cluster group [page 42]. Perform

the steps on all MSCS nodes.



2009-08-25 PUBLIC 37/58


38/58

CAUTION

Do not delete the old software, if it still has to be accessed by another SAP instance running

with this version. For example, this may be the case if an SAP dialog or central instance

belonging to a different SAP system is running on the same database host.

Database client only:

In a distributed system, you must delete the old Oracle database client 9.2 software at least on

the central instance host before you start upgrading your SAP system. In a distributed system,

your central instance is installed on a separate host than the database instance.

If you cannot delete the old Oracle client software because it is used by other programs or

SAP instances on the same host, you have to modify the environment variable path for user

adm and SAPService. Make sure that it does not contain any reference to

the old ORACLE_HOME\bin directory.

In a central system, only delete the database client after you have finished upgrading your

system.

Procedure

1. Stop the database.

2. MSCS only: Set the Oracle Services for MSCS offline.

3. MSCS only: Stop the ClusterService on all MSCS nodes.

4. Stop the service Distributed Transaction Coordinator.

5. Stop the services of the old Oracle Home.

6. Start the Oracle Universal Installer from your Startmenu as follows:

If you find the Universal Installerunder Start All Programs Oracle

Installation Products Universal Installer , you must start it from this path.

Otherwise, start it from Start All Programs Oracle Installation Products Universal Installer

NOTE

Note that on a database client, you start the Universal Installer from the Oracle RDBMS

DVD. Double-click the file setup.exe in the directory :\NT\

\install

7. Follow the instructions for your Oracle Home you want to remove.1. In the Welcome screen, choose Deinstall Products.

2. In the Inventory dialog box, expand the node representing your old Oracle Home and remove

it.

On a database client, you expand the node representing the old Oracle Home and remove

it.

3. Confirm the removal of the products in the popup that appears



38/58 PUBLIC 2009-08-25


39/58

NOTE

Note that it is not possible to delete all old Oracle products. These are deleted in the

following steps.

8. Delete the services whose name contains the old Oracle Home name.To delete a service, open a command prompt and enter:

sc delete

Make sure that you do not delete the services listed under Oracle Services [page 49].

NOTE

Multiple Oracle Homes only: On a database server with multiple Oracle Homes, do not

delete the service OracleService. If more than one Listener is configured, do not

delete these either.

9. In the Windows Explorer, delete the Oracle Home directory of old software.

10. Delete the entry Oracle for Windows NT, if it exists, in the Windows Startmenu, as follows:

1. Choose Start All Programs

2. Right-click Oracle and choose Delete.

CAUTION

Make sure that you delete the registry key for the earlier Oracle version, for example:

HKEY_LOCAL_MACHINE SOFTWARE ORACLE HOME only, if there is

only one Oracle client installed. Otherwise do not delete it.

5.8 Backing Up the Database

You need to back up your upgraded Oracle Database 10g database.

CAUTION

You risk losing data if you do not back up your database.

Procedure

Perform a full database backup.

5.9 Performing Post-Upgrade Tasks

You need to perform certain post-upgrade tasks.

Procedure

1. Change database compatibility by executing the following SQL command as the adm user:

sqlplus /nolog

SQL>connect / as sysdba

SQL>alter system set compatible='10.2.0' scope = spfile;


5.8 Backing Up the Database

2009-08-25 PUBLIC 39/58


40/58

2. Restart the Oracle database.

3. Deactivate the Oracle recycle bin by executing the following SQL command as the adm

user:

SQL>purge dba_recyclebin;

SQL>alter system set recyclebin = 'off' scope = spfile;

For more information, see SAP Note838982.

4. Gather Oracle optimizer statistics as follows:

1. Execute the following commands as the adm user:

brconnect -u / -c -f stats -t system_stats

brconnect -u / -c -f stats -t oradict_stats

2. Execute the following commands with SQLPlus:

SQL>exec dbms_scheduler.disable('GATHER_STATS_JOB');

SQL>exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');

SQL>exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

5. Identify the objects that are invalid after the upgrade as follows:

1. Execute the following commands as the adm user:

SQL>@?/rdbms/admin/utlrp.sql;

SQL>spool %ORACLE_HOME%/cfgtoollogs/invalid_post.log

SQL>select count(*) from dba_objects where status = 'INVALID';

SQL>select substr(owner,1,12) owner, substr(object_name,1,30) object, substr

(object_type,1,30) type, status from dba_objects where status 'VALID' order

by owner;

SQL>spool off;

2. Check the log file invalid_post.log. created at %ORACLE_HOME%\ cfgtoollogs

\invalid_post.log to compare the invalid objects before the start of the upgrade.

6. Check the Oracle database parameters against SAP Note830576 and adjust them if necessary.

You can find an automated script in SAP Note1171650 to help you check whether your SAP system

complies with the database parameter recommendations at any given point in time.

7. Restart the database to activate the changes:

1. Log on to the database with SQL*Plus

2. Execute the following commands:

sqlplus / as sysdba

shutdown immediate

startup

8. Gather statistics for SAP schemas:

1. With Oracle Database 10g all tables have statistics, which means that you need to update some

entries in the DBSTATC table before starting BRCONNECT, as follows:

sqlplus SAP/


5.9 Performing Post-Upgrade Tasks

40/58 PUBLIC 2009-08-25
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1171650&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=830576&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=838982&_NLANG=en&_NVERS=0


41/58

SQL>update DBSTATC set activ = 'A' where activ in ('N', 'R');

SQL>commit;

CAUTION

Perform this action separately for each SAP schema on the database, but not for Java

systems.

2. Update the Oracle database statistics with BRCONNECT as follows:

brconnect -c -u / -f stats -t all f collect -p 4

NOTE

For more information about update statistics, see the documentation SAP Database Guide:

Oracle at:

www.sdn.sap.com/irj/sdn/ora SAP ON ORACLE KNOWLEDGE CENTER SAP

Documentation

5.10 Creating the orapwd File

You create the orapwd file to use for the Oracle Enterprise Manager. This allows you to connect to the

Oracle database as sysdba without using the operating system users.

NOTE

This procedure is only required if you upgraded an Oracle 9.2.0.6 database to Oracle 10.2.

Procedure

1. In sqlplus, set the parameter remote_login_passwordfile to EXCLUSIVE.

For more information on how to set parameters, see Changing Oracle Database Parameters [page 51].

2. Open a command prompt and create the pwd.ora file with the following command:

orapwd file=%Oracle_Home%\database\pwd.ora password=

entries=100 force=y

Enter a password for .

3. Stop and restart the Oracle database.

4. To allow a database user, for example sap, or a system to connect to the Oracle databaseas sysdba or sysoper (connect dbusername/dbpassword as sysdba) although the database is

not started, enter the following commands:

sqlplus /nolog

SQL>connect / as sysdba

SQL>grant sysdba to ;

SQL>grant sysoper to ;


5.10 Creating the orapwd File

2009-08-25 PUBLIC 41/58
http://www.sdn.sap.com/irj/sdn/ora


42/58

5.11 MSCS Only: Adding the Database to the Cluster Group

To enable a database to fail over with all the resources it requires, you must add it to the cluster group.

Prerequisites

The Cluster Service is running on all MSCS nodes.

Procedure

1. Copy the file sqlnet.ora from the directory %ORACLE_HOME%\network\admin from the first MSCS

node to the same directory on the additional MSCS node.

2. Start the Cluster Administratorand bring the Oracle Services for MSCS resource online.

3. Start the Oracle services.

4. Start the database.

5. Start the Oracle Fail Safe Managerwith Start All Programs Oracle - Oracle

Fail Safe Manager .

6. If the Welcome dialog box appears, choose Verify Cluster. Otherwise, right-click the cluster and choose

Verify Cluster.

NOTE

All MSCS nodes must be up and running for this step.

The window Verifying Clustershows the steps that are executed to verify the cluster. When you are

informed that the operation has completed successfully, close the window.

7. Add the SAP database to the cluster group Oracle.

1. In the tree on the left, choose Nodes Standalone Resources .

2. Select the database .world

3. Choose Resources Add to Group .

8. In the dialog box Add Resource to Group Resource:

For Resource Type, select Oracle Database.

For Group name, select Oracle.

9. Choose Next.

10. In the dialog box Add Resource to Group Database Identity:, enter the following information:

Service Name .world

Instance Name

Database Name

Parameter File :\\database\init_OFS.ora

11. Choose Next.

12. In the dialog box Add Resource to Group Database Password:

Select Yes, create the password file (recommended).

Enter and confirm the password.

13. Choose Finish.


5.11 MSCS Only: Adding the Database to the Cluster Group

42/58 PUBLIC 2009-08-25


43/58

14. In the dialog box Finish Adding the Database to the Group, choose OKto add the database resource to the

group.

15. In the dialog box Confirm Add database to Group, choose Yes.

The Adding resource .world to group window, shows the steps that are executed to add the

database to the cluster group.

16. Copy tnsnames.ora from %ORACLE_HOME%\network\admin to \\\sapmnt

\\SYS\profile\oracle.

17. On the additional MSCS node, set the user environment variable TNS_ADMIN to point to the

directory \\\sapmnt\\SYS\profile\oracle.

Only valid for: ABAP+Java;Java;Java Add-In |

5.12 Changing the Location of the JDBC Driver

If you have an SAP system with Java components, you may have to change the location of the JDBC

driver after you have upgraded the database. Otherwise the J2EE Engine cannot start because the

location of the JDBC driver still points to the path of the old ORACLE HOME.

You change the location of the JDBC driver as follows:

In files that are located in the database you use the J2EE Engine Config Tool to change the JDBC

driver location.

In files that are not located in the database you use Note Pad or another text editor to change the

JDBC driver location.

CAUTION

Make sure when you change the driver location that you use a forward slash "/" or backward

slash "\" as appropriate.

Make sure that you replace the old driver location in all locations stated in the following

procedure.

Procedure

1. Change to the config.properties file, which is located in the following directory:


/usr/sap//JC/j2ee/configtool

End of: Java |

Only valid for: ABAP+Java;Java Add-In |

/usr/sap//DVEBMGS/j2ee/configtool

End of: ABAP+Java;Java Add-In |

1. Open the file with your text editor and search for the property rdbms.DriverLocation.

2. Replace the old driver location with the new one:

:\\usr\\sap\\\\JC\\exe\

\.jar (if it exists) or:



2009-08-25 PUBLIC 43/58


44/58

:\\usr\\sap\\\\SYS\\exe\\run\\.jar

where .jar is classes12.jar or ojdbc14.jar

2. In the same directory as in the first step, start the J2EE Engine - ConfigTool by double-clicking

the configtool.bat file.

1. Change to Configuration Editor mode.

2. Use the Editmode to replace the driver location in the following property sheets that contain

the string rdbms.driverLocation= followed by the driver location:

cluster_data/Propertysheet instance.properties.IDXXXXXXX/

IDXXXXXXX.JavaParameters

where XXXXXXX is the instance number

NOTE

Make sure that you change all occurrences. There might be severalIDXXXXXX.JavaParameters properties in the property sheet.

cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager

cluster_data/server/IDXXXX/kernel/propertysheet ConfigurationManager

where XXXX is the instance number

NOTE

If you have more than one server or dispatcher you must modify all relevant

property sheets.

3. Close theJ2EE Engine - ConfigTool.

3. Change to the bootstrap.properties file, which is located in the following directory:


/usr/sap//JC/j2ee/cluster/bootstrap

End of: Java |


/usr/sap//DVEBMGS/j2ee/ cluster/bootstrap

1. Open the file with your text editor and search for the property rdbms.DriverLocation.

2. Replace the old driver location with the new one:


\.jar (if it exists) or::\\usr\\sap\\\\SYS\\exe\\run\\.jar

CAUTION

If you have more than one J2EE Engine server installed, you must repeat steps 2 and

3 for all servers.


4. Change to the sdmrepository.sdc file, which you can find in the following directory:


/usr/sap//JC/SDM/program/config/

End of: Java |



44/58 PUBLIC 2009-08-25


45/58


/usr/sap//DVEBMGS/SDM/program/config/

1. Search for the following text:

2. If required, replace the old driver location with the new one, such as one of the following:

:\\jdbc\lib\


\.jar (if it exists), or:

:\\usr\\sap\\\\SYS\\exe\\run\\.jar


5. Change to the rdb.properties file, which is located in the following directory:

/usr/sap///j2ee/deploying

1. Open the file with your text editor and search for the property rdbms.Drive

Win Ora Upgrade v50

Documents

Transcript of Win Ora Upgrade v50