Vous êtes sur la page 1sur 58

Upgrade Guide

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

Target Audience
`*èQå Technology Consultants
`*èQå System Administrators

PUBLIC
`*èàt*ñF˚*¡’£ÉŁ©~}u"P'a*éù_' ýfl"µ¸F–ÃEt´⁄üBéˆÃêñÇsêf „†E’TÙ�“”Ð<ü~
Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://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 ˜¾úU Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
˜¾úU Cross-references to other documentation or published works
Example ˜¾úU Output on the screen following a user action, for example, messages
˜¾úU Source code or syntax quoted directly from a program
˜¾úU File and directory names and their paths, names of variables and parameters, and
names 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


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 Description
5.0 2009-08-25 Major Update

2009-08-25 PUBLIC 3/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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.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 <dbsid>adm . . . . . . . . . . . . . . . . . . . . . 30
4.5 Performing the Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4/58 PUBLIC 2009-08-25


Chapter 5 Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.1 Creating the Oracle TNSListener Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2 Changing Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.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


This page is left blank for documents
that are printed on both sides.
1 Introduction

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

)Øfi‚m In this document we use <DBSID> for the database instance identifier and <SAPSID> for the
SAP system identifier. These can be different if your:
)Øfi‚ Database system uses Oracle Real Application Cluster (RAC)
)Øfi‚ SAP system uses Multiple Components in One Database (MCOD) Implementation
Considerations
)Øfi‚m 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

)Øfi‚m For more information about implementation considerations, including the most important SAP
Notes for the upgrade, see Planning [page 11].
)Øfi‚m 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

2009-08-25 PUBLIC 7/58


1 Introduction
1.1 New Features

(^æ˛¦M Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for
Oracle Database 10g Release 2 (10.2).
(^æ˛¦M 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
(^æ˛¦M The database server and database client must be in the same Windows domain. For information
on permitted domain names see SAP Note 314671.

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 Information about the upgrade and corrections to this
(10.2) on Windows guide.
720886 Oracle Database 10g: Integration Provides information about integration of Oracle
into the SAP environment 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 Provides information about Oracle initialization
Oracle 10g parameters that need to be reset to their default values
or which need to be removed
841728 10.2: Solutions for installation and Describes known software installation problems and
upgrade problems solutions or workarounds

8/58 PUBLIC 2009-08-25


1 Introduction
1.3 More Information on SAP Service Marketplace

Number Title Remarks


839187 Oracle 10.2.0: Applying Patch Set / Contains important information about the installation
Patches / Patch Collection 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 Lists the status of Oracle patch sets and interim patches
collections for Oracle 10.2.0.4 for 10.2.0.4
134592 Importing the SAPDBA role Describes how to update the SAPDBA role after the
(sapdba_role.sql) upgrade
834917 Oracle Database 10g: New database Describes the new SAPCONN role, which replaces the
role SAPCONN 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 patch Describes how to install an Oracle patch with OPatch
installation
868681 Oracle Database 10g: Database Describes some additional transports to be applied to SAP
Release Check 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 www.sdn.sap.com/irj/sdn/ SAP Database Guide: Oracle
Administration ora SAP ON ORACLE
KNOWLEDGE CENTER SAP
Documentation
SAP Software http://service.sap.com/swdc None
Distribution Center
Oracle Database Upgrade http://service.sap.com/ Upgrade to Oracle Database <Version>: Windows
Guide instguides Database Upgrades
– that is, the guide you are Oracle
now reading
Oracle upgrade http://download.oracle.com Upgrade: Oracle Database Upgrade Guide 10g Release 2
documentation in Oracle /docs/cd/B19306_01/server. (10.2)
Metalink or My Oracle 102/b14238/toc.htm
Support http://metalink.oracle.com r]@0$ 10g Upgrade Companion
Document ID: 466181.1
r]@0$ Complete Checklist for Manual Upgrades to 10gR2
Document ID: 316889.1
r]@0$ Complete checklist for manual upgrades of Oracle
databases from any version to any version on any platform
Document ID: 421191.1

2009-08-25 PUBLIC 9/58


1 Introduction
1.3 More Information on SAP Service Marketplace

Description Internet Address Title


Oracle Technology http://forums.oracle.com/ None
Network (OTN) forum forums/forum.jspa?
forumID=583&start=0

10/58 PUBLIC 2009-08-25


2 Planning
2.1 Checking the Original Version of Your Database

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:
òÇ5¤®e 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.
òÇ5¤®e If you are upgrading from Oracle 9.2.0 to Oracle Database 10g Release 2 (10.2) in manual mode.
òÇ5¤®e 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.

2009-08-25 PUBLIC 11/58


2 Planning
2.2 Checking Hardware and Software Requirements

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 a member of the Oracle
Technology Network (OTN).

Procedure
1. Note the following general hardware requirements:
XuÃ÷ At least 1024 MB of physical RAM
XuÃ÷ About 500 MB free space in the %TEMP% directory
XuÃ÷ At least 10 GB for the Oracle Home directory, consisting of:
XuÃÃØ 3 to 5 GB for the Oracle software
XuÃÃØ 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 the
Oracle 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

12/58 PUBLIC 2009-08-25


2 Planning
2.4 Using Multiple Oracle Homes

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:
#ú+Pèj SAP Release 4.6x, see SAP Note 156548
#ú+Pèj SAP Release 6.x, see SAP Note 407314
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 is
regularly 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 Notes 1137346 and 1137346. You can download the patches
from:
http://service.sap.com/swcenter-3pmain
CAUTION

#ú+Pèj The patches listed in SAP Note 1137346 are mandatory. To avoid severe database
problems, make sure that you install all these patches.
#ú+Pèj 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:

2009-08-25 PUBLIC 13/58


2 Planning
2.4 Using Multiple Oracle Homes

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:


v
"¦Â Two different databases are installed on the same computer and use different Oracle releases that
cannot be installed in a single Oracle Home directory.
v
"¦Â A migration or an upgrade to Oracle 10g is being performed. The new Oracle software must be
installed in a new Oracle Home directory.

14/58 PUBLIC 2009-08-25


3 Preparation
3.1 Checking the SAP System Prerequisites

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<xxx>.sar) to the latest patch level
3. Apply a correction to the ABAP system
This 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 Note 684106.
2. Download the latest version of dboraslib.dll for your release from:
http://service.sap.com/swdc
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

2009-08-25 PUBLIC 15/58


3 Preparation
3.2 Migrating to Automatic Undo Management

SAP Release (SAP_BASIS) Basis Support Package Level


6.20 SAPKB62044
6.40 SAPKB64009

Bçpo ` If the level of your Basis support package is higher than or equal to that shown above, no
additional corrections are necessary.
Bçpo ` 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 <ORACLE_DVD>:\NT\<platform>\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 Note 600141, 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 Note 717484.

Procedure
1. Log on as the user under which the statspack jobs run (usually PERFSTAT):
SQL> connect PERFSTAT/<pwd>
SQL> select job, what from user_jobs;
This displays a list of the jobs that are currently entered under the user PERFSTAT.

16/58 PUBLIC 2009-08-25


3 Preparation
3.4 Checking the SYSTEM and SYSAUX Tablespace for Freespace

2. Delete all jobs with the print job number <jobnr>:


SQL> connect PERFSTAT/<pwd>
SQL> execute dbms_job.remove( <jobnr> );

3.4 Checking the SYSTEM and SYSAUX Tablespace for


Freespace
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 <dbsid>adm user:
ü×�²vS brspace –f dbshow –c tsinfo –s SYSTEM
ü×�²vS 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:
ü×�²vS Setting the AUTOEXTEND option for the existing datafile to ON.
ü×�²vS Adding an additional datafile.
ü×�²vS 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

2009-08-25 PUBLIC 17/58


3 Preparation
3.6 MSCS Only: Removing the Database from the Cluster Group

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 Cluster


Group
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 Manager as the user under which the Cluster Service is running.
4. Choose Groups Oracle<DBSID> Cluster Resources and select <DBSID>.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.

18/58 PUBLIC 2009-08-25


3 Preparation
3.7 MSCS Only: Upgrading to OFS 3.3.4

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

fýGªå For a domain user make sure that you use the syntax <domain_name>\<user_name>. The
Oracle Fail Safe Software is not able to handle the syntax <user_name>@<domain>.
fýGªå Make sure that you install the Oracle Fail Safe 3.3.4 software in the same Oracle Home on all
MSCS nodes.

Prerequisites
fýGªå You are logged on as user <SAPSID>adm
.
fýGªå 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 Manager is 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 Installer from the DVD. To do this, double-click setup.exe in the
directory <DVD_DRIVE>:\OFS<platform>\install.
2. In the Welcome screen, choose Installed Products.

2009-08-25 PUBLIC 19/58


3 Preparation
3.7 MSCS Only: Upgrading to OFS 3.3.4

3. In the Inventory window, expand <Fail_Safe_Home> and select Oracle Fail Safe <version_lower_to
3.3.4>.
4. Choose Remove.
5. In the Confirmation dialog box, confirm that you wish to delete the selected products.
6. Click Exit to 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 Installer from the Oracle RDBMS DVD.
1. Start the Oracle Universal Installer by double-clicking the file setup.exe in the directory
<DVD_DRIVE>:\OFS334I386\Install
2. In the Welcome screen, choose Installed Products.
3. In the Inventory window, select OFSCLI and 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 Administrator make sure that the:


ÐÅ’U"¨ Other MSCS node is not set to Pause.
ÐÅ’U"¨ SAP group is offline on the node where you are installing.
2. Make sure that the Cluster Server service is started on all MSCS nodes.
3. Start the Oracle Universal Installer from the Oracle RDBMS DVD.
To do this, double-click the file setup.exe in the directory <DVD_DRIVE>:\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 Error window with the text The
exception unknown software exception ..., check the TMP and TEMP variables. In the user environment
of <SAPSID>adm, 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.

20/58 PUBLIC 2009-08-25


3 Preparation
3.7 MSCS Only: Upgrading to OFS 3.3.4

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.0 and 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 Exit to 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 Administrator make sure that the:


ÐùfiÝé\ Other MSCS nodes are not set to Pause.
ÐùfiÝé\ SAP group is offline on the MSCS node where you are installing.
2. Make sure that the Cluster Server service is started on all MSCS nodes.
3. Start the Oracle Universal Installer from 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:
<DVD_DRIVE>:\OFS334IA64\install or <DVD_DRIVE>>:\OFS334AMD64\install
4. Enter the required information as follows:
Screen Entry
Welcome Choose Next.
File Locations Source...
For Path

2009-08-25 PUBLIC 21/58


3 Preparation
3.7 MSCS Only: Upgrading to OFS 3.3.4

Screen Entry
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 Fail Safe
software. The Fail Safe software must be installed in
a separate Oracle Home directory, for example
OFSSRV.

NOTE
If Oracle 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
Enter the path of the Oracle Home directory for the
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.
Summary View the information and choose Install.
Install Wait while the software is installed.
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 the
same account as the one under which the Cluster
Server service 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..
End of Installation Click Exit to leave the installer.
5. Start the Oracle Universal Installer from 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:
<DVD_DRIVE>:\OFS334I386\install
6. Enter the required information as follows:
Screen Entry
Welcome Choose Next.
File Locations Source...
For Path:
The path to the Oracle software on the DVD is
displayed. Do not change the path.

22/58 PUBLIC 2009-08-25


3 Preparation
3.7 MSCS Only: Upgrading to OFS 3.3.4

Screen Entry
Destination...
For Name:
Enter the name of the Oracle Home for the Fail Safe
software. The Fail Safe software must be installed in
a separate Home directory, for example OFSCLI.
Use the same Oracle Home for all MSCS nodes.
For Path:
Enter the path of the Oracle Home directory for the
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.0 and choose Next.
Installation Types Choose Client Only.
Summary View the information and choose Install.
Install Wait while the software is installed.
End of Installation Click Exit to leave the installer.
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.

2009-08-25 PUBLIC 23/58


This page is left blank for documents
that are printed on both sides.
4 Oracle Database Upgrade
4.1 Installing the Oracle Database Software

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 <dbsid>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

ÐWgŠv You need 2 GB disk space for the Oracle server software.
ÐWgŠv 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:
<DVD_DRIVE>:\NT\<platform>
2. Start the Oracle Universal Installer as follows:
ÐWgŠv 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 of the local disk where you want to install
the Oracle software, and the <DBSID>. The dos-box only appears if you perform a new
installation (under a different user), or if the ORACLE_HOME and <DBSID> are not set.
ÐWgŠv 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


4 Oracle Database Upgrade
4.1 Installing the Oracle Database Software

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:
 N9ı For Path:
Shows the path to the Oracle source software.
Do not change the path.
Under Destination:
 N9ı For Name:
Enter the name of the new Oracle Home
directory. We recommend that you use the
name <SAPSID><ORACLE_VERSION>, for example,
PRD102
 N9ı For Path:
Enter the path of a new Oracle Home directory.
We recommend that you use the path:
<DRIVE>:\ORACLE\<DBSID>\<ORA_VERS>, 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 Exit to close the Oracle Universal Installer.
4. Install the latest patch set [page 27] and patch collection [page 27] (if available). For more information,
refer to SAP Note 839187.
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


4 Oracle Database Upgrade
4.1 Installing the Oracle Database Software

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
ô
¡˚Xí For more information on the latest patch set available for Oracle 10.2 see SAP Note 839187.
ô
¡˚Xí 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.
ô
¡˚Xí You only have to install the latest (that is, the current) patch set.

Procedure
1. Log on as <sapsid>adm user.
2. Install the patch set as described on the patch set README file.
For more information, see SAP Note 839187.
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 Note 839187.
You use OPatch to install the patch collection and the generic patches. For more information, see SAP
Note 839182.

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

Procedure
1. Log on as <sapsid>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


4 Oracle Database Upgrade
4.1 Installing the Oracle Database Software

NOTE

£(±ÊîJ The README file uses the term “bundle patch” instead of “patch collection”.
£(±ÊîJ 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.
£(±ÊîJ If you have an instance-specific exe directory on the central instance host, you install and replicate
the client software automatically with sapcpe on each application server, every time the system
starts:
£(±ÊîJ 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<xx>.sar archive on the central instance as follows:
NOTE

£(±ÊîJ The archive is located on the Oracle 10g Client Software DVD in the directory
OCL_WINDOWS_<platform>.

£(±ÊîJ To unpack the archive, use the latest sapcar.exe program, which you find on the Oracle
RDBMS DVD in the directory: NT\<platform>\SAP.
£(±ÊîJ In mixed environments (32-bit and 64-bit) you have to extract the archive in the respective
directory on both platforms.
£(±ÊîJ If you have an instance-specific exe directory on the central instance host, extract the platform-
specific OCL102<xx>.sar archive to the DIR_CT_RUN [page 51] directory.
Open a command prompt and enter the following commands in a separate line:
cd <path_to_DIR_CT_RUN>
sapcar -xvf <path_to OCL_WINDOWS_<platform>>\OCL102<xx>.SAR

28/58 PUBLIC 2009-08-25


4 Oracle Database Upgrade
4.2 Copying and Adapting the SQL*Net Files

z8õ“˜ë If you do not have an instance-specific exe directory on the central instance host, extract the
platform-specific OCL102<xx>.sar archive to the DIR_EXECUTABLE [page 51] directory.
Open a command prompt and enter the following commands in a separate line:
cd <path_to_DIR_EXECUTABLE>
sapcar -xvf <path_to OCL_WINDOWS_<platform>>\OCL102<xx>.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 <dbsid>adm.
2. Copy the SQL*Net parameter files from the <old_ORACLE_HOME>\network\admin-directory to the
<new_ORACLE_HOME>\network\admin-directory.
3. Edit the listener.ora in the <new_ORACLE_HOME>\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 Manager that guides you through the Network configuration process.
To do this, choose Start All Programs Oracle - <NEW_ORACLE_HOME_NAME>
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
Manager as 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.

2009-08-25 PUBLIC 29/58


4 Oracle Database Upgrade
4.3 Backing Up the Oracle Database

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 to 10.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_<DBSID>.log alert_<DBSID>.log-SV-9.2.0

4.4 Changing the Environment for User <dbsid>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 - <Home_Name> Oracle
Installation Products Universal Installer .
2. In the Welcome screen, choose Installed Products.
3. In the Inventory screen, choose the Environment tab.
4. Deselect all components and choose Apply.
2. In the environment of the user <dbsid>adm, delete the following variables:
«—H�Łå ORACLE_HOME

«—H�Łå 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 <Old_ORACLE_HOME\bin.
4. Set the database parameter JOB_QUEUE_PROCESSES = 0.

30/58 PUBLIC 2009-08-25


4 Oracle Database Upgrade
4.5 Performing the Database Upgrade

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 Note 905279.
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 Administrator make sure that the database disks are online on the first MSCS node.

1. Stop the SAP system.


2. Change the registry entry of ORA_<DBSID>_AUTOSTART as follows:
Enter the command:
oradim -edit –sid <dbsid> –startmode manual
3. Start the Oracle Database Upgrade Assistant from the Start menu with:
Start All Programs Oracle - <NEW_ORACLE_HOME_NAME> 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 Next or 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:
Kçé¯fil If you are asked, to resize the rollback segment
SYSTEM, choose Continue.
Kçé¯fil If there is not enough space for the SYSTEM
tablespace, increase the space.
2. Choose Next.

2009-08-25 PUBLIC 31/58


4 Oracle Database Upgrade
4.5 Performing the Database Upgrade

Screen Input
DUA: SYSAUX Tablespace NOTE
N¤øuNV 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 <drive>:\….\sapdata1\system_1
\sysaux01.dbf into <drive>:\sapdata1\sysaux_1
\sysaux.data1
Make sure that there is enough space on the specified
disk.
N¤øuNV 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 OK to 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


5 Post-Upgrade Steps
5.1 Creating the Oracle TNSListener Service

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. You perform 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:
<complete_path_to_new_Oracle_Home>\bin\lsnrctl start

5.2 Changing Environment Variables


Procedure

NOTE

MSCS only: Edit the variables on all MSCS nodes.

2009-08-25 PUBLIC 33/58


5 Post-Upgrade Steps
5.3 MSCS Only: Setting Up a Shared Database Directory in Oracle Home

1. In the user environment and system environment <SAPSID>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
<SAPSID>adm user.
2. In the user environment of <SAPSID>adm, set the ORACLE_HOME variable to the correct value for
Oracle 10g, for example to: <DRIVE>:\ORACLE\PRD\102.
3. If you have two or more co-existing Oracle Homes, make sure that the user environment variable
PATH of the <SAPSID>adm user points to the corresponding %Oracle_Home%\bin-directory.
4. Copy tnsnames.ora and sqlnet.ora from %ORACLE_HOME%\network\admin to \\<sapglobalhost>
\sapmnt\<SAPSID>\SYS\profile\oracle.

NOTE

This 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 variable TNS_ADMIN to point to the directory \\<sapglobalhost>\sapmnt
\<SAPSID>\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 in


Oracle 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:
—ÐˇpmV You can also use sqlplus remotely to make changes to your profile parameters
—ÐˇpmV 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<DBSID>.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<DBSID>_OFS.ora file, and specify it when adding the database to the cluster resource
group [page 42].

34/58 PUBLIC 2009-08-25


5 Post-Upgrade Steps
5.3 MSCS Only: Setting Up a Shared Database Directory in Oracle Home

Prerequisites
You have one of the following executables available:
t˜ºA 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.
t˜ºA junction.exe
You can download this file from www.sysinternals.com.
Search for junction.

Procedure
1. 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\* <path to_sapdata1>\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:
t˜ºA For junction, enter:
<path_to_junction.exe> %Oracle_Home%\database <complete_path_to_sapdata1>
\database

t˜ºA For linkd, enter:


<path_to_linkd.exe> %Oracle_Home%\database <complete_path_to_sapdata1>
\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<DBSID>_OFS.ora in the database directory, and enter the following
line:
spfile = <path_to_Oracle_Home>\database\SPFILE<DBSID>.ora

2009-08-25 PUBLIC 35/58


5 Post-Upgrade Steps
5.4 Changing the Registry Value of Oracle Autostart

NOTE

If the file init<DBSID>_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 <dbsid> -startmode manual

NOTE

Make sure that you use oradim of Oracle 10.2.

NOTE

If you have several Oracle Homes, ORA_<DBSID>_AUTOSTART, is available in one Oracle Home only.
Set the value for ORA_<DBSID>_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 of OracleService<DBSID> and
Oracle<ORACLE_HOME_NAME>TNSListener to automatic to ensure that they are automatically restarted
after booting. For more information on how to start services, see Starting or Stopping Services [page 50].

CAUTION

MSCS only:
Set the startup type of OracleService<DBSID> and Oracle<ORACLE_HOME_NAME>TNSListener to
manual to ensure that they are not automatically restarted after booting.

5.6 Updating BR*Tools


You 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:
http://service.sap.com/swdc
2. Unpack BR*Tools to the DIR_CT_RUN [page 51] directory.

36/58 PUBLIC 2009-08-25


5 Post-Upgrade Steps
5.7 Deleting the Old Oracle Software

NOTE

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


˙+§S DIR_CT_RUN [page 51] on one MSCS node only.
˙+§S %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<DBSID>.sap and init<DBSID>.utl from the <old_ORACLE_HOME>\database directory
to the new one:
cd <old_ORACLE_HOME>\database
copy init<DBSID>.sap %ORACLE_HOME%\database
copy init<DBSID>.utl %ORACLE_HOME%\database (this file is only available only if you use a 3rd
party backup solution)
NOTE

˙+§S init<DBSID>.dba is no longer needed because BR*Tools release 6.40 SAPDBA is no longer
available.
˙+§S The init<DBSID>.utl file is only available if you use external backup software based on
a backint interface.
4. Update the SAPDBA role as <dbsid>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:
˙+ü‡š±¢ˆ–+6Ó×ëëı˘-.ë~HkÙK“,ïÃ_>ýtÓ¦˛¥V⁄O°/º

sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>


˙+ö‡š¹¢C–d6Ã×°ëÖ0-ë˜H]Ù—“"
˙+ü‡š±¢ˆ–+6Ó×ëëı˘-.ë~HkÙK“,ïÃ_>ý�Ó–˛™V¶O°/º

sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>DB


˙+ö‡š¹¢C–d6Ã×°ëÖ;-+ë(HlÙ—“"

NOTE

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


CAUTION

Make sure that you execute the commands for every SAPSCHEMA_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


5 Post-Upgrade Steps
5.7 Deleting the Old Oracle Software

CAUTION

ßÆˇ5ù™ 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.
ßÆˇ5ù™ 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
<SAPSID>adm and SAPService<SAPSID>. 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 Cluster Service 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 Start menu as follows:
ßÆˇ5ù™ If you find the Universal Installer under Start All Programs <New_Oracle_Home_Name> Oracle
Installation Products Universal Installer , you must start it from this path.
ßÆˇ5ù™ 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 <DVD-DRIVE>:\NT\<platform>
\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


5 Post-Upgrade Steps
5.8 Backing Up the Database

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 <service_name>
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<DBSID>. 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 Start menu, as follows:
1. Choose Start All Programs
2. Right-click Oracle – <OLD_ORACLE_HOME_NAME> 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<n> 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 <dbsid>adm user:
sqlplus /nolog
SQL>connect / as sysdba
SQL> alter system set compatible='10.2.0' scope = spfile;

2009-08-25 PUBLIC 39/58


5 Post-Upgrade Steps
5.9 Performing Post-Upgrade Tasks

2. Restart the Oracle database.


3. Deactivate the Oracle recycle bin by executing the following SQL command as the <dbsid>adm
user:
SQL> purge dba_recyclebin;
SQL> alter system set recyclebin = 'off' scope = spfile;
For more information, see SAP Note 838982.
4. Gather Oracle optimizer statistics as follows:
1. Execute the following commands as the <dbsid>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 <dbsid>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 Note 830576 and adjust them if necessary.
You can find an automated script in SAP Note 1171650 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<SAPSCHEMA_ID>/<password>

40/58 PUBLIC 2009-08-25


5 Post-Upgrade Steps
5.10 Creating the orapwd File

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<DBSID>.ora file with the following command:
orapwd file=%Oracle_Home%\database\pwd<DBSID>.ora password=<pwdFilePassword>
entries=100 force=y
Enter a password for <pwdFilePassword>.
3. Stop and restart the Oracle database.
4. To allow a database user, for example sap<sapsid>, or a system to connect to the Oracle database
as 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 <dbusername>;
SQL>grant sysoper to <dbusername>;

2009-08-25 PUBLIC 41/58


5 Post-Upgrade Steps
5.11 MSCS Only: Adding the Database to the Cluster Group

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 Administrator and bring the Oracle Services for MSCS resource online.
3. Start the Oracle services.
4. Start the database.
5. Start the Oracle Fail Safe Manager with Start All Programs Oracle - <Fail_Safe_Home_Name> 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 Cluster shows 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<DBSID>.
1. In the tree on the left, choose Nodes <First MSCS Node> Standalone Resources .
2. Select the database <DBSID>.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<DBSID>.
9. Choose Next.
10. In the dialog box Add Resource to Group – Database Identity:, enter the following information:
Service Name <DBSID>.world

Instance Name <DBSID>

Database Name <DBSID>

Parameter File <DRIVE>:\<ORACLE_HOME>\database\init<DBSID>_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.

42/58 PUBLIC 2009-08-25


5 Post-Upgrade Steps
5.12 Changing the Location of the JDBC Driver

14. In the dialog box Finish Adding the Database to the Group, choose OK to add the database resource to the
group.
15. In the dialog box Confirm Add database to Group, choose Yes.
The Adding resource <DBSID>.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 \\<sapglobalhost>\sapmnt
\<SAPSID>\SYS\profile\oracle.
17. On the additional MSCS node, set the user environment variable TNS_ADMIN to point to the
directory \\<sapglobalhost>\sapmnt\<SAPSID>\SYS\profile\oracle.
®jþì�£ ÇÍ—?Ç;6‰¶k!)ẃunfis8“˚K• 0yæ±I@�Œfl˝Â˛−ü‹ÕZZcflù¢Ä‰c=JÏnàq_*?¥ÄüÛý&"'ÕJ _Ë·c9½˚

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:
®jþû5" In files that are located in the database you use the J2EE Engine Config Tool to change the JDBC
driver location.
®jþû5" In files that are not located in the database you use Note Pad or another text editor to change the
JDBC driver location.

CAUTION

®jþû5" Make sure when you change the driver location that you use a forward slash "/" or backward
slash "\" as appropriate.
®jþû5" 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:
®jþû5" ®jþì�£ ÇÍ—?Ç;6‰¶k!)ẃunfis8“˚K•0ZæƒIq��Œ¢

/usr/sap/<SAPSID>/JC<instance_number>/j2ee/configtool
®jþ˚ì�« XÇIÍfl?œ;z‰Łk$)·º†u¡fi}

®jþû5" ®jþì�£ ÇÍ—?Ç;6‰¶k!)ẃunfis8“˚K• 0yæ±I@�Œfl˝Â˛−ü‹ÕZZcflù¢Ä‰c=QÏeàt_8?éÄŁÛÒ&æ'Í

/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool
®jþ˚ì�« XÇIÍfl?œ;z‰žk)•º°u*fiK8Ö˚˛•+0æºIq�IŒ¿˝…˛½ü“ÕZflѢ܉¢=
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:
<drive>:\\usr\\sap\\<SAPSID>\\JC<instance_number>\\exe\
\<java_class_archive>.jar (if it exists) or:

2009-08-25 PUBLIC 43/58


5 Post-Upgrade Steps
5.12 Changing the Location of the JDBC Driver

<drive>:\\usr\\sap\\<SAPSID>\\SYS\\exe\\run\\<java_class_archive>.jar
where <java_class_archive>.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 Edit mode to replace the driver location in the following property sheets that contain
the string rdbms.driverLocation= followed by the driver location:
*ÿñõø9 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 several
IDXXXXXX.JavaParameters properties in the property sheet.

*ÿñõø9 cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager

*ÿñõø9 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 the J2EE Engine - ConfigTool.
3. Change to the bootstrap.properties file, which is located in the following directory:
*ÿñõø9 *ÿñˆÝ÷â¾ÝÎHó½(ÑxÀ¥îœ ù¥ B„Ê¡*%ô ºdBflT‹šmk—Y

/usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/bootstrap
*ÿñÝ÷â¶ÝŠH_ó�(−x„¥Íœ%ùD¥ BCʯ

*ÿñõø9 *ÿñˆÝ÷â¾ÝÎHó½(ÑxÀ¥îœ ù¥ B„Ê¡*%ô ºoB·T&‹¬mà—oIÖ!´ fi/¸]iê{qŠÆºó�˙˜»‹N©a”±œÏ°3

/usr/sap/<instance_ID>/DVEBMGS<instance_number>/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:
<drive>:\\usr\\sap\\<SAPSID>\\JC<instance_number>\\exe\
\<java_class_archive>.jar (if it exists) or:
<drive>:\\usr\\sap\\<SAPSID>\\SYS\\exe\\run\\<java_class_archive>.jar

CAUTION

If you have more than one J2EE Engine server installed, you must repeat steps 2 and
3 for all servers.
*ÿñÝ÷â¶ÝŠH_ó�(−x„¥Æœùs¥=BÈÊŽ*~ôvºOBÎT-‹šm½—DIŠ´%fip¸v]AêcqVÆæ
4. Change to the sdmrepository.sdc file, which you can find in the following directory:
*ÿñõø9 *ÿñˆÝ÷â¾ÝÎHó½(ÑxÀ¥îœ ù¥ B„Ê¡*%ô ºdBflT‹šmk—Y

/usr/sap/<SAPSID>/JC<instance_number>/SDM/program/config/
*ÿñÝ÷â¶ÝŠH_ó�(−x„¥Íœ%ùD¥ BCʯ

44/58 PUBLIC 2009-08-25


5 Post-Upgrade Steps
5.13 Upgrading the SAP Executables to the Latest Version

0— ¶º½ 0— Y�s$fiªı±|áSw˜%-
At;ˆ;ý¬^ÎÊsÜ+ gꩺ˙èI÷.˛õ›¶W×Ã}µãÊlàÌ’›=¢;½ò–9A˜yqÆìd¹

/usr/sap/<SAPSID>/DVEBMGS<instance_number>/SDM/program/config/
1. Search for the following text:
<Param type="String" hide="false" name="jarPaths" encrypted="false"
displayName="Driver Paths (separated by ;)">
2. If required, replace the old driver location with the new one, such as one of the following:
<drive>:\<Oracle_Home>\jdbc\lib\<java_class_archive>
<drive>:\\usr\\sap\\<SAPSID>\\JC<instance_number>\\exe\
\<java_class_archive>.jar (if it exists), or:
<drive>:\\usr\\sap\\<SAPSID>\\SYS\\exe\\run\\<java_class_archive>.jar
0— S�s$łªÃþ|ñS,˜i-"AR;{;ˬˆÎòs⁄+vgÊ©Ã˙ãIÆ.@õ¢¶×5Æ}šµ—ÊDàÔ’H=þ
5. Change to the rdb.properties file, which is located in the following directory:
/usr/sap/<SID>/<INSTANCE>/j2ee/deploying
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:
<drive>:\\usr\\sap\\<SAPSID>\\JC<instance_number>\\exe\\classes12.jar (if it
exists), or:
<drive>:\\usr\\sap\\<SAPSID>\\SYS\\exe\\run\\<java_class_archive>.jar
6. Change to the templateconfigurator.properties file, which is located in the following directory:
/usr/sap/<SID>/<INSTANCE>/j2ee
1. Open the file with your text editor and search for the property RDBMS_DRIVER_LOCATION.
2. Replace the old driver location with the new one:
<drive>:\\usr\\sap\\<SAPSID>\\JC<instance_number>\\exe\
\<java_class_archive>.jar (if it exists), or:
<drive>:\\usr\\sap\\<SAPSID>\\SYS\\exe\\run\\<java_class_archive>.jar
0— S�s$łªÃþ|ñS,˜i-"AR;{;ˬˆÎòs⁄+vgÊ©Ã˙ãIÆ.@õ¢¶ ×>Ã}‘µÈÊ-àû’„=æ;Ñòï–3̘:

5.13 Upgrading the SAP Executables to the Latest Version


Procedure
Before you start your SAP system [page 52], make sure that you have applied the latest available packages
for:
0— ¶º½ disp+work

0— ¶º½ libdbsl

0— ¶º½ sapcpe

2009-08-25 PUBLIC 45/58


5 Post-Upgrade Steps
5.14 Disabling Database User Locking Mechanism For Failed Logins

5.14 Disabling Database User Locking Mechanism For Failed


Logins
When upgrading an Oracle database to Oracle version 10g, user locking is automatically activated so
that, if you repeatedly enter invalid login information, the user is locked. By default, ten invalid login
attempts are allowed before the user is locked. Since old SAP systems first try to log in with a standard
user (sapr3) and password, this locking mechanism might lock the user when starting the system.
For more information, see SAP Note 951167.

Procedure
To deactivate user locking after invalid logon attempts, enter the following information in sqlplus:
sqlplus /nolog
sql>connect / as sysdba
sql>ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;
sql>exit

5.15 Checking the National Character Set


If your database still runs with a national character set (NLS_NCHAR_CHARACTERSET) different
from UTF8, you need to change it to UTF8. You can expect to experience severe problems during SAP
upgrades if the database national character set is not set to UTF8. If you already use a Java system or
plan to use one in the future, the national character set must be UTF8.

Procedure
If necessary, follow SAP Note 669902 to change the national character set to UTF8.

5.16 Configuring the New Features for Oracle Database 10g


Release 2 (10.2)
You need to configure the new Oracle Database 10g Release 2 (10.2) features.

Procedure
For more information about new features with Oracle Database 10g Release 2 (10.2) see SAP Note
828268. This note provides links to other SAP notes that describe how to configure or activate each new
feature.

46/58 PUBLIC 2009-08-25


6 Common Administration Tasks
6.1 Starting and Stopping the Database

6 Common Administration Tasks

The following sections provide information on common administration tasks that have to be performed
repeatedly during the upgrade procedure. Some of these tasks are standard tasks, others are only
relevant for a Microsoft Cluster Service (MSCS) configuration.
ÞÑÅñ�ô Starting and stopping the database [page 47]
ÞÑÅñ�ô Checking Oracle services [page 49]
ÞÑÅñ�ô Starting and stopping services [page 50]
ÞÑÅñ�ô Changing or deleting Oracle database parameters [page 51]
ÞÑÅñ�ô Determining the value of SAP system profile parameters [page 51]
ÞÑÅñ�ô Moving groups for MSCS [page 52]
ÞÑÅñ�ô Starting and stopping the SAP system [page 52]

6.1 Starting and Stopping the Database


The following sections provide information on:
ÞÑÅñ�ô Starting and stopping the database in a standard configuration [page 47]
ÞÑÅñ�ô Starting and stopping the database in an MSCS configuration [page 48]

6.1.1 Starting and Stopping the Database in a Standard


Configuration
In a standard configuration you use sqlplus to start or stop the database.

Procedure
Enter the following commands in sqlplus:
ÞÑÅñ�ô To start the database, enter:
sqlplus /nolog
SQL>connect / as sysdba
SQL>startup
SQL>exit

ÞÑÅñ�ô To stop the database, enter:


sqlplus /nolog
SQL>connect / as sysdba
SQL>shutdown immediate

2009-08-25 PUBLIC 47/58


6 Common Administration Tasks
6.1 Starting and Stopping the Database

SQL>exit

6.1.2 Starting and Stopping the Database in an MSCS


Configuration
This section describes how to start or stop the database in an MSCS configuration.
You have the following options
ĺØüu You use sqlplus
You use this option if:
ĺØüu� The database disks are online and the OracleService<DBSID> is started.
ĺØüu� You start the database in a certain mode, for example you use the commands startup
upgrade or startup migrate during an upgrade or a migration.

NOTE

If want to start the database in a certain mode (for example, you use the commands startup
migrate, startup upgrade, startup nomount, or if you have installed a patch set or patch
collection), perform the following steps:
1. In the Oracle Fail Safe Manager, right-click the database <DBSID>.world in the cluster
group ORACLE<DBSID>.
2. Choose Place offline.
3. Choose the specific modus.
4. On the node, where the Oracle group is partially online, start the service
OracleService<DBSID>
5. Perform administrative tasks including start up or shutdown
6. In the Oracle Fail Safe Manager, take the cluster resource <DBSID>.world online.
For more information on how to start and stop your database with sqlplus, see Starting and Stopping the
Database in a Standard Configuration [page 47].
ĺØüu You use the Oracle Fail Safe Manager
You use this option, if the database is under control of the Oracle Fail Safe Manager.
CAUTION

If the Oracle database resource is online, you must use the Oracle Fail Safe Manager to stop
the database. If you do not use the Oracle Fail Safe Manager, the cluster functionality
automatically attempts to restart the database.

Prerequisites
You are logged on as user <SAPSID>adm.

Procedure
The following procedure describes how to start and stop the database with the Oracle Fail Safe Manager.

48/58 PUBLIC 2009-08-25


6 Common Administration Tasks
6.2 Checking Oracle Services

ı¸k/ˇÀ Starting the database


1. In the Oracle Fail Safe Manager, right-click the database <DBSID>.world in the cluster group
ORACLE<DBSID>.
2. Choose Place online.
ı¸k/ˇÀ Stopping the database
1. In the Oracle Fail Safe Manager, right-click the database resource <DBSID>.world in the cluster
group ORACLE<DBSID>
2. Choose Take offline.
NOTE

If a pop-up appears, asking you how to take the database offline, choose Immediate.

6.2 Checking Oracle Services


This section describes how to check the status of the Oracle services.

Oracle Services

The following services are available in an Oracle 10g installation:


ı¸k/ˇÀ Oracle<Oracle_Home_Name>iSQL*Plus
ı¸k/ˇÀ OracleService<DBSID>
ı¸k/ˇÀ OracleCSService
ı¸k/ˇÀ OracleDBConsole<DBSID>
ı¸k/ˇÀ OracleJobScheduler<DBSID>
ı¸k/ˇÀ Oracle<Oracle_Home_Name>TNSListener
ı¸k/ˇÀ Oracle<Oracle_Home_Name>SNMPPeerEncapsulator
ı¸k/ˇÀ Oracle<Oracle_Home_Name>SNMPPeerMasterAgent
ı¸k/ˇÀ MSCS only: OracleMSCSServices
ı¸k/ˇÀ MSCS only: Oracle<Oracle_Home_Name>TNSListenerFsl<virtual DB host name>

Procedure
To check the status of an service, perform the following steps:
1. Choose Start All Programs Administrative Tools Services
2. Double-click on the required service.
ı¸k/ˇÀ The Status column shows whether a service has been started.
ı¸k/ˇÀ The Startup Type column shows whether a service is started automatically after booting or
whether it has to be started manually.
ı¸k/ˇ¯ To change the startup type, right-click Properties. Select the General tab and choose the
startup type from the dropdown box.
ı¸k/ˇ¯ To change the user that is assigned to a service, select the Log On tab and make the
appropriate entries.

2009-08-25 PUBLIC 49/58


6 Common Administration Tasks
6.3 Starting and Stopping Services

6.3 Starting and Stopping Services


This section describes how to stop services in a standard configuration and in an MSCS configuration.

Procedure

Starting and Stopping Services in a Standard Configuration

1. Right-click on My Computer and choose Manage.


2. Double-click on Services and Applications and select Services.
3. Right-click on the service you want to start or stop.
4. Choose Start or Stop as required.

Starting and Stopping Services in an MSCS Configuration

ª÷ûSF Starting or Stopping the Cluster Service with the Cluster Administrator
1. Start the Cluster Administrator.
2. Select the node where you want to start or stop the Cluster Service.
3. To stop the cluster service, choose File Stop Cluster Service.
4. To start the service, choose File Start Cluster Service
ª÷ûSF Starting and Stopping Services with the Cluster Administrator or Fail Safe Manager
You can start or stop the services listed in the table below with the Cluster Administrator or Fail Safe
Manager.
To start a resource, set it online. To stop a resource set it offline.
CAUTION

If during the migration process the Cluster Service is stopped, you cannot use the Fail Safe
Manager or Cluster Administrator to stop services. In this case, you have to stop them as described
above under Starting and Stopping Services in a Standard Configuration.
However, when the Cluster Service is running, you must use the Cluster Administrator or Fail Safe
Manager, otherwise the cluster functionality automatically attempts to restart the services you
have stopped.
The following table shows how to start the services.
Service Resource
SAP<SAPSID>_<Instance_No.> Set the SAP cluster resource to online. The SAP
system is started.
OracleService<DBSID> Choose one of the following:
ª÷ûS) Set the resource <DBSID>.world in the group
ORACLE<DBSID> to online.
ª÷ûS) In the Oracle Fail Safe Manager, set the Fail Safe
Database <DBSID>.world to online.
Oracle<Oracle_Home_Name>TNSListenerFsl<virtual DB Set the corresponding resource in the group
host name> ORACLE<DBSID> to online.
OracleMSCSServices Set the resource Oracle Services for MSCS in the Cluster
group to online.

50/58 PUBLIC 2009-08-25


6 Common Administration Tasks
6.4 Changing or Deleting Oracle Database Parameters

6.4 Changing or Deleting Oracle Database Parameters


Depending on the configuration of the Oracle database, you must use one of the following files to
change or delete the Oracle database parameters:
_˝ë× If your database is not configured for using a spfile you use the init<DBSID>.ora file.
_˝ë× If your database is configured for using a spfile you use the spfile.

Procedure
1. Check the configuration of your Oracle database with the following sqlplus commands:
sqlplus /nolog
SQL>connect / as sysdba
SQL>show parameter spfile
2. Check the value of the spfile parameter and perform one of the following steps:
_˝ë× If the value of the parameter spfile is empty, your database is not configured for using a spfile.
Edit the init<DBSID>.ora file to change the parameters.
_˝ë× If a value for the parameter spfile is displayed, your database is configured for using a spfile.
Change the parameters in the spfile as follows:
_˝ë×z To set the parameter, enter one of the following:
_˝ë×s If <parameter_value> consists of a string, for example 10.2.0, enter:
SQL> alter system set <parameter_name>=’<parameter_value>’ scope =
spfile;

_˝ë×s Otherwise enter:


SQL> alter system set <parameter_name>=<parameter_value> scope =
spfile;
NOTE

To find out if your parameter value is a string or a number, use the command:
show parameter <parameter_name>

_˝ë×z To delete a parameter, enter:


SQL> alter system reset <parameter_name> scope = spfile sid = '*';

NOTE

If you get an error during the ‘alter system reset’ command like ORA-32010 : cannot
find entry to delete in SPFILE, you can ignore it, as it only indicates that the
entry did not exist in the SPFILE.

6.5 Determining the Value of SAP System Profile Parameters


This section describes how to determine the value of SAP system profile parameters, for example of
DIR_CT_RUN and DIR_EXECUTABLE.

2009-08-25 PUBLIC 51/58


6 Common Administration Tasks
6.6 Moving Groups for MSCS

Procedure
The following procedure shows an example how to determine the value of the DIR_CT_RUN parameter.
To find out the value of DIR_CT_RUN, do one of the following:
fÚl‡ÉÎ If your SAP system is started, use transaction SE38.
Run report rsparam and search for the parameter DIR_CT_RUN.
fÚl‡ÉÎ If your SAP system is not started, open a command prompt and enter: sappfpar
pf=<full_path_to instance_profile> DIR_CT_RUN

6.6 Moving Groups for MSCS


You can use the Cluster Administrator or the Fail Safe Manager. This sections describes the procedure for
both.

Procedure

Moving Groups with the Cluster Administrator

Use the Cluster Administrator for groups that do not belong to the Oracle database groups:
1. Start the Cluster Administrator with Start < Settings> Control Panel Administrative Tools Cluster
Administrator.
2. On the left-hand pane, under Groups right-click the cluster group you want to move.
3. Click Move group on the context menu.
The group is now moved to another node.

Moving Groups with the Fail Safe Manager

Use the Fail Safe Manager to move the Oracle resources, for example, the database group
Oracle<DBSID>:
1. Start the Fail Safe Manager 3.3.4 with Start All Programs Oracle <Home_Name_fail safe> Oracle Fail
Safe Manager
2. On the left-hand pane, select the group you want to move.
3. Press the right mouse button and click Move to a Different Node on the context menu.
The group is now moved to another node.

6.7 Starting and Stopping the SAP System


This section describes how to start or stop an SAP system in a:
fÚl‡ÉÎ Standard Configuration
fÚl‡ÉÎ Microsoft Cluster Service (MSCS) Configuration
If you use MSCS, you start or stop your SAP system with one of the following tools:
fÚl‡É¡ The SAP Microsoft Management Console (SAP MMC)

52/58 PUBLIC 2009-08-25


6 Common Administration Tasks
6.7 Starting and Stopping the SAP System

L|‰˝˙ù The Cluster Administrator

Procedure

Starting and Stopping the SAP System in a Standard Configuration

For a standard configuration, you use the SAP Microsoft Management Console (SAP MMC) to start or stop
your SAP system. With a newly installed MMC you can start or stop installed SAP instances locally on
the host that you are logged on to. If the MMC is configured for central system administration, you
can start the entire system from a single host. To stop the system, you first have to stop all dialog
instances before you can stop the other instances. For more information on the start or stop order of
an SAP system, see SAP Note 897933.

NOTE

When you boot the Windows operating system in a standard configuration, the SAP Service
SAP<SAPSID>_<Instance_number> (for example SAPPRD_00) is always started automatically.

Perform the following steps:


1. Start the SAP MMC on the SAP system host by choosing Start All Programs SAP Management
Console.
2. Right-click the SAP system node and choose Start or Stop.
All instances listed under the system node, will start or stop in the correct order.
3. If the SAP system is installed on multiple hosts (distributed system), you have the following options
to start or stop your system:
L|‰˝˙Œ You start or stop the SAP instances using the SAP MMC on each host.
L|‰˝˙Œ You add the remote instances to the MMC configuration to start or stop all instances from a
single MMC.
To do so, do one of the following:
L|‰˝˙ù You configure the SAP MMC manually. For more information, see Changing the Configuration
of the MMC in the MMC documentation.
L|‰˝˙ù You use the automatic LDAP registration. For more information, see Configuring MMC
for Active Directory Service in the MMC documentation.

Starting and Stopping the SAP System in an MSCS Configuration

In an MSCS configuration, you start or stop your SAP system using one of the following options:
L|‰˝˙Œ The SAP Microsoft Management Console (SAP MMC)
To start or stop your SAP system with the SAP MMC, see above.
L|‰˝˙Œ The Cluster Administrator
L|‰˝˙ù To start the SAP system with the Cluster Administrator, open the Cluster Administrator and set the
SAP cluster resource in the SAP cluster group online.

2009-08-25 PUBLIC 53/58


6 Common Administration Tasks
6.7 Starting and Stopping the SAP System

yÅßæ‘ To stop the SAP system with the Cluster Administrator, set the SAP cluster resource in the SAP
cluster group offline.

54/58 PUBLIC 2009-08-25


SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2009 SAP AG. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany
and in several other countries all over the world. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.

Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or
altered in any way.

2009-08-25 PUBLIC 55/58


Documentation in the SAP Service Marketplace
You can find this document at the following address: https://service.sap.com/instguides

56/58 PUBLIC 2009-08-25


SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2009 SAP AG. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.