upg920_60_11may04

8/3/2019 upg920_60_11may04

http://slidepdf.com/reader/full/upg9206011may04 1/43

Database Upgrade Guide

Upgrade to Orac le9 i

Vers ion 9.2.0 on

Windows

Document Vers ion 1 .70 – May 11 t h, 2004

8/3/2019 upg920_60_11may04


© Copyright 2004 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.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,

Tivoli, and Informix are trademarks or registered trademarks of IBM

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, a

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 ot

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 materia

are provided by SAP AG and its affiliated companies ("SAP Group

for informational purposes only, without representation or warranty

any kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only warranties for SA

Group products and services are those that are set forth in the expre

warranty statements accompanying such products and services, if a

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 expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be u

by SAP’s Support Services and may not be modified or altered in a

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http: / /service.sap.com/instguides

SAP AGNeurottstraße 1669190 Walldorf GermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap .com

8/3/2019 upg920_60_11may04


Typographic Convent ions

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to other documentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded by

body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such

as F2) or the Enter key.

I cons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

8/3/2019 upg920_60_11may04


Upgrade to Oracle9i Version 9.2.0 on Windows

Contents

Upgrade to Oracle9i Release 9.2.0...................................................5 1 Upgrade of the Database Server........................................................7

1.1 New Features..........................................................................................7

1.2 Multiple Oracle Homes........................................................................... 7

1.3 Backing up the Oracle Source Database and SAP System ................ 8

1.4 Setting the NLS_LANG Variable............................................................ 9

1.5 MSCS Only: Removing the Database from the Fail Safe Group....... 10

1.6 MSCS Only: Upgrading to OFS 3.3.2 .................................................. 11

1.7 Installing the Oracle9i Release 9.2.0 Software................................... 14

1.8 Preparing for the Database Upgrade.................................................. 16

1.9 Upgrading the Database...................................................................... 16

2 Post-Upgrade Activities....................................................................19

2.1 Modifying the Oracle Network Configuration .................................... 19

2.2 Configuration Tasks............................................................................. 21 2.2.1 Configuration Tasks for SAP systems below 6.40......................................................21 2.2.1 Configuration Tasks for SAP systems 6.40 and higher..............................................24

2.3 Deleting the old Oracle Software ........................................................28

2.4 Setting Environment Variables ........................................................... 29

2.5 MSCS Only: Configuring Node B ........................................................ 31

2.6 MSCS Only: Adding the Database to the Fail Safe Group ................ 31 2.7 Backing up the Oracle9i Database...................................................... 33

2.8 Upgrade of Database Clients............................................................... 33

3 Common Administration Tasks.......................................................34

3.1 Standard Tasks..................................................................................... 34 3.1.1 Starting sqlplus ...........................................................................................................34 3.1.2 Starting and Stopping the Database...........................................................................35 3.1.3 Starting the Instance Manager....................................................................................35 3.1.4 Oracle Services...........................................................................................................35 3.1.5 Setting the NLS_LANG Variable.................................................................................36 3.1.6 Checking Services ......................................................................................................37 3.1.7 Starting or Stopping Services .....................................................................................37 3.1.8 Starting or Stopping the SAP System.........................................................................37 3.1.9 Updating the Dynamic Link libraries...........................................................................38 3.1.10 Deleting a Registry Entry..........................................................................................38 3.1.11 Setting or Deleting Environment Variables...............................................................38 3.1.12 Creating a Local Group.............................................................................................38

3.2 MSCS Tasks.......................................................................................... 39 3.2.1 Starting Up or Shutting Down the Database for MSCS..............................................39 3.2.2 Services for MSCS......................................................................................................40 3.2.3 Starting and Stopping Services for MSCS..................................................................40 3.2.4 Stopping the Cluster Service ......................................................................................41 3.2.5 Moving Groups for MSCS...........................................................................................42 3.2.6 Starting or Stopping the SAP System for MSCS........................................................43

3.2.7 Backing Up the SAP System for MSCS......................................................................43

8/3/2019 upg920_60_11may04


SAP AG 1 Upgrade of the Database Server

1.1 New Features

May 2004 5

Upgrade to Oracle9i Release 9.2.0Purpose

This documentation explains how to upgrade your database from Oracle version 8.1.7 to Oracleversion 9.2.0. The upgrade must be performed on the database server and any databaseclients that exist on other machines of the system.

If you want to migrate from Oracle version 7.3.4 to 9.2.0, you must first migrate to Oracle 8.1.7according to the instructions in the guide Upgrade or Migration to Oracle8i Release 8.1.7 . Thenyou can upgrade to Oracle 9.2.0 following the instructions in this guide.

Implementation Considerations

A number of factors can influence the upgrade or migration procedure. In the following cases youmust follow additional instructions or refer to other sources of information:

• MSCS Configuration

If your system is configured to run with Microsoft Cluster Server (MSCS) you have to performadditional steps. These are necessary to include the second node of the system in theupgrade procedure and to deal with cluster-specific features. Steps that must be performedfor a cluster configuration are marked with MSCS only in this documentation.

The cluster node that a particular step has to be executed on can be:Node A which is the primary node where the database server is locatedNode B which is the other or secondary node.

• Multiple Homes

When you upgrade, you can choose to either overwrite the old database version or to keep itand to run it in parallel with the new database version. You must decide whether you want torun the old and new version in parallel before you begin the upgrade. For more informationsee Multiple Oracle Homes [Page 7]:

• Windows Domain

The database server and database client must be in the same Windows domain. For information on permitted domain names see SAP Note 314671.

• Important Additional Information

Read the SAP Note 493143 to find out the latest information on the upgrade andany corrections to this guide.

In this documentation, instructions are supplemented by additional information

that is provided in the chapter Common Administrative Tasks . Please refer to thischapter, if you need more detailed instructions for some of the tasks that need tobe performed repeatedly.

8/3/2019 upg920_60_11may04


1 Upgrade of the Database Server SAP AG

1.1 New Features

6 May 2004

Integration

This document focuses on the Oracle upgrade procedure in an SAP environment. For further supplementary information, see the documentation provided by Oracle on the RDBMS CD 1under <CD_ROM_DRIVE>:\NT\I386\DOC

To view the documentation, open the file start_here.htm with a browser.

8/3/2019 upg920_60_11may04



1.1 New Features

May 2004 7

1 Upgrade of the Database Server

Purpose

When you upgrade the database server, you need to perform the actions listed here.

Process Flow

• Decide whether you need multiple Oracle Homes []

• Create an offline backup [Page 8]

• MSCS only: Remove the database from the Fail Safe group [Page 9]

• MSCS only: Upgrade to OFS 3.1.1 [Page 11]

• Install the Oracle9i Release 9.2.0 software [Page 14]

• Prepare the database upgrade [Page 16]

•

Upgrade the database data [Page 16] After the database server upgrade, you need to perform a number of post-upgrade tasks.For more information, see Post-Upgrade Activities [Page 19].

1.1 New Features• For SAP systems 6.40 and higher the database and installation software is available on

DVDs.

• Server Manager svrgmgrl has been replaced with the command-line tool sqlplus.

If you enter sqlplus you are asked to enter your user name and password. To

avoid this and to have the same behavior as with the previous commandsvrmgrl, enter the following to start the database administration tool:sqlplus /nolog

If you have your own scripts using svrgmgrl that connect to the database, you

need to rewrite these accordingly: Replace the previous command svrmgrl

command=@<sql_file_name> with sqlplus /nolog @<sql_file_name>.

• User internal no longer exists in Oracle9i. To connect to the database, use:

connect / as sysdba

You can not longer use:

connect internal/<password>.

1.2 Multiple Oracle HomesBefore the upgrade or migration, you need to decide whether you want to set up multiple Oraclehomes as this influences the procedure.

Oracle allows multiple Oracle homes for specific database versions. This means that more thanone version of the database software can exist in different home directories on the same host.

8/3/2019 upg920_60_11may04



1.3 Backing up the Oracle Source Database and SAP System

8 May 2004

MSCS only:Multiple Oracle homes for different database instances are not supported in aMSCS configuration.

During the upgrade or migration there are temporarily two Oracle homes.However, the old home is deleted at the end of the migration or upgradeprocedure.Note however that the Oracle Failsafe software is installed in its own OracleHome.

Multiple Oracle homes are necessary:

• If two different databases or database clients are installed on the same computer and thesedatabases or database clients use different Oracle releases that cannot be installed in asingle Home directory.

• If a migration or upgrade to Oracle 8.1.x or 9i is being performed, the new Oracle softwaremust be installed in a new Oracle home directory.

RestrictionsNote the following restrictions regarding the installation of different Oracle versions in a singleOracle Home:

• Only one Oracle7 release can be installed in the same Oracle Home as an Oracle 8.0*release

• Oracle 8.0.5 and Oracle 8.0.6 cannot be installed in a single Oracle Home due to thedirectory structure.

• All Oracle releases prior to 8.0.5 can only be installed in the first Oracle Home that is thedefault home.

1.3 Backing up the Oracle Source Database andSAP System

Use

To protect your database and system against any unforeseen damage that may occur during themigration or upgrade procedure, it is essential to make a full offline backup before you begin. Thebackup ensures that you can restore the original system if anything goes fundamentally wrong inthe course of the migration.

Procedure

1. Use regedit to create a backup of the registry entries under

HKEY_LOCAL_MACHINE → Software → Oracle HKEY_Current_User → Environment

2. Create backups of the Oracle source version environment, the database files, the SAPinstance (\usr\sap...) and the Windows system directories.

If you can recover to this point, you do not need to make a backup of the database files.

Save the following file trees:

8/3/2019 upg920_60_11may04



1.4 Setting the NLS_LANG Variable

May 2004 9

Directory Explanation Tool

\ORACLE Save the database(not on a database client)

SAP tool BRBACKUP

\<ORACLE_HOME> Save the Oracle software NTBACKUP

\USR\SAP

\USERS Save the SAP software NTBACKUP

%windir% Save the Windows system NTBACKUP

Note that the above file trees are normally distributed on several disks. Use the Verify option, which is offered by both BRBACKUP and NTBACKUP, to check your tape after saving.

MSCS only:

For information on additional directories that have to be backed up in a cluster see:Backing Up the SAP System for MSCS [Page 43].

To be able to use extended backup functions, such as the incremental backup,you need to install one of the following backup libraries:

• SAP Backup Library

• Legato Storage Manager

• Backup tool of another vendor that implements the backup interface of theOracle Recovery Manager.

Backup libraries are optional and can be installed at any time after the Oraclemigration. For more information and instructions on installing the Legato StorageManager, see SAP Note 142635.

1.4 Setting the NLS_LANG Variable

Use

Set the NLS_LANG variable in the user environment of <DBSID>adm. The value of NLS_LANG

depends on the value of the Oracle parameter NLS_CHARACTERSET. The following describes

how to determine the value of NLS_CHARACTERSET and then how to derive the value of

NLS_LANG from it.

MSCS only:NLS_LANG must be set on both nodes. It has the same value on both nodes.

8/3/2019 upg920_60_11may04



1.5 MSCS Only: Removing the Database from the Fail Safe Group

10 May 2004

Procedure

1. Find out the value of the Oracle parameter NLS_CHARACTERSET:

a. Log on as user <DBSID>adm

b. At the command prompt, start the Oracle Server Manager or sqlplus with the appropriatestartup command for your Oracle version:

Oracle8 Oracle8.1 Oracle9i

svrmgr30 svrmgrl sqlplus

sqlplus \nolog

sql> connect \ as sysdba

For Oracle version < 9.2.0, enter the following: <SERVER_MANAGER_CALL>

SVRMGR> connect @<DBSID> as sysdba

c. Enter the following command in a single line:

sql> select * from v$nls_parameters where parameter like'NLS_CHAR%';

For Oracle version < 9.2.0, enter the following: SVRMGR> select * from v$nls_parameters where parameter like'NLS_CHAR%';

The value of the parameter NLS_CHARACTERSET is returned.

2. Set the variable NLS_LANG in the Windows user environment of <SAPSID>adm. If you areupgrading or migrating a database client do this on the client machine.

− If NLS_CHARACTERSET has the value WE8DEC, set NLS_LANG toAMERICAN_AMERICA.WE8DEC

− If NLS_CHARACTERSET has the value US7ASCII, set the variable NLS_LANG toAMERICAN_AMERICA.US7ASCII

For more information, see Setting or Deleting Environment Variables [Page 38].

1.5 MSCS Only: Removing the Database from the

Fail Safe GroupUse

In a cluster configuration, you have to remove the SAP database from the Oracle Fail Safe Group before you begin the upgrade.

8/3/2019 upg920_60_11may04



1.6 MSCS Only: Upgrading to OFS 3.3.2

May 2004 11

Procedure

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

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

2. In the Cluster Administrator, move all groups as well as the Cluster group to node A.

3. Log on to the Oracle Fail Safe Manager as the user under which the Cluster Service isrunning.

Choose Groups → Oracle<DBSID> → Cluster Resources and select <DBSID>.world . Clickthe right mouse button and choose Remove from Group .

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 37].

4. In the dialog box Confirm Remove Database from Fail Safe Group , choose Yes .

The Clusterwide operation window displays the steps that are executed to remove thedatabase from the Fail Safe group. The last line informs you that The clusterwide operation completed successfully.

5. In the Clusterwide operation window, choose Close.

6. Exit the Fail Safe Manager .


Use

If the cluster configuration is still running with Oracle Failsafe Software version lower than 3.3.2,you must upgrade to version 3.3.2.

The Oracle Failsafe Service from previous Oracle releases is now calledOracleMSCSServices. You might still see the old name in certain SAP Notes.Be sure to always use the new name OracleMSCSServices.

Procedure

Install Oracle Fail Safe 3.3.2 on a local disk on both nodes. It must be installed inthe same home on both nodes!

1. In the Control Panel , make sure the Cluster Service is running on both nodes.

For more information, see Starting and Stopping Services for MSCS [Page 40]

2. Make sure you are logged on as user <SAPSID>adm.

8/3/2019 upg920_60_11may04




12 May 2004

3. Make sure the Oracle Fail Safe Manager is closed.

4. Uninstall the old OFS software on both nodes before you install OFS 3.3.2.

While you are uninstalling the software on a particular node, do not reboot theother node.

a. Start the Oracle Installer from the FailSafe CD. To do this, double-click sapofs.cmd in

the directory <CD_DRIVE>:\NT\I386

On the RDBMS DVD, the file is located in the directory

<DVD_DRIVE>:\ORAFS332I386.

b. Choose Installed Products .

c. In the Inventory window, expand <Failsafe_Home> and select Oracle FailSafe <version_lower_to 3.3.2>

d. Choose Remove. e. In the Confirmation dialog box, confirm that you wish to delete the selected products.

f. Click Exit to close the Oracle Installer .

5. Install Oracle Fail Safe version 3.3.2:

a. Insert the Oracle Fail Safe CD.

b. Start the Oracle Universal Installer . To do this, double-click the file sapofs.cmd in the

directory <CD_DRIVE>:\NT\I386.

On the RDBMS DVD, the file is located in the directory

<DVD_DRIVE>:\ORAFS332I386.The installer opens and guides you through the installation process in a series of screens.

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.

8/3/2019 upg920_60_11may04




May 2004 13

Screen Entry

Welcome Choose Next.

File Locations Source ...

Path:

The path to the Oracle software on the CD is displayed. Do notchange the path.

Destination ...

Name: Enter the name of the Oracle Home directory for the Fail Safe software. The software must be installed in a separate Oraclehome, for example, Failsafe

Use the same Oracle home for both nodes.

If Oracle Fail Safe version 3.1.1 or 3.3.1 was previouslyinstalled, you can use the old Oracle Fail Safe home for 3.3.2.

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

Available Products Select Oracle Fail Safe 3.3.2.0.0 and choose Next .

Installation types Choose Typical.

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 Fail Safe software is torun. This must be the same account as the one under whichthe Cluster 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 onaccount for the service is displayed. Enter this account for Oracle Fail Safe Account/Password.

End of Installation Click Exit to leave the Installer.

6. Reboot and log on again.

Do not reboot a node, if the installation of OFS 3.3.2 or the deinstallation of earlier releases is in progress on the other node.

8/3/2019 upg920_60_11may04



1.7 Installing the Oracle9i Release 9.2.0 Software

14 May 2004


Use

You install the Oracle 9.2.0 database software.

For Oracle 9.2.0 there are three RDBMS CDs. If you use an RDBMS DVD, they are located in

the directories ORA92_1 to ORA92_3.

During the installation, you are prompted to specify the correct path to CD2 andCD3. To avoid this, you can copy the CDs to disk as follows before theinstallation:

a. Copy the contents of \NT\<OS> on RDBMS CD1 (or ORA92_1\NT\<OS> on

the RDBMS DVD) to \disk1 on your hard disk.

b. Repeat this for the second and third CD.

\disk1 to \disk3 can be on a network drive if required

• When you have installed the database software, you have to in installthe current Oracle patch set and hot fix, if available. For moreinformation, see SAP Note 578683.

• MSCS only: Install the Oracle 9.2.0 software, patch set and hot fix (if available)on both nodes.

You must run different files to install the client and the server software.

Procedure

1. Start the Oracle Universal Installer as follows:

• Place the Oracle RDBMS CD1 in the CD drive and start from:

<CD_DRIVE>:\NT\<OS>

If you use an RDBMS DVD, place the Oracle RDBMS DVD in the DVD drive andstart from <DVD_DRIVE>:\ORA92_1\NT\<OS>

• If you have copied the CDs to disk, start from \disk1

On the database server, double-click the file sapserver.cmd

On the database client double-click the file sapclient.cmd

2. Enter the information as shown in the table below.

8/3/2019 upg920_60_11may04




May 2004 15

• 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. Make sure that these variables in

the user environment of <DBSID>adm refer to existing files. If not,reset them.

• If during the installation an error is reported when writing to a DLL file,the DLL has the read-only attribute. In this case, before you continuethe installation, open a command prompt and remove the read-onlyattribute with the command:attrib –r <DRIVE>:\%windir%\system32\<DLL>

To view attributes enter:attrib <DRIVE>:\%windir%\system32\<DLL>

Window Entry

File Locations Under Source :

For Path :

Shows the path to the Oracle source software. Do not change thepath.

Under Destination :

For Name:

Enter the name of the new Oracle Home directory. Werecommend that you use the name<SAPSID><ORACLE_VERSION>, for example, C11920

For Path Enter the path of a new Oracle Home directory. We recommendthat you use the path:

<DRIVE>:\ORACLE\<DBSID>\<ORA_VERS>, for example,

C:\ORACLE\C11\920

Do not specify an already existing Oracle Homedirectory. You must specify a new directory.You need 2.2 GB disk space for the Oracle 9.2.0server software and about 250 MB for the Oracle9.2.0 client software

Choose Nex t.

Oracle Server Software

only:Create Database

Choose No and then Next.

Summary Choose Install .

8/3/2019 upg920_60_11may04



1.8 Preparing for the Database Upgrade

16 May 2004

Window Entry

Oracle Server Softwareonly:

Oracle Net Configuration Assistant: Welcome

If this dialog appears, select Perform typical configuration .

File Locations / End of Installation

Choose Exit .

3. Install the latest patch set and hot fix (if available) as described in SAP Note 578683.

MSCS only:You have to install the current Oracle patch set and hot fix (if available) on bothnodes.

1.8 Preparing for the Database UpgradeUse

Before you can upgrade the database with the Database Upgrade Assistant , you have to performthe following tasks.

Procedure

1. In the environment of the user <DBSID>adm, delete the variables listed below.

• ORACLE_HOME

• TNS_ADMIN (if it exists)

MSCS only:Delete the variables on both nodes.

2. Edit init<DBSID>.ora and set JOB_QUEUE_PROCESSES = 0.

3. Log off and log on again to activate the changes to the Windows environment.

1.9 Upgrading the Database

Procedure

MSCS only:Follow the instructions in the following section only on node A where thedatabase is located.In the Cluster Administrator make sure that the database disks are online on nodeA.

8/3/2019 upg920_60_11may04




May 2004 17

1. Stop the SAP system.

2. Start the Oracle Database Upgrade Assistant from the Start menu with:

Start → Programs → Oracle - <NEW_ORACLE_HOMENAME> → Configuration and

Migration Tools → Database Upgrade Assistant

The Oracle Database Upgrade Assistant (DUA) opens. A sequence of windows guides youthrough the process. You can navigate between the windows by choosing Next or Back .

The data upgrade takes approximately 15 minutes on a fast machine.

During the upgrade empty DOS-boxes may appear. Ignore them as long as theydisappear automatically.

Screen Input 1. DUA: Welcome Choose Next .

2. DUA: Select a Database Instance

Select <DBSID>-<OLD_ORACLE_HOME> and

choose Next .

3. DUA: NCHAR datatypes

Choose Yes .

4. DUA: SYSTEMtablespace

If there is not enough space in the SYSTEMtablespace, this message appears.

Extend the SYSTEM tablespace and chooseRetry without stopping the Database UpgradeAssistant.

If you intend to use brtools.exe to extend the

system tablespace you will have to start acommand prompt and fix the environment variablePATH in this command prompt using the set command.

Put the binary directory of the old 8.1.7 OracleHome to the very beginning of the environmentvariable PATH. Start brtools.exe from within

this command box.

5. DUA: SYSTEM rollbacksegment

If this message appears, choose Continue .

6. DUA: Backup Your Database

Select I have already backed up my database andchoose Next.

7. Summary Choose Finish to start the upgrade.

8. DUA: Progress The screen displays the phases of the dataupgrade procedure. It takes approximately 15-20minutes to complete the upgrade. After the

8/3/2019 upg920_60_11may04




18 May 2004

Screen Input upgrade has finished choose OK to see theupgrade results.

9. DUA: Upgrade Results Window

Check the results and any errors.

Do not Configure Database Passwords .

Do not choose Restore Database .

10. Close Choose Close to close the Database UpgradeAssistant.

8/3/2019 upg920_60_11may04


SAP AG 2 Post-Upgrade Activities

2.1 Modifying the Oracle Network Configuration

May 2004 19

2 Post-Upgrade Activities

Process Flow

To complete the upgrade of a database server, you perform the following tasks:

• Modification of the Oracle Network configuration []

• Configuration tasks [Page 21]

• Deletion of the old Oracle software [Page 24]

• Setting of user environment variables [Page 29]

• MSCS Only: Configuration of node B [Page 31]

• MSCS only: Addition of the database to the Fail Safe group [Page 31]

• Backup of the Oracle8 Database [Page 32]

• Upgrade of Database Clients [Page 33]


Use

After the database upgrade, you perform a number of manual tasks to complete the databaseconfiguration.

You have to perform the following steps for each active ORACLE_HOME and make sure that youdo not use the same TCP/IP port number for more than one listener

Procedure

• Multiple Oracle Homes:See the installation procedure at the end of this section.

• MSCS only:Modify the Network Configuration only on node A where the database islocated.

1. Stop the old Oracle Listener service.

2. Start the Net Manager that guides you through the Network configuration process. To do this,

choose Start → Programs → Oracle - <NEW_ORACLE_HOMENAME> → Configuration and

Migration Tools → Net Manager

The assistant opens. 3. On the Net Manager screen, in the tree on the left, expand Local and select Profile.

a. On the right, if necessary, select Naming from the dropdown box and then the tab Oracle Names .

In the field Default Domain , enter world

Leave the other settings unchanged.

8/3/2019 upg920_60_11may04


2 Post-Upgrade Activities SAP AG


20 May 2004

b. On the right, select the Methods tab.

From the list of Selected Methods remove the entries hostname and onames.

4. In the tree on the left, expand Listeners and select the LISTENER node that appears.

a. On the right, select Listening Locations from the dropdown box.Address tabs appear.

b. Check all the address tabs. If it exists, on the tab with the port number 2481, the optionDedicate this endpoint to IIOP connections is selected. Delete this address.

c. Choose Add Address to open a dialog box for a new address. Enter the port number 1527, if it is free.

Note that this is the network configuration of the Listener for the database server.

d. In the tree on the left, expand Service Naming and select <DBSID>.<tcp/ip_dns_name>

Choose Edit → Rename. E nter the name <DBSID>.world and choose OK.

e. Under Service Naming select <DBSID>.world . On the right, in Address Configuration

choose the plus icon to open a dialog box for a new address. Enter the port number 1527 a second time if it is free. Under Service Identification select Use Oracle8 Release

8.0 Compatible Identification . For SID enter <DBSID>.

Note that this is the network configuration for the database client.

If the option Use Oracle8 Release 8.0 Compatible Identification is not selected,the standalone database is later not visible in the Oracle Fail Safe Manager .

5. From the menu, choose File → Save Network Configuration.

6. Exit the Net Manager.

7. Restart the Oracle Listener for Oracle 9.2.0.

Multiple Oracle Homes only:

If you want to continue using additional ORACLE_HOMEs, then perform this

procedure.

If you have two or more co-existing Oracle Homes, each has its own Listener and its owncorresponding configuration. Make sure you do not use the same port number for more than onelistener. To check existing numbers in the Net Manager:

1. Choose File → Open Network Configuration

2. In the tree, open the Oracle Home folder, for example, for 8.0.x this can be ORANT.

3. Navigate to the admin folder.Under Oracle 8.0.x the path is: <ORACLE_HOME>\net80\admin

Under Oracle 8.1.* the path is: <ORACLE_HOME>\network\admin

4. Select the Listener and choose OK .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 thisfor both the client and server using the Net Manager as described earlier.

8/3/2019 upg920_60_11may04



2.2 Configuration Tasks

May 2004 21

5. Restart both the old and new TNSListener services.

If the TNSListener for Oracle 9.2.0 cannot be started, the Network configuration is

incorrect.

6. Carry out steps 1-8 listed at the beginning of this chapter for each active ORACLE_HOMEand make sure that you do not use the same port number for more than one listener.


Use

Several manual steps must be performed to set up the database server correctly for Oracle 9.2.0.The configuration tasks differ, depending whether you use an SAP system below 6.40 or an SAPsystem 6.40 or higher.

The following describes the configuration procedure for both system variants.

2.2.1 Configuration Tasks for SAP systems below 6.40

MSCS only:Some of the following steps must be performed on node A, others also on nodeB. Make sure that you perform the step on the node indicated for each step.If an error message appears when you open the Cluster Administrator , you canignore it. The message no longer appears when you have called up the Oracle Fail Safe Manager and verified the cluster as described later.

Procedure

1. Edit the file <NEW_ORACLE_HOME>\network\admin\sqlnet.ora by inserting the line:

tcp.nodelay = true

MSCS only:Edit this file on node A only.

2. In the <NEW_ORACLE_HOME> directory for 9.2.0, create the subdirectory SAP.

From the Oracle RDBMS CD3, copy all the files from the directory

<CD_DRIVE>:\NT\I386\SAP to the new SAP directory.

MSCS only:Create the subdirectory on both nodes.

3. Copy the init<DBSID>.dba and init<DBSID>.sap file from the old Oracle home to the

new Oracle home.

The location of the init<DBSID>.* files under the new Oracle Home is:<NEW_ORACLE_HOME>\DATABASE

8/3/2019 upg920_60_11may04




22 May 2004

MSCS only:Copy the init<DBSID>.dba and init<DBSID>.sap files on node A only.

4. The Database Upgrade Assistant switches the profile mechanism to the new SPFILEmechanism, which is not fully supported by SAP at the moment. Therefore we have to revertthis step manually:

a. Startup the database and run the following commands:sqlplus /nolog

sqlplus> connect / as sysdba

sqlplus> create pfile from spfile;

sqlplus> exit

b. Delete the file <New_Oracle_HOME>\database\SPFILE<DBSID>.ora .

MSCS only:Perform Step 4 on node A only

5. Edit the init<DBSID>.ora file in <NEW_ORACLE_HOME>\DATABASE with the SAPPad

editor as follows:

a. Choose Options → Save As NT TextFile

b. Delete *. in front of the parameter names. You can achieve this by replacing *. inthe whole document with nothing.

c. Make sure that the following parameters point to the correct directory:

o background_dump_dest has to point to

<drive>:\oracle\<DBSID>\saptrace\background

o core_dump_dest has to point to <drive>:\oracle\<DBSID>\saptrace\background

o user_dump_dest has to point to <drive>:\oracle\<DBSID>\saptrace\usertrace

d. Search for the parameter compatible and set it from 8.1.7 to 9.2.0.

• The environment variable saptrace normally points to the directory

<drive>:\oracle\<DBSID>\saptrace\ . If not,

%sapdata_home%\saptrace points to this directory.

• Be aware, that you cannot use the names saptrace or sapdata_home as

environment variables in the init<DBSID>.ora file. For example youcannot use: user_dump_dest = '%saptrace%\usertrace' or

'$saptrace\usertrace'.

MSCS only:

• Edit init<DBSID>.ora file on node A only.

• Remove the character ‘ from the value of db_name.

8/3/2019 upg920_60_11may04




May 2004 23

6. Change the parameter values with the Oracle Administration Assistant for Windows NT

Windows NT only:The Administration Assistant is not available if you have not installed the MMC.In releases prior to 4.5B, you can change the parameters in the Registry . Bothprocedures are explained in the following.

• Changing the Parameters with the Administration Assistant

i. Start the Administration Assistant with Start → Programs → Oracle-

<NEW_ORACLE_HOMENAME> → Configuration and Migration Tools → Administration Assistant for Windows NT

The Assistant opens.

ii. Choose Oracle Managed Objects → Computers → <hostname> → Oracle Homes

→ <New_Oracle_Home_Name>

iii. Open the context menu with the right mouse button and choose Properties .

iv. In the Properties dialog box, change the entry for ORA_<DBSID>_PFILE to:

<NEW_ORACLE_HOME>\DATABASE\init<dbsid>.ora

v. Set the entry for ORA_<DBSID>_AUTOSTART to FALSE and confirm with OK .

• Changing the Parameters in the Registry

i. Choose Start → Run and then enter regedit.

ii. Expand HKEY_LOCAL_MACHINE→ SOFTWARE → ORACLE → <HOME<n>>Where <HOME<n>> is the Home for Oracle 9.2.0.

iii. Change the parameters as required.

MSCS only:Change the parameter values on node A only.

7. Start the Oracle Services, if not yet started. 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, see Starting or Stopping Services [Page 37].

MSCS only:Start the services on node A, where the database is located.

8. MSCS only: Move the Oracle<DBSID> and the SAP-R3<SAPSID> groups to node A. In the

Cluster Administrator, make sure that the disk groups and the shares SAPMNT and SAPLOC are online on node A.

9. Start up the database.

For more information, see Starting and Stopping the Database [Page 35].

8/3/2019 upg920_60_11may04




24 May 2004

10. Unpack BR*Tools as follows:

a. Open a command prompt.

b. Switch to the directory:

<DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\RUN

c. To unpack the tools, enter the following command on a single line:

<NEW_ORACLE_HOME>\SAP\sapcar -xvf<NEW_ORACLE_HOME>\SAP\DBATOOLS.SAR

Make sure that you use the most current archives for your SAP system. You candownload them from the SAP Service Marketplace.

MSCS only:

Install BR*Tools in the directory <DRIVE>\USR\SAP\<SAPSID>\SYS\EXE\RUN

on one node only. Also install them in the directory %windir%\SapCluster on

both nodes.

11. Make sure that the user SAPService<SAPSID> is included in the local groupORA_<DBSID>_DBA.

MSCS only:

• Make sure that the user under which the OracleMSCSServices was started is

also included in the local group ORA_<DBSID>_DBA.

• Perform this step on both nodes.

For more information see Creating a Local Group [Page 38].

2.2.1 Configuration Tasks for SAP systems 6.40 andhigher

MSCS only:Some of the following steps must be performed on node A, others also on nodeB. Make sure that you perform the step on the node indicated for each step.If an error message appears when you open the Cluster Administrator , you canignore it. The message no longer appears when you have called up the Oracle Fail Safe Manager and verified the cluster as described later.

Procedure

1. Edit the file <NEW_ORACLE_HOME>\network\admin\sqlnet.ora by inserting the line:

tcp.nodelay = true

MSCS only:Edit this file on node A only.

8/3/2019 upg920_60_11may04


8/3/2019 upg920_60_11may04




26 May 2004

• Be aware, that you cannot use the names saptrace or sapdata_home

as environment variables in the init<DBSID>.ora file. For example you

cannot use: user_dump_dest = '%saptrace%\usertrace' or

'$saptrace\usertrace'.

MSCS only:Perform this step on node A only.Remove single character ‘ from the value of db_name.

5. Change the parameter values with the Oracle Administration Assistant for Windows NT

Windows NT only:The Administration Assistant is not available if you have not installed the MMC.In releases prior to 4.5B, you can change the parameters in the Registry . Bothprocedures are explained in the following.

• Changing the Parameters with the Administration Assistant

i. Start the Administration Assistant with Start → Programs → Oracle-

<NEW_ORACLE_HOMENAME> → Configuration and Migration Tools → Administration Assistant for Windows NT

The Assistant opens.

ii. Choose Oracle Managed Objects → Computers → <hostname> → Oracle Homes → <New_Oracle_Home_Name>

iii. Open the context menu with the right mouse button and choose Properties .

iv. In the Properties dialog box, change the entry for ORA_<DBSID>_PFILE to:

<NEW_ORACLE_HOME>\DATABASE\init<dbsid>.ora

v. Set the entry for ORA_<DBSID>_AUTOSTART to FALSE and confirm with OK .

vi. Delete parameter ORA_<DBSID>_PFILE.

• Changing the Parameters in the Registry

i. Choose Start → Run and then enter regedit.

ii. Expand HKEY_LOCAL_MACHINE→ SOFTWARE → ORACLE → <HOME<n>>Where <HOME<n>> is the Home for Oracle 9.2.0.

iii. Change the parameters as required.

iv. Delete parameter ORA_<DBSID>_PFILE.

MSCS only:Change the parameter values on node A only.

6. Start the Oracle Services, if not yet started. Set the startup type of OracleService<DBSID> and Oracle<ORACLE_HOME_NAME>TNSListener to

automatic to ensure that they are automatically restarted after booting.

8/3/2019 upg920_60_11may04




May 2004 27

MSCS only:Start the services on node A, where the database is located.

For more information, see Starting or Stopping Services [Page 37].

7. MSCS only: Move the Oracle<DBSID> and the SAP-R3<SAPSID> groups to node A. In the

Cluster Administrator, make sure that the disk groups and the shares SAPMNT and SAPLOCare online on node A.


For more information, see Starting and Stopping the Database [Page 35].

9. Unpack BR*Tools.

MSCS only:

Install BR*Tools in the directory <DRIVE>\USR\SAP\<SAPSID>\SYS\EXE\RUN

on one node only. Also install them in the directory %windir%\SapCluster onboth nodes.

a. Open a command prompt.

b. Switch to the directory:

<DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\RUN

c. To unpack the tools, enter the following command on a single line:

<NEW_ORACLE_HOME>\SAP\sapcar -xvf<NEW_ORACLE_HOME>\SAP\DBATOOLS.SAR

Make sure that you use the most current archives for your SAP system. You can

download them from the SAP Service Marketplace.

10. Make sure that the user SAPService<SAPSID> is included in the local groupORA_<DBSID>_DBA.

MSCS only:Make sure that the user under which the OracleMSCSServices was started is

also included in the local group ORA_<DBSID>_DBA.

Perform this step on both nodes.

For more information see Creating a Local Group [Page 38].

8/3/2019 upg920_60_11may04



2.3 Deleting the old Oracle Software

28 May 2004

2.3 Deleting the old Oracle Software

Procedure

1. Delete the old Oracle 8.1.x installation.

Do not delete the 8.0.x or 8.1.x software, if it still has to be accessed by another SAP instance running with this version. For example, this may be the case if anSAP dialog or central instance belonging to a different SAP system is running onthe same database host.

MSCS only:Perform all the steps to delete the software on both nodes. In a cluster begin withthe steps:

− Stop the database.

− Set the Oracle Services for MSCS offline.− Stop the Cluster Service on both nodes.

− Continue with step 2.

2. Shut down the database.

3. Stop the service Distributed Transaction Coordinator.

4. Stop the Oracle 8.1.x Services in the Control Panel.

5. Follow the instructions for your Oracle home you want to remove.

Oracle Home version 8.1.x

a. Start the Oracle 8.1.x Installer with Start → Programs → Oracle Installation Products → Universal Installer.

Note that on a database client, you start the Installer from the Oracle RDBMS CD1.Double-click the file setup.exe in the directory <CD-DRIVE>:\NT\<OS>

On the RDBMS DVD, the file is located in the directory<DVD_DRIVE>:\ORA92_1\NT\<OS>

b. In the Welcome screen, choose Deinstall Products

c. In the Inventory dialog box, expand the node representing Oracle home for version 8.1.xand then select Oracle 8.1.x. Click Remove .

Note that on a database client, you expand the node representing the home of Oracle Client 8.1.x and then select Oracle Client 8.1.x

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

Note that it is not possible to delete all the Oracle 8.1.x products.

MSCS only: Do carry out Step 6 only after Adding the Database to the Fail Safe Group [Page31].

8/3/2019 upg920_60_11may04



2.4 Setting Environment Variables

May 2004 29

6. Delete the old Oracle 8.1.x services that still exist. To delete a service, open a commandprompt and enter:

ntscmgr remove <service_name>

The following services must be left after the deletion:

Oracle<ORACLE_HOME_NAME>Agent

Oracle<ORACLE_HOME_NAME>ClientCache

Oracle<ORACLE_HOME_NAME>TNSListener

Oracle<ORACLE_HOME_NAME>SNMPPeerEncapsulator

Oracle<ORACLE_HOME_NAME>SNMPPeerMasterAgent

OracleService<DBSID>

MSCS only:The OracleMSCSServices and theOracle<ORACLE_HOME_NAME>TNSListenerFsl<VIRTUAL_DATABASE_HOST

NAME> must be left after the deletion.

Multiple Oracle Homes only:On a database server with multiple homes, do not delete the service

OracleService<DBSID>. If more than one Listener is configured, do not delete

these either.

7. In the Windows Explorer delete the Oracle Home directory of the 8.1.x software.

The home directory for 8.1.x can be <DRIVE>:\ORACLE\<DBSID>\81x

8. Delete the entry Oracle for Windows NT in the Windows Start menu, if it exists, as follows:

a. Choose Start → Programs .

b. Right-click and select Oracle – <OLD_ORACLE_HOMENAME>

c. Choose Delete.

Be sure not to delete the Registry key for the earlier Oracle version, for example:

HKEY_LOCAL_MACHINE → SOFTWARE → ORACLE → HOME<n>


Procedure

MSCS only:Edit the variables on both nodes.

For more information see Setting or Deleting Environment Variables [Page 38].

1. In the user environment of <SAPSID>adm, check the PATH variable and remove all parts

referring to the old Oracle version.

8/3/2019 upg920_60_11may04




30 May 2004

If you have two or more co-existing Oracle Homes, each <SAPSID>adm user has

a different Oracle home. For each of these users, enter the following in the

corresponding PATH variable of the user environment:

<Oracle_Home>\bin Note that when you modify the user environment, you must be logged on as thecorresponding <SAPSID>adm user.

Make sure that the new Oracle home is included in the path.

MSCS only:Do not remove parts of the PATH variable referring to Oracle Fail Safe .

2. In the system environment, delete the Oracle parts of the PATH variable that refer to the old

Oracle version.

Do not delete parts of the path referring to the Java runtime environment, for example:\jre\...If you have two or more co-existing Oracle Homes, delete all parts of the pathreferring to Oracle except those mentioning the Java runtime environment. Inaddition, make sure that no Oracle binary directory is included in the path.

MSCS only:Do not remove parts of the PATH variable referring to Oracle Fail Safe .

3. In the user environment of <SAPSID>adm, set the ORACLE_HOME variable to the correct

value for Oracle 9.2.0. For example to: <DRIVE>:\ORACLE\C11\920

MSCS only:Set the variables on both nodes.

4. Only releases prior to 4.6A:

MSCS only:Run ntenv2reg on both nodes.

In the Cluster Administrator , make sure that the SAP-R3<SAPSID> group, the SAP

disks and the shares SAPMNT and SAPLOC are online on node A.

a. Open a new command prompt and run the script ntenv2reg

b. Enter the following:

ntenv2reg

c. In the dialog box that appears, select the instance you want to upgrade

SAP<SAPSID>_<INSTANCE_NO>, for example, SAPC11_09

5. Reboot the computer.

8/3/2019 upg920_60_11may04



2.5 MSCS Only: Configuring Node B

May 2004 31

2.5 MSCS Only: Configuring Node BCopy files from the primary node A to node B:

1. Make sure that the Cluster Service is running on node B.

2. SAP systems below 6.40: Copy the file init<DBSID>.* from the directory

<ORACLE_HOME>\database on node A to the same directory on node B.

3. SAP systems 6.40 and higher: Copy the files init<DBSID>.* and spfile*.ora from

the directory <ORACLE_HOME>\database on node A to the same directory on node B.

4. Copy the file sqlnet.ora from the directory <ORACLE_HOME>\network\admin on node A

to the same directory on node B.

2.6 MSCS Only: Adding the Database to the FailSafe GroupTo enable a database to fail over with all the resources it requires, it must be added to the

Fail Safe group.

Procedure

Follow the instructions on the primary node A.

1. Make sure the Cluster Service is running on both nodes.

2. Start the Cluster Administrator.

3. In the Cluster Administrator bring the Oracle Services for MSCS resource online.

4. Start the Oracle services. Make sure the

Oracle<NEW_ORACLE_HOME_NAME>TNSLISTENER and OracleService<DBSID> are

online.


For more information, see Starting and Stopping the Database [Page 34]

6. Move the cluster group to node A, if it is on node B. Afterwards, in the Cluster Administrator ,make sure that the Oracle Services for MSCS resource in the cluster group is online on nodeA.

7. Move the Cluster Group from node A to B and then back to node A again.

If you leave out this step, you may not be able to add the database to the FailSafe Group.

8. Start the Oracle Fail Safe Manager with Start → Programs → Oracle -

<Failsafe_HomeName> → Oracle Fail Safe Manager

9. In the Welcome dialog box choose Verify Cluster .

Both cluster nodes must be up and running for this step.

8/3/2019 upg920_60_11may04



2.6 MSCS Only: Adding the Database to the Fail Safe Group

32 May 2004

The window Clusterwide Operation: Verifying Fail Safe Cluster shows the steps that areexecuted to verify the cluster. When you are informed that the operation has completedsuccessfully, close the window.

10. Add the SAP database to the Fail Safe group Oracle<DBSID>

a. In the tree on the left, choose Nodes → <Node_A> → Standalone Resources and thenselect the database <DBSID>.world

b. Choose Resources → Add to Group

11. In the dialog box Add Resource to Group – Resource: Step 1 for Resource Type, selectOracle Database . For Group name , select Oracle <DBSID>

12. Choose Next.

13. In the dialog box Add Resource to Group – Database Identity: Step 2, verify the information and choose Finish . You may need to specify the database name.

14. In the dialog box Finish Adding the Database to the Group , choose OK to add the databaseresource to the group.

15. In the dialog box Confirm Add database to Group : click Yes .

The Adding resource <DBSID>.world to group window, shows the steps that are executed toadd the database to the Fail Safe group.

16. In the Clusterwide Operation Query window, click Yes .

17. Delete the old Oracle 8.1.x services that still exist. To delete a service, open a commandprompt and enter:

ntscmgr remove <service_name>

The following services must be left after the deletion:

Oracle<ORACLE_HOME_NAME>Agent

Oracle<ORACLE_HOME_NAME>ClientCache

Oracle<ORACLE_HOME_NAME>TNSListenerOracle<ORACLE_HOME_NAME>SNMPPeerEncapsulator

Oracle<ORACLE_HOME_NAME>SNMPPeerMasterAgent


MSCS only:The OracleMSCSServices Service and theOracle<ORACLE_HOME_NAME>TNSListenerFsl<VIRTUAL_DATABASE_HOST

NAME> must be left after the deletion.

Multiple Oracle Homes only:

On a database server with multiple homes, do not delete the serviceOracleService<DBSID>. If more than one Listener is configured, do not delete

these either.

8/3/2019 upg920_60_11may04



2.7 Backing up the Oracle9i Database

May 2004 33

2.7 Backing up the Oracle9i Database

MSCS only:Backup the database after you have performed the additional steps for MSCSdescribed in the next section.

Use

Create a full backup of the SAP database to ensure that a restore operation to the state after themigration is possible.

Procedure

1. Shut down the Oracle9i database with SHUTDOWN NORMAL.For more information see Starting and Stopping the Database [Page 34]

2. Shut down all Oracle services.

For more information see Starting or Stopping Services [Page 37].3. Make an offline backup of your SAP database and the Oracle software.

2.8 Upgrade of Database Clients

Purpose

To complete a database migration or upgrade, you must update any database clients in thesystem to the new Oracle version.

Prerequisites

The migration or upgrade of the database server is complete.

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

Process Flow

Actions necessary on the database client are:

• Setting the NLS_LANG variable [Page 36]

• Installing the Oracle9i Release 9.2.0 software [Page 14] using sapclient.cmd

• Deletion of the old Oracle software [Page 24]

• Setting environment variables [Page 29]

• Copy the files sqlnet.ora, tnsnames.ora from the database server to the

corresponding directory on the database client.

The location of the files on the server, is:<ORACLE_HOME>\network\admin

8/3/2019 upg920_60_11may04


3 Common Administration Tasks SAP AG

3.1 Standard Tasks

34 May 2004

3 Common Administration TasksCommon Administration tasks that have to be performed repeatedly during the installation aredescribed in this section. Some of these tasks are standard, others are only relevant for a

Microsoft Cluster Server configuration.

3.1 Standard TasksCommon tasks that have to be repeated during the upgrade procedure are documented here.

• Starting sqlplus []

• Starting and Stopping the Database [Page 34]

• Starting the Instance Manager [Page 35]

• Oracle services [Page 35]

• Setting the NLS_LANG environment variable [Page 36]

• Checking Services [Page 37]

• Starting or stopping services [Page 37]

• Starting or stopping the SAP System [Page 37]

• Updating the Dynamic Link Libraries [Page 37]

• Deleting a Registry entry [Page 38]

• Setting or deleting environment variables [Page 38]

• Creating a local group [Page 38]

3.1.1 Starting sqlplusUse

Start the Oracle Server Manager or sqlplus as follows.

Procedure

1. Open a Command Prompt

2. Enter the appropriate command for your Oracle version:

ORACLE8 ORACLE8.1 Oracle9i

svrmgr30 svrmgrl sqlplus /nolog

8/3/2019 upg920_60_11may04


SAP AG 3 Common Administration Tasks

3.1 Standard Tasks

May 2004 35

3.1.2 Starting and Stopping the Database

Procedure

To start up or shut down the database, enter the appropriate commands in the Server Manager or sqlplus .

• To start up the database enter:

connect / as sysdba

startup

exit

• To shut down the database enter:

connect / as sysdba

shutdown immediate

exit

3.1.3 Starting the Instance Manager

Procedure

Open a Command Prompt and start the instance manager for your particular database releasewith the required option:

ORACLE8 ORACLE 8.1.x ORACLE 9i

oradim80 oradim oradim

3.1.4 Oracle ServicesThe following services exist after a standard Oracle installation:

ORACLE 8.0x ORACLE 8.1.x ORACLE 9i

OracleService<DBSID> OracleService<DBSID> Oracle<ORACLE_HOME_NAME>Agent

OracleTNSListener80 Oracle<ORACLE_HOME_N AME>TNSListener

Oracle<ORACLE_HOME_NAME>Client Cache

OracleAgent80 Oracle<ORACLE_HOME_N

AME>Agent

Oracle<ORACLE_HOME_NAME>TNSLi

stener

OracleClientCache80 Oracle<ORACLE_HOME_N AME>ClientCache

Oracle<ORACLE_HOME _NAME>SNMP

PeerEncapsulator

Oracle<ORACLE_HOME_N AME>DataGatherer

Oracle<ORACLE_HOME_NAME>SNMP PeerMasterAgent


8/3/2019 upg920_60_11may04



3.1 Standard Tasks

36 May 2004

3.1.5 Setting the NLS_LANG Variable

Use

Set the NLS_LANG variable in the user environment of <DBSID>adm. The value of NLS_LANG

depends on the value of the Oracle parameter NLS_CHARACTERSET. The following describes

how to determine the value of NLS_CHARACTERSET and then how to derive the value of

NLS_LANG from it.

MSCS only:NLS_LANG must be set on both nodes. It has the same value on both nodes.

Procedure

1. Find out the value of the Oracle parameter NLS_CHARACTERSET:

a. Log on as user <DBSID>adm

b. At the command prompt, start the Oracle Server Manager or sqlplus with the appropriatestartup command for your Oracle version:

Oracle8 Oracle8.1 Oracle9i

svrmgr30 svrmgrl sqlplus

sqlplus \nolog

sql> connect \ as sysdba

For Oracle version < 9.2.0, enter the following: <SERVER_MANAGER_CALL> SVRMGR> connect @<DBSID> as sysdba

c. Enter the following command in a single line:

sql> select * from v$nls_parameters where parameter like'NLS_CHAR%';

For Oracle version < 9.2.0, enter the following: SVRMGR> select * from v$nls_parameters where parameter like'NLS_CHAR%';

The value of the parameter NLS_CHARACTERSET is returned.

2. Set the variable NLS_LANG in the Windows user environment of <SAPSID>adm. If you are

upgrading or migrating a database client perform this step on the client machine.

− If NLS_CHARACTERSET has the value WE8DEC, set NLS_LANG toAMERICAN_AMERICA.WE8DEC

− If NLS_CHARACTERSET has the value US7ASCII, set the variable NLS_LANG toAMERICAN_AMERICA.US7ASCII

8/3/2019 upg920_60_11may04



3.1 Standard Tasks

May 2004 37

For more information, see Setting or Deleting Environment Variables [Page 38].

3.1.6 Checking Services

Procedure

1. Choose Start → Programs → Administrative Tools → Services

2. Double-click on the required service.

The Status column shows whether a service has been started.The Startup Type column shows whether a service is started automatically after booting or whether it has to be started manually.

To change the startup type, choose Action → Properties. Select the General tab and thenchoose the startup type from the dropdown box.To change the user that is assigned to a service, select the Log On tab and make theappropriate entries.

3.1.7 Starting or Stopping Services1. 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.

3.1.8 Starting or Stopping the SAP System

Procedure

To start or stop the SAP system in releases 4.5B and higher, use the Microsoft Management

Console (MMC). In releases prior to 4.5B, use the SAP Service Manager.

When you boot the Windows system, the SAP Service SAP<SAPSID>_<Instance_number>

(for example SAPC11_00) is always started automatically.

Using the Microsoft Management Console

1. Start the MMC on the host where the SAP central instance is running. To do this, choose

Start → Programs → SAP Management Console

2. In the tree on the left side, select the central instance.

3. Open the context menu by clicking the right mouse button and choose Start or Stop

When you start the system, the SAP central instance and the database are started.When you stop the system, only the SAP system is stopped. The database remains running.

Using the SAP Service Manager

You can start or stop the SAP processes using the SAP Service Manager s by choosing Start or stop in the SAP Service Manager .

When the SAP services receive the stop message from the SAP Service Manager , they stop theSAP system.

8/3/2019 upg920_60_11may04



3.1 Standard Tasks

38 May 2004

3.1.9 Updating the Dynamic Link libraries

Procedure

1. Insert the SAP Kernel CD into the CD-ROM drive and switch to the directory<CD_DRIVE>:\NT\I386\NTPATCH

For releases 6.40 and higher you have to use the SAPinst Master CD and switchto the directory <dvd_drive>:IM1\NT\I386\NTPATCH

2. Start the program r3dllins.exe

3. Reboot the computer to activate the new settings.

If your DLLs were already up-to-date before you started r3dllins.exe, no new DLLs are

installed and you are not prompted to reboot.

3.1.10 Deleting a Registry EntryProcedure

Start the Registry Editor regedit.

1. Select the required key (for example, HKEY_LOCAL_MACHINE → SOFTWARE → Oracle).

2. Make the changes required. To delete an entry, choose Edit → Delete .

3. Leave the Registry Editor.

3.1.11 Setting or Deleting Environment Variables

Procedure

To view or change environment variables

1. Right-click on My Computer .

2. Choose Properties.

3. On the System Properties dialog box, choose the Advanced tab. Click Environment variables .

The user and system environment variables are displayed. New , Edit and Delete buttons areavailable and allow you to change variables.

3.1.12 Creating a Local Group

UseThe following describes the steps that must be executed locally on the host in order to create thelocal group and to insert a domain user.

Procedure

1. Right-click My Computer and choose Manage.

2. From the Computer Management tree, choose Local users and Groups and expand it.

8/3/2019 upg920_60_11may04



3.2 MSCS Tasks

May 2004 39

3. Right-click Groups and choose New Group .

4. Enter the Group name and a description.

5. To add members to the group choose Add.

The Select Users or Groups dialog box opens.6. Under Name , select a user you want to include in the group and then click Add . This user is

added to the group that appears in the text box below. Repeat the process until all the namesthat you want to include in the group are listed and then click OK .

Alternatively, if the group you want to add users to already exists:Select the user in the Computer Management tree and double-click on it. Choose the Member of tab. Select the group in which you want to include the user andchoose Add . Click OK to confirm the entry.

3.2 MSCS Tasks

Common tasks that have to be performed repeatedly during the upgrade in a MSCSconfiguration are documented here.

• Starting Up or Shutting Down the Database for MSCS []

• Services for MSCS [Page 40]

• Starting and Stopping Services for MSCS [Page 40]

• Stopping the Cluster Service [Page 41]

• Starting and Stopping the SAP System for MSCS [Page 42]

• Backing Up the SAP System for MSCS [Page 43]

3.2.1 Starting Up or Shutting Down the Databasefor MSCS

Procedure

Always use the Fail Safe Manager to stop the database, if the Cluster Service and OracleMSCSServices are running. If you do not use the Fail Safe Manager ,the cluster functionality automatically attempts to restart the database.If the Cluster Service and OracleMSCSServices are stopped, you must usesqlplus to start and stop the database. This is often the case during an upgrade or migration.

• Starting up the database with the Oracle Fail Safe Manager

Log on as user <SAPSID>adm. In the Oracle Fail Safe Manager, select the database

<DBSID>.world in the Fail Safe group ORACLE<DBSID> . Press the right-hand mouse buttonand choose place online .

• Shutting down the database with the Oracle Fail Safe Manager.

8/3/2019 upg920_60_11may04



3.2.2 Services for MSCS

40 May 2004

Log on as user <SAPSID>adm. In the Oracle Fail Safe Manager , select the database

<DBSID>.world in the Fail Safe group ORACLE<DBSID> and set it to offline.As of Fail Safe Version 2.1 you can choose between the options offline normal , offline immediate and offline abort at this point. Choose offline normal .

3.2.2 Services for MSCSThe following services exist in an Oracle 8i Release 8.1.7 MSCS installation:

• OracleService<DBSID>

• Oracle<Oracle-HomeName>TNSListener

• Oracle<Oracle-HomeName>Agent

• Oracle <Oracle-HomeName>ClientCache

• Oracle <Oracle-HomeName>DataGatherer

• OracleFailSafe

• Oracle <Oracle-HomeName>TNSListenerFsl<virtual DB host name>

The following services exist in an Oracle 9i Release 9.2.0 MSCS installation:

• OracleService<DBSID>

• Oracle<Oracle-HomeName>TNSListener

• Oracle<Oracle-HomeName>Agent

• Oracle<Oracle-HomeName>ClientCache

• Oracle<Oracle-HomeName>SNMPPeerEncapsulator

• Oracle<Oracle-HomeName>SNMPPeerEncapsulator

• OracleMSCSServices

• Oracle<Oracle_Home_Name>TNSListenerFsl<virtual DB host name>

3.2.3 Starting and Stopping Services for MSCSTo start or stop the following services:

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.

Oracle 8 Oracle 8.1.7 Oracle 9.2.0

SAPOsCol SAPOsCol SAPOsCol

OracleAgent80 <Oracle_Home>Agent <Oracle_Home>Agent

OracleTNSListener80 <Oracle_Home>TNSListener <Oracle_Home>TNSListener

8/3/2019 upg920_60_11may04




May 2004 41

The following services can only be started or stopped with the Cluster Administrator or Fail Safe Manager . To start a resource, set it online. To stop a resource set it offline.

If during the migration process the Cluster S ervice is stopped, you cannot use theFail Safe Manager or Cluster Administrator to stop services. In this case, youhave to stop them in the Control Panel.However, when the Cluster Serv ice is running, you must use the Cluster Administrator or Fail Safe Manager , otherwise the cluster functionalityautomatically attempts to restart the services you have stopped.

Service Resource

SAP<SAPSID>_<Instance_No.> Set the resource SAP R/3 to online. R/3 isstarted up

OracleService<DBSID> Set the resource <DBSID>.world in the groupORACLE<DBSID> to online.

or

Set the Fail Safe Database <DBSID>.world toonline in the Oracle Fail Safe Manager

OracleAgent<virtual DB host name>

<ORACLE_HOME>Agent (for 9.2.0)

Set the corresponding resource in the groupORACLE<DBSID> to online

Oracle<Oracle_Home_Name>TNSListenerFs l<virtual DB host name>

Set the corresponding resource in the groupORACLE<DBSID> to online

OracleMSCSServices Set the resource Oracle Services for MSCS in the Cluster group to online

Cluster Service In the Cluster Administrator , choose theservice and press the right mouse button.Choose Start Cluster Service .

3.2.4 Stopping the Cluster Service

Procedure

1. Start the Cluster Administrator .

2. Select the node where you want to stop the Cluster Service .

3. Choose File → Stop Cluster Service.

The Cluster Service is stopped. To restart the service, choose File → Start Cluster Service.

Alternatively, you can stop the Cluster Service in the Control Panel.

8/3/2019 upg920_60_11may04




42 May 2004

3.2.5 Moving Groups for MSCS

Use

You can use the Cluster Administrator or the Fail Safe Manager . The following describes theprocedure for both.

Use the Fail Safe Manager to move the database group Oracle<DBSID>.

Procedure

Cluster Administrator

1. Start the Cluster Administrator with Start → Settings → Control Panel → Administrative Tools → Cluster Administrator.

2. On the left-hand pane, under Groups select the cluster group you want to move. Press the

right mouse button and click Move group on the context menu.The group is now moved to the other node.

Fail Safe Manager

When you use the Fail Safe Manager for the first time you are asked to enter theCluster Alias . Enter the virtual cluster name.With Fail Safe Manager Version 3.3.2 you can enter “.” or the virtual cluster name. If you enter “.” you are connected directly to the local cluster.

Fail Safe Manager 3.3.2 (or 3.3.1)1. Start the Fail Safe Manager 3.3.2 (or 3.3.1) with Start → Programs → Oracle

<Home_name_fail safe> → Oracle Fail Safe Manager.

2. On the left-hand pane, select the group you want to move. Press the right mouse button andclick Move to a Different Node on the context menu.

The group is now moved to the other node.

Fail Safe Manager 3.1.1

1. Start the Fail Safe Manager 3.1.1 with Start → Programs → Oracle Enterprise Manager → Fail Safe Manager.

2. On the left-hand pane, select the group you want to move. Press the right mouse button and

click Move to different node on the context menu.


Fail Safe Manager 3.0.4

1. Start the Fail Safe Manager 3.0.4 with Start → Programs → Oracle- FailSafe → Oracle Fail Safe Manager.

8/3/2019 upg920_60_11may04




2. On the left-hand pane, select the group you want to move. Press the right mouse button andclick Move to different node on the context menu.


3.2.6 Starting or Stopping the SAP System for MSCS

Procedure

• To start the SAP system, open the Cluster Administrator and set the resource SAP-

R/3<SAPSID> in the group SAP-R/3 online.

• To stop the SAP system, set the resource SAP-R/3<SAPSID> in the group SAP R/3 offline.

3.2.7 Backing Up the SAP System for MSCS

Procedure

Back up the following file trees:

Directory Explanation Backup tool

\Oracle Backing up the database(only on database server)

SAP tool BRBACKUP

\<ORACLE_HOME> Backing up the Oraclesoftware

NTBACKUP

\usr\sap

\users Backing up the SAP software NTBACKUP

%windir% Backing up the Windowssystem NTBACKUP

<Quorum disk>:\mscs Backing up the cluster administration files

NTBACKUP

upg920_60_11may04

Documents