UPG_817

8/4/2019 UPG_817

http://slidepdf.com/reader/full/upg817 1/41

SAP®

AG • Neurottstr. 16 • D-69190 Walldorf

Upgrade to Oracle8iRelease 8.1.7

8/4/2019 UPG_817


Upgrade to Oracle8i Release 8.1.7 SAP AG

2 March 2001

Copyright

©Copyright 2001 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server ® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,

AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of

Informix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.

JAVA® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto,CA 94303 USA.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

ADABAS® is a registered trademark of Software AG.

SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.comBusiness Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAPBusiness Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management

Cockpit, SEM, SAP DB are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

http://service.sap.com/instguides

8/4/2019 UPG_817


SAP AG Upgrade to Oracle8i Release 8.1.7

March 2001 3

Typographic Conventions

Type Style Represents

Interface Text Words or characters that appear on the screen. Thisincludes system messages, field names, screen titles,pushbuttons, menu names, and menu options.

Document Title Cross-references to other documentation

User Entry Exact user entry. These are words and characters thatyou enter exactly as they appear in the documentation.

File Name File names, batch files, paths or directories, andscreen messages

<Variable User

Entry>

Variable user entry. Pointed brackets indicate that you

replace these words and characters with appropriateentries.

NAME Names of elements in the SAP System. These includereport names, program names, transaction codes,table names, and ABAP language elements.

KEY Keys on your keyboard. These include function keys

(for example, F2) and the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Tip

8/4/2019 UPG_817



4 March 2001

Contents

Upgrade to Oracle8i Release 8.1.7 ................................................. 5

1 Upgrade of the Database Server....................................................... 71.1 Multiple Oracle Homes .......................................................................................................7

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

1.3 Setting the NLS_LANG Variable.........................................................................................9

1.4 MSCS Only: Removing the DB from the Fail Safe Group ................................................10

1.5 MSCS Only: Upgrading to OFS 3.1.1...............................................................................11

1.6 Installing the Oracle8i Release 8.1.7 Software.................................................................13

1.7 Installing Hot Fix 8.1.7.0.1 ................................................................................................15

1.8 Preparing for the Data Upgrade........................................................................................16

1.9 Upgrading the Database...................................................................................................17

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

2.1 Modifying the Oracle Net8 Configuration..........................................................................192.2 Configuration Tasks..........................................................................................................21

2.3 Deleting the old Oracle Software ......................................................................................24

2.4 Setting Environment Variables .........................................................................................26

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

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

2.7 Backing up the Oracle8 Database ....................................................................................29

2.8 Upgrade of Database Clients............................................................................................29

3 Common Administration Tasks ...................................................... 30

3.1 Standard Tasks.....................................................................................303.1.1 Starting the Server Manager .......................................................................................303.1.2 Starting and Stopping the Database ...........................................................................313.1.3 Starting the Instance Manager ....................................................................................313.1.4 Oracle Services ...........................................................................................................323.1.5 Setting the NLS_LANG Variable .................................................................................323.1.6 Checking Services.......................................................................................................333.1.7 Starting or Stopping Services......................................................................................333.1.8 Starting or Stopping the R/3 System...........................................................................343.1.9 Updating the Dynamic Link libraries............................................................................343.1.10 Deleting a Registry Entry ..........................................................................................353.1.11 Setting or Deleting Environment Variables ...............................................................353.1.12 Creating a Local Group .............................................................................................35

3.2 MSCS Tasks..........................................................................................373.2.1 Starting Up or Shutting Down the Database for MSCS ..............................................37

3.2.2 Services for MSCS......................................................................................................383.2.3 Starting and Stopping Services for MSCS..................................................................393.2.4 Stopping the Cluster Server Service ...........................................................................403.2.5 Moving Groups for MSCS ...........................................................................................403.2.6 Starting or Stopping the SAP System for MSCS ........................................................413.2.7 Backing Up the SAP System for MSCS......................................................................41

8/4/2019 UPG_817


SAP AG Upgrade to Oracle8i Release 8.1.7

March 2001 5

Upgrade to Oracle8i Release 8.1.7Purpose

This documentation explains how to upgrade your database from Oracle version 8.0.x or 8.1.x toOracle version 8.1.7. The upgrade must be performed on the database server and anydatabase clients that exist on other machines of the system.

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

Oracle 8.1.7 is only available for NT-INTEL processors.

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

Oracle 8i Release 8.1.7 can be run on Windows 2000. If you want to run 8.1.7 on Windows2000, migrate or upgrade the database first, before you upgrade to the new operating systemversion.

• Windows Domain

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

information on permitted domain names see R/3 Note 314671.

• Important Additional Information

Read the R/3 Note 384495 to find out the latest information on the upgrade andany corrections to this guide.

8/4/2019 UPG_817



6 March 2001

In this documentation, instructions are supplemented by additional informationthat 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 to

be performed repeatedly.

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 under <CD_ROM_DRIVE>:\NT\I386\DOC

To view the documentation open the file index.htm with a browser.

8/4/2019 UPG_817


SAP AG 1 Upgrade of the Database Server

1.1 Multiple Oracle Homes

March 2001 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]

• Set the environment variable NLS_LANG [Page 32].

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

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

• Install the Oracle8i Release 8.1.7 software [Page 13]

•

Install Hot Fix 8.1.7.0.1 [Page 14]• Preparate for the data upgrade [Page 15]

• Upgrade the database data [Page 16]

After the database server upgrade, you need to perform a number of post-upgrade tasks.See Post-Upgrade Activities [Page 19]

1.1 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 samemachine.

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 is being performed, the new Oracle software mustbe installed in a new Oracle home directory.

8/4/2019 UPG_817


1 Upgrade of the Database Server SAP AG

1.2 Backing up the Oracle Source Database and SAP System

8 March 2001

Restrictions

Note 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.2 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 R/3

instance (\usr\sap...) and the Windows NT 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:

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

\WINNT Save the NT 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.

8/4/2019 UPG_817



1.3 Setting the NLS_LANG Variable

March 2001 9

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

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 (not available for Alpha)

• 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 Note 142635.

1.3 Setting the NLS_LANG Variable

Use

Set the NLS_LANG variable in the user environment of <SAPSID>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 <SAPSID>adm

b. At the command prompt, start the Oracle Server Manager with the appropriate startupcommand for your Oracle version:

Oracle 7.3 Oracle8 Oracle8.1

svrmgr23 svrmgr30 svrmgrl

<SERVER_MANAGER_CALL>

SVRMGR> connect internal/<password>@<SAPSID>

If you normally do not use a password for the connection, leave it out of the command.

8/4/2019 UPG_817



1.4 MSCS Only: Removing the DB from the Fail Safe Group

10 March 2001

c. Enter the following command in a single line:

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 NT user environment of <SAPSID>adm. If you are

upgrading or migrating a database client do this on the client machine.

− If NLS_CHARACTERSET has the value WE8DEC, set NLS_LANG to AMERICAN_AMERICA.WE8DEC

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

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

1.4 MSCS Only: Removing the DB from the FailSafe Group

Use

In a cluster configuration, the SAP database has to be removed from the Oracle Fail Safe Groupbefore the upgrade can begin.

Procedure

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

1. In the Cluster Administrator, take the R/3 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 Server service isrunning.

For Oracle Fail Safe version 2.1.3:

Choose Fail Safe Groups → Oracle<SAPSID> → Fail Safe Databases and select your SAPdatabase <SAPSID>.world . Click the right mouse button and choose Remove from group.

For Oracle Fail Safe version 3.04:

Choose Groups → Oracle<SAPSID> → Cluster Resources and select <SAPSID>.world .Click the right mouse button and choose Remove from Group.

To find out under which account the Cluster Server service is running, choose

Start → Settings →==Control Panel → Services. Select the Cluster Server serviceand click Startup... The log on account for the service is displayed. Enter thisaccount for Oracle Fail Safe Account/Password.

For more information about services, see Checking Services [Page 33].

8/4/2019 UPG_817



1.5 MSCS Only: Upgrading to OFS 3.1.1

March 2001 11

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 operationcompleted 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 2.1.3 or 3.0.4, youmust upgrade to version 3.1.1.

Procedure

Install Oracle Fail Safe 3.1.1 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 Server service is running on both nodes.

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

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

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

4. Uninstall the old OFS software on both nodes before you install OFS 3.1.1. The steps differ,

depending on whether you are upgrading from start version OFS 2.1.3 or 3.0.4. Follow theinstructions for your source release.

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

Start Version OFS 2.1.3

a. Start the Oracle Installer with Start → Programs → Oracle for Windows NT → OracleInstaller

b. Under Products Installed , select:Oracle Fail Safe Manager 2.1.3.0.0 Oracle Fail Safe Server 2.1.3.1.0

c. Choose Remove

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

e. In the dialog box Unregister Oracle database resource from the cluster , click No in thepopup that asks whether you want to unregister the Oracle database resource from thecluster.

f. Click Exit to close the Oracle Installer .

8/4/2019 UPG_817




12 March 2001

Start Version OFS 3.0.4

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

the directory <CD_DRIVE>:\NT\I386\INSTALL

b. In the Inventory window, expand <Failsafe_Home> and select Oracle FailSafe 3.0.4

c. Choose Remove

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

e. Click Exit to close the Oracle Installer .

5. Install Oracle Fail Safe version 3.1.1:

a. Insert the Oracle Fail Safe CD.

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

directory<CD_DRIVE>:\NT\I386\INSTALL

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 withthe text The exception unknown software exception ..., check the TMP and TEMPvariables. In the user environment of <SAPSID>adm, make sure that these refer to existing files. If not, reset them.

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 Safesoftware. The software must be installed in a separate Oraclehome, for example, Failsafe

Use the same Oracle home for both nodes.

If Oracle Fail Safe 3.0.4 was previously installed, you can use

the old Oracle Fail Safe home for 3.1.1

Path:Enter the path of the Oracle Home directory for the Fail Safesoftware. It must be on a local disk. For example,F:\Oracle\OFS

Installation types Choose Typical.

8/4/2019 UPG_817



1.6 Installing the Oracle8i Release 8.1.7 Software

March 2001 13

Screen Entry

Reboot Needed After Installation

Choose Next.You reboot later when the installation of the OFS software iscomplete.

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 theaccount and password under which Fail Safe software is to run.This must be the same account as the one under which theCluster Server service is running.

To find out which account must be entered, choose Start →

Settings →==Control Panel → Services. Select the Cluster Server service and click Startup... The log on account for the service isdisplayed. 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.0.4 is in progress on the other node.


Procedure

MSCS only:Install the Oracle 8.1.7 software on both nodes. Ensure that you are logged on toNT as user <SAPSID>adm.

Installing Oracle 8.1.7

1. Place the CD Oracle RDBMS in the CD drive.

Start the Oracle Universal Installer from the directory:

<CD_DRIVE>:\NT\I386

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

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

8/4/2019 UPG_817




14 March 2001

2. Enter information as shown in the table below.

During the installation you can ignore the progress bar which always indicates100% When the installation is complete the progress bar disappears.

If the Installer aborts and an error is displayed in an Application Error window withthe text The exception unknown software exception ..., check the TMP and TEMPvariables. Make sure that these variables in the user environment of <SAPSID>adm refer to existing files. If not, reset them.

If during the installation an error is reported when writing to a DLL file, the DLLhas the read-only attribute. In this case, before you continue the installation, opena command prompt and remove the read-only attribute with the command:

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

Window Entry

1. File Locations Under Source:

The path to the Oracle source software isdisplayed. Do not change the path.

Under Destination:

For Nameenter the name of the new Oracle Home directory.SAP recommends the name<SAPSID><ORACLE_VERSION>, for example,C11817

For Pathenter the path of a new Oracle Home directory.SAP recommends:<DRIVE>:\ORACLE\<SAPSID>\<ORA_VERS>, for

example,

C:\ORACLE\C11\817

Caution: Do not specify an already existing Oracle

Home directory. You must specify a newdirectory.

2. Net8 Configuration Assistant: Welcome

Select Perform typical configuration.

3. End of Installation Choose Exit .

8/4/2019 UPG_817



1.7 Installing Hot Fix 8.1.7.0.1

March 2001 15

1.7 Installing Hot Fix 8.1.7.0.1

Use

When you have installed the Oracle 8.1.7 software, install patch 8.1.7.0.1.

Procedure

MSCS only:Install the hot fix 8.1.7.0.1 on both nodes.Before you begin:

− Stop the services of the new Oracle 8.1.7 version. The name of theseservices includes the new <ORACLE_HOME_NAME>

− In the Cluster Administrator, set the Fail Safe resource offline

− Continue with step 2 belowFor more information see Starting or Stopping Services [Page 33].

1. Make sure that the services for the new Oracle 8.1.7 version are stopped. These serviceshave a name that includes the new <ORACLE_HOME_NAME>

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

2. Insert the Oracle RDBMS CD into the CD drive.

3. Change to the directory

<CD_DRIVE>:\NT\I386\PATCHES\8.1.7.0.1

4. Double-click one of the following programs:

On a database server double-click sap81701srv.exeOn a database client double-click sap81701cl.exe

The dialog box Winzip Self-Extractor appears.5. Click Browse and then select the Oracle home directory where the hot fix is to be installed.

6. Click Unzip to extract the files to the selected Oracle home directory. Confirm thereplacement of all files.

If any files cannot be written, find out the reason and then repeat the above steps.

8/4/2019 UPG_817



1.8 Preparing for the Data Upgrade

16 March 2001

1.8 Preparing for the Data Upgrade

Use

Before the data can be upgraded with the Data Migration Assistant , you need to perform anumber of preparatory tasks.

Procedure

MSCS only:The changes to the init<SAPSID>.ora file are only necessary on node A. Theother steps are necessary on both nodes.

1. Open the Oracle file init<SAPSID>.ora in the SAPpad editor. It is located in the directory<ORACLE_HOME>\DATABASE

2. Change the parameters in the init<SAPSID>.ora file as specified below.

MSCS only:Change parameters on node A only.

− If they exist, delete the parameters:

• OPTIMIZER_FEATURES_ENABLE

• OPTIMIZER_SEARCH_LIMIT

• COMPATIBLE

− Change the LOG_CHECKPOINT_INTERVAL parameter setting to:

LOG_CHECKPOINT_INTERVAL = 300000

− Add or change the parameter:LOG_BUFFER = 1048576

3. In the environment of the user <SAPSID>adm, delete the variables listed below.

MSCS only:Delete the variables on both nodes.

• ORACLE_HOME

• TNS_ADMIN (if it exists)

4. Log off and log on again to activate the changes to the NT environment.

8/4/2019 UPG_817



1.9 Upgrading the Database

March 2001 17


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 onnode A.

1. Stop the SAP System.

2. Start the Oracle Data Migration Assistant from the Start menu with:

Start → Programs → Oracle - <NEW_ORACLE_HOME> → Migration Utilities → Oracle DataMigration Assistant

The Oracle Data Migration Assistant (ODMA) 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.

Screen Input

1. ODMA:Welcome Choose Next .

2. Before you Migrateor Upgrade

Choose Next

3. Select a DatabaseInstance

Select <SAPSID>-<old_Oracle_home>

4. ODMA: DatabasePassword and Init.Ora Files

Password : This refers to the password used for theconnect internal command. Normally nopassword is used for the command and you canenter an arbitrary string here. If you do normally usea password, you must enter it now.Init.ora file:

Confirm the location of the INIT.ORA file.

5. ODMA: ChooseMigration Type

Select Default.

6. ODMA: Backup Your Database

Select I have already backed up my database.

8/4/2019 UPG_817




18 March 2001

Screen Input

7. ODMA: Start the

Migration or Upgrade

Choose Next to start the data upgrade.

A dialog box appears and requests you to confirmthat you want to start the data upgrade.

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

9. Listener.oraMigrationConfirmation

Choose Yes to migrate the Listener

10. ODMA: Finish The upgrade has been completed. Choose View Summary to view log information. You can ignoretwo entries indicating an ORA-00604 error. Choose

Finish to exit the Migration Assistant .

8/4/2019 UPG_817


SAP AG 2 Post-Upgrade Activities

2.1 Modifying the Oracle Net8 Configuration

March 2001 19

2 Post-Upgrade Activities

Process Flow

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

• Modification of the Oracle Net8 configuration []

• Configuration tasks [Page 20]

• Deletion of the old Oracle software [Page 24]

• Setting of user environment variables [Page 25]

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

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

• Backup of the Oracle8 Database [Page 29]

• Upgrade of Database Clients [Page 29]


Use

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

Procedure

MSCS only:Modify the Net8 Configuration only on node A where the database is located.

1. Stop the old Oracle Listener service.

2. Start the Net8 Assistant that guides you through the Net8 configuration process. To do this,

choose Start → Programs → Oracle - <NEW_ORACLE_HOME> → Network Administration

→ Net8 Assistant

The assistant opens.

3. On the Net8 Assistant 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 OracleNames.

In the field Default Domain, enter world

Leave the other settings unchanged.

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.

8/4/2019 UPG_817


2 Post-Upgrade Activities SAP AG


20 March 2001

Address tabs appear.

b. Check all the address tabs. On the tab with the port number 2481, the option Dedicatethis 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 configuration for the Listener for the database server .

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

Choose Edit → Rename and enter the name <SAPSID>.world

e. Under Service Naming select <SAPSID>.world . On the right, choose the plus icon toopen a dialog box for a new address. Enter the port number 1527 a second time if it is

free. Under Service Identification select Use Oracle8i Release 8.0 Compatible

Identification. For SID enter the name of your system <SAPSID>.

Note that this is the configuration of the Listener for the database client.

If the option Use Oracle8i 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 Net8 Assistant.

7. Multiple Oracle Homes only:

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 thanone listener. To check existing numbers in the Net8 Assistant :

a. Choose File →==Open Network Configuration

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

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

c. 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 dothis for both the client and server using the Net8 Assistant as described earlier.

d. Restart both the old and new TNSListener services.

If the TNSListener for Oracle 8.1.7 cannot be started, the Net8 configuration is

incorrect.

8. Start the Oracle Listener for Oracle 8.1.7

8/4/2019 UPG_817



2.2 Configuration Tasks

March 2001 21


Use

Several manual steps must be performed to set up the database server correctly for Oracle 8.1.7.

Procedure

MSCS only:Some of the following steps must be performed on node A, others on node B.Make sure 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 OracleFail Safe Manager and verified the cluster as described later.

1. In the <ORACLE_HOME> directory for 8.1.7, create the subdirectory SAP. From the RDBMSCD, copy all the files from the directory <CD_DRIVE>:\NT\I386\SAP to the new SAP

directory.

MSCS only:Copy the files to both nodes.

2. If it exists, copy the file protocol.ora located in a subdirectory of the old Oracle home to

a subdirectory of the new Oracle home.

MSCS only:

Copy protocol.ora on node A only.

The location of protocol.ora depends on the Oracle source version you are upgrading

from:

− For source 8.0.x: <ORACLE_HOME>\net80\admin

− For source 8.1.x: <ORACLE_HOME>\network\admin

The location in the new Oracle Home can, for example, be:<DRIVE>:\ORACLE\<SAPSID>\817\network\admin

3. Copy all the init<SAPSID>.* files from a subdirectory of the old Oracle home to a

subdirectory of the new Oracle home.

MSCS only:

Copy init<SAPSID>.* files on node A only.

The default location of the init<SAPSID>.* files under the old Oracle Home is

<ORACLE_HOME>\DATABASE

For example, if the start version for the upgrade is 8.0.x this can be:

<DRIVE>:\ORANT\DATABASE

8/4/2019 UPG_817




22 March 2001

The location of the init<SAPSID>.* files under the new Oracle Home can, for example,

be:

<DRIVE>:\ORACLE\<SAPSID>\817\DATABASE

4. Use the Oracle Administration Assistant for Windows NT to change parameter values.

MSCS only:

Change the parameter values on node A only.

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

− Administration Assistant

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

<NEW_ORACLE_HOME>→=Database Administration →= Oracle Administration Assistant for Windows NT

The Assistant opens.

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

→= <Oracle_Home_Name for 8.17>

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

In the Properties dialog box, change the entry for ORA_<SAPSID>_PFILE to:

<ORACLE_HOME>\DATABASE\init<sapsid>.ora

Set the entry for ORA_<SAPSID>_AUTOSTART to FALSE

− Registry

i. Choose Start →= Run and then enter regedit.

ii. Expand HKEY_LOCAL_MACHINE →=SOFTWARE→ORACLE →<HOMEX>Where <HOMEX> is the Home for Oracle 8.1.7>

iii. Change the parameters as required.

5. Start the Oracle Services. Set the startup type of OracleService<SAPSID> andOracle<ORACLE_HOME_NAME>TNSListener to automatic to ensure that they areautomatically restarted after booting.

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

For more information see Starting and Stopping Services for MSCS [Page 39].

6. Start up the database.

Starting Up or Shutting Down the Database for MSCS [Page 37]

8/4/2019 UPG_817




March 2001 23

7. MSCS only:

Move the Oracle<SAPSID> and the SAP-R3<SAPSID> groups to node A. In theCluster Administrator, make sure that the disk groups and the shares SAPMNTand SAPLOC are online on node A.

8. Unpack the SAPDBA database tools.

MSCS only:

Install the SAPDBA tools in the directory<DRIVE>\USR\SAP\<SAPSID>\SYS\EXE\RUN on one node only. Also install

them in the directory %winnt%\SapCluster on both 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

9. In the User Manager make sure that the user SAPService<SAPSID> is included in thelocal group ORA_<SAPSID>_DBA.

MSCS only:Do this on both nodes.

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

10. Only for previous versions lower than Oracle 8.1.5

Run the script oradbusr.sql

MSCS only:Perform the steps on node A where the database is located.

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

b. Switch to the directory <ORACLE_HOME>\SAP

Start the script oradbusr.sql. To do this, enter one of the following commands:

• If the SAP System is running with a local SAPService<SAPSID> user enter:

sqlplus internal @oradbusr.sql NT <hostname>

You can find out under which user the SAP system is running under Control

Panel → Services. Select the service SAP<SAPSID>_<Instance_no.> andclick Startup. In the Service dialog box, under Log On As, you can see whether the user is a domain or local user.

• If the SAP System is running with a domain <SAPSID>Service user enter:

8/4/2019 UPG_817



2.3 Deleting the old Oracle Software

24 March 2001

sqlplus internal @oradbusr.sql NT <domain_name>

c. Enter the command:

sapdba -sapr3 <user_password>

Enter a new password for the database user sapr3. If an error occurs, change thecommand to the following:

sapdba -u <user_name>/<password>

Where <user_name> must be a user with DBA rights.


Procedure

Delete the old Oracle 8.0.x or 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 Fail Safe resource offline

− Stop the Cluster Server service on both nodes

− Continue with step 21. Shut down the database.

2. Stop the service Distributed Transaction Coordinator.

3. Stop the Oracle 8.0.x or 8.1.x Services in the Control Panel.

4. Follow the instructions for your Oracle start version.

Start version 8.0.x

a. Start the Oracle 8.0.x installer with Start → Programs → Oracle for Windows NT →Oracle Installer

b. In the Software Asset Manager Screen, select the products that are displayed andchoose Remove. If you cannot remove a product leave it and delete the next one.

Start 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 RDBMS CD. Double-clickthe file setup.exe in the directory <CD-DRIVE>:\NT\I386

b. In the Welcome screen, choose Deinstall Products

8/4/2019 UPG_817




March 2001 25

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 OracleClient 8.1.x and then select Oracle Client 8.1.x

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

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

5. Delete the old Oracle 8.0.x or 8.1.x services that still exist. To delete a service, open acommand prompt and enter:

ntscmgr remove <service_name>

The following services must be left after the deletion:

Oracle<ORACLE_HOME_NAME>AgentOracle<ORACLE_HOME_NAME>ClientCacheOracle<ORACLE_HOME_NAME>DataGathererOracle<ORACLE_HOME_NAME>TNSListenerOracleService<SAPSID>

MSCS only:The OracleFailSafe service must be left after the deletion.

Multiple Oracle Homes only:On a database server with multiple homes, do not delete the serviceOracleService<SAPSID>. If more than one Listener is configured, do not deletethese either.

6. In the Windows NT Explorer delete the Oracle Home directory of the 8.0.x or 8.1.x software.

The home directory for 8.0.x can be <DRIVE>:\ORANT

The home directory for 8.1.x can be <DRIVE>:\ORACLE\<SAPSID>\81x7. In the Windows Explorer delete the following directory, if it exists:

Windows NT:

%WINDIR%\PROFILES\ALL USERS\START MENU\PROGRAMS\ORACLE FOR WINDOWS NT

Windows 2000:DOCUMENTS AND SETTINGS\ALL USERS\START MENU\PROGRAMS\ORACLE FOR WINDOWS NT

This deletes the entries in the NT Start menu.

Do not delete the Registry key for the earlier Oracle version, for example:

HKEY_LOCAL_MACHINE → SOFTWARE → ORACLE → HOME0

8/4/2019 UPG_817



2.4 Setting Environment Variables

26 March 2001

2.4 Setting Environment Variables

Procedure

MSCS only:Edit the variables on both nodes.

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

1. In the user environment of <SAPSID>adm, check the PATH variable and remove all partsreferring to the old Oracle version.

If you have two or more co-existing Oracle Homes, each <SAPSID>adm user hasa different Oracle home. For each of these users, enter the following in thecorresponding PATH variable of the user environment:

<Oracle_Home>\binNote 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 oldOracle 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 correctvalue for Oracle 8.1.7. For example to: <DRIVE>:\ORACLE\C11\817

MSCS only:Set the variables on both nodes.

4. Only releases prior to 4.6A

MSCS only:Run ntenv2reg on both nodes.

8/4/2019 UPG_817



2.5 MSCS Only: Configuring Node B

March 2001 27

In the Cluster Administrator , make sure that the SAP-R3<SAPSID> group, the SAPdisks and the shares SAPMNT and SAPLOC are online on node A.

Open a new command prompt and run the script ntenv2reg

Enter the following:

ntenv2reg

In the dialog box that appears, select the instance you want to upgradeSAP<SAPSID>_<INSTANCE_NO>

For example, SAPC11_09

5. Additional configuration task only for database clients:

Copy the files sqlnet.ora, tnsnames.ora and protocol.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

6. Reboot the computer.

2.5 MSCS Only: Configuring Node B

Procedure

1. Copy files from the primary node A to node B:

a. Make sure that the Cluster Server service is running on node B.

b. Copy the files init<SAPSID>.* from node A <ORACLE_HOME>\database to the

same directory on node B.

c. Copy the files protocol.ora and 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 Server service is running on both nodes.

2. Start the Cluster Administrator.

3. In the Cluster Administrator bring the Oracle Fail Safe resource online.

4. Start the Oracle services. Make sure the Oracle<ORACLE_HOME_NAME>TNSLISTENER andOracleService<SAPSID> are online.

5. Start up the database.

8/4/2019 UPG_817



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

28 March 2001

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

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

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

If you leave out this step, you cannot add the database to the Fail Safe Group.

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

9. In the Welcome dialog box choose Verify Cluster .

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

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 completed

successfully, close the window.10. Add the SAP database to the Fail Safe group Oracle<SAPSID>

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

b. Choose Resources=→ Add to Group

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

12. On the dialog box Add Resource to Group – Database Identity: Step 2 of 3, enter thefollowing and then choose Next :

Database Name <SAPSID>

Parameter File <ORACLE_HOME>\database\init<SAPSID>.ora

13. In the window Add Resource to Group – Database Authentication: Step 3 of 3, enter thefollowing and then choose Next :

User name internal

Password : <password>

After the migration to Oracle8, the user is authenticated using the

local NT groups ORA_<SAPSID>_DBA and

ORA_<SAPSID>_OPER. This means that you do not have a

specific Oracle password for the user internal. However, youmust enter something, so enter a password of your choice.

Confirm Password : Repeat the password

8/4/2019 UPG_817



2.7 Backing up the Oracle8 Database

March 2001 29

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

The Adding resource <SAPSID>.world to group window, shows the steps that are executedto add the database to the Fail Safe group.

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

2.7 Backing up the Oracle8 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 Oracle8 database with SHUTDOWN NORMAL.For more information see Starting and Stopping the Database [Page 30]

2. Shut down all Oracle services.For more information see Starting or Stopping Services [Page 33].

3. Make an offline backup of your R/3 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 32]

• Installation of the Oracle 8.1.7 client software [Ext.]

• Application of Hot Fix 8.1.7.0.1 [Page 14]

• Deletion of the old client software [Ext.]

• Setting environment variables [Page 25]

8/4/2019 UPG_817


3.1 Standard Tasks SAP AG

3.1.1 Starting the Server Manager

30 March 2001

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 the Server Manager []

• Starting and Stopping the Database [Page 30]

• Starting the Instance Manager [Page 31]

• Oracle services [Page 31]

• Setting the NLS_LANG environment variable [Page 32]

• Checking Services [Page 33]

• Starting or stopping services [Page 33]

• Starting or stopping the SAP System [Page 34]

• Updating the Dynamic Link Libraries [Page 34]

• Deleting a Registry entry [Page 35]

• Setting or deleting environment variables [Page 35]

• Creating a local group [Page 35]

3.1.1 Starting the Server Manager Use

Start the Oracle Server Manager as follows.

Procedure

1. Open a Command Prompt

2. Enter the appropriate command for your Oracle version:

ORACLE 7.3 ORACLE8 ORACLE8.1


8/4/2019 UPG_817


SAP AG 3.1 Standard Tasks

3.1.2 Starting and Stopping the Database

March 2001 31

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 SQL*DBA.

• To start up the database enter:

connect internal/<password>

startup

exit

• To shut down the database enter:

connect internal/<password>

shutdown

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:

ORACLE 7.3 ORACLE8 ORACLE 8.1.x

oradim73 oradim80 oradim

8/4/2019 UPG_817



3.1.4 Oracle Services

32 March 2001

3.1.4 Oracle Services

Definition

Structure

The following services exist after a standard Oracle installation:

ORACLE 7 ORACLE 8.0x ORACLE 8.1.x

OracleService<SAPSID> OracleService<SAPSID> OracleService<SAPSID>

OracleTNSListener OracleTNSListener80 Oracle<ORACLE_HOME_NAME>TNSListener

OracleAgent80 Oracle<ORACLE_HOME_NAME>Agent

OracleClientCache80 Oracle<ORACLE_HOME_NAME>ClientCache

Oracle<ORACLE_HOME_NAME>DataGatherer

3.1.5 Setting the NLS_LANG Variable

Use

Set the NLS_LANG variable in the user environment of <SAPSID>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

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

d. Log on as user <SAPSID>adm

e. At the command prompt, start the Oracle Server Manager with the appropriate startupcommand for your Oracle version:

Oracle 7.3 Oracle8 Oracle8.1


<SERVER_MANAGER_CALL>

SVRMGR> connect internal/<password>@<SAPSID>

If you normally do not use a password for the connection, leave it out of the command.

f. Enter the following command in a single line:

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

8/4/2019 UPG_817



3.1.6 Checking Services

March 2001 33

The value of the parameter NLS_CHARACTERSET is returned.

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

upgrading or migrating a database client do this on the client machine.

− If NLS_CHARACTERSET has the value WE8DEC, set NLS_LANG to AMERICAN_AMERICA.WE8DEC

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

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

3.1.6 Checking Services

Procedure

NT 4.0

1. Choose Start → Settings → Control Panel → Services

2. Select the required service.

The Status shows whether a service has been started.The startup type, automatic or manual, is shown in the column Startup.Choose Startup to change the startup type (field Startup Type) or the user that is assignedto the service (field Log On As).

Windows 2000

1. Choose Start → Programs → Administrative Tools→Services

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

Procedure

NT 4.0

1. Choose Start → Settings → Control Panel → Services

2. Select the service you want to start or stop.

3. Click Start or Stop as required.

8/4/2019 UPG_817



3.1.8 Starting or Stopping the R/3 System

34 March 2001

Windows 2000

1. Choose Start → Programs → Administrative Tools → Services

2. Select the service you want to start or stop.

3. Choose Action → All tasks and then Start or Stop as required.

3.1.8 Starting or Stopping the R/3 System

Procedure

To start or stop the 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 NT System, the R/3 ServiceSAP<SAPSID>_<Instance_number> (for example SAPC11_00) is always startedautomatically.

Using the Microsoft Management Console

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

→ Programs → SAP R3 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 R/3 central instance and the database are started.When you stop the system, only the R/3 System is stopped. The database remains running.

Using the SAP Service Manager

You can start or stop the R/3 processes using the SAP Service Manager s by choosing Start or

stop in the SAP Service Manager .

When the R/3 services receives the stop message from the SAP Service Manager , it stops theR/3 System.

3.1.9 Updating the Dynamic Link libraries

Procedure

1. Insert the SAP Kernel CD into the CD-ROM drive.

2. Switch to the directory <CD_DRIVE>:\NT\I386\NTPATCH

3. Start the program r3dllins.exe

4. Reboot the computer to activate the new settings.

If your DLLs were already up-to-date before you started r3dllins.exe, no new DLLs areinstalled and you are not prompted to reboot.

8/4/2019 UPG_817



3.1.10 Deleting a Registry Entry

March 2001 35

3.1.10 Deleting a Registry Entry

ProcedureStart 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

NT 4.0Choose Start → Settings → Control Panel →= System → Environment .

• To set a variable, enter its name and value in the fields available under User Variables for <user> and then click Set .

• To delete a variable, select it and then click delete.

Windows 2000

To view or change environment variables

1. Choose Start → Settings → Control Panel =→=System.

2. On the System Properties dialog box, choose the Advanced register. 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

Use

The following describes the steps that must be executed locally on the host in order to create thelocal group Example and to insert the domain user Test :

Procedure

Windows NT

Open the User Manager :

1. Choose Start → Programs → Administrative Tools (Common) → User Manager for domains.

2. In the window User Manager - <domain name>, choose User → Select Domain.

8/4/2019 UPG_817



3.1.12 Creating a Local Group

36 March 2001

3. In the window Select domain, define the local host name as follows:\\<name_of_local_server> and choose OK .

4. In the window User Manager - <name_of_local_server>, choose User → New Local Group.

5. In the window New Local Group, enter the group name Example and a suitable description of

the group. Choose Add .

6. In the window Add Users and Groups, select the domain (in which user Test lies) in field List Names from. Select user Test from the list Names. With Add, you can include the user in thelist Add Names.

Choose OK .

7. In the window New Local Group, choose OK and save the local group.

8. Check that the local group Example is displayed in the list of existing groups in the User Manager .

Windows 2000

1. Choose Start →

Programs →

Administrative Tools →

Computer Management.2. From the Computer Management tree, choose Local users and Groups → Groups and then

Action → New Group

The New Group dialog box appears.

3. Enter the Group name and a description.

4. To add members to the group choose Add.

The Select Users or Groups dialog box opens.

5. Under Names, select a user you want to include in the group and then click Add . This user isadded 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 involved in the Computer Management tree and then choose

Action → All tasks → Add to group.

− In the Properties dialog box click Add .

− In the Select Users or Groups dialog box, select the group in which you wantto include the user and choose Add . Click OK to confirm the entry.

8/4/2019 UPG_817


SAP AG 3.2 MSCS Tasks

3.2.1 Starting Up or Shutting Down the Database for MSCS

March 2001 37

3.2 MSCS TasksCommon 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 37]

• Starting and Stopping Services for MSCS [Page 39]

• Stopping the Cluster Server Service [Page 40]

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

• Backing Up the R/3 System for MSCS [Page 41]

3.2.1 Starting Up or Shutting Down the Database for

MSCSProcedure

Always use the Fail Safe Manager to stop the database, if the Cluster Server Service and Fail Safe Service are running. If you do not use the Fail SafeManager , the cluster functionality automatically attempts to restart the database.If the Cluster Server service and Fail Safe service are stopped, you must use theOracle Server Manager to start and stop the database. This is often the caseduring 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<SAPSID>.world in the Fail Safe group ORACLE<SAPSID> . Press the right-hand mousebutton and choose place online.

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

Log on as user <SAPSID>ADM. In the Oracle Fail Safe Manager , select the database<SAPSID>.world in the Fail Safe group ORACLE<SAPSID> and set it to offline.As of Fail Safe Version 2.1 you can choose between the options offline normal , offlineimmediate and offline abort at this point. Choose offline normal .

8/4/2019 UPG_817


3.2 MSCS Tasks SAP AG

3.2.2 Services for MSCS

38 March 2001

3.2.2 Services for MSCS

Definition

The following services exist in an Oracle7 MSCS installation:• Oracle 7.3

• OracleService<SAPSID>

• OracleTNSListener

• OracleAgent

• OracleAgent<virtual DB host name>

• OracleClientCache

• OracleFailSafe

• OracleServiceOFS<n> (Enterprise Manager DB with repository, on one server)

• OracleTNSListener

• OracleTNSListenerFsl<virtual DB host name>

The following services exist in an Oracle8 MSCS installation:


• OracleTNSListener80

• OracleAgent80

• OracleClientCache80

• OracleAgent80<virtual DB host name>

• OracleExtprocAgent

• OracleFailSafe

• OracleServiceOFS<n> (Enterprise Manager database with repository, only on one server)

• OracleTNSListener80Fsl<virtual DB host name>

The following services exist in an Oracle 8i Release 8.1.7 MSCS installation:


• <Oracle-Home>TNSListener

• <Oracle-Home>Agent

• <Oracle-Home>ClientCache

• <Oracle-Home>DataGatherer

• OracleFailSafe

• OracleServiceOFS<n> (Enterprise Manager database with repository, only on one server)

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

8/4/2019 UPG_817



3.2.3 Starting and Stopping Services for MSCS

March 2001 39

3.2.3 Starting and Stopping Services for MSCS

The following services are started with Start → Settings → Control Panel →= Services.

Select the required service, and then choose Start .

Oracle 7.3.4 Oracle 8 Oracle 8.1.7

SAPOsCol SAPOsCol SAPOsCol

OracleAgent OracleAgent80 <Oracle_Home>Agent

OracleTNSListener OracleTNSListener80 <Oracle_Home>TNSListener

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

If during the migration process the Cluster Server service is stopped, you cannotuse the Fail Safe Manager or Cluster Administrator to stop services. In this case,you have to stop them in the Control Panel .However, when the Cluster Server service 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>_<NR> Set the resource SAP R/3 to online. R/3 isstarted up

OracleService<SAPSID> Set the resource <SAPSID>.world in thegroup ORACLE<SAPSID> to online.

or

Set the Fail Safe Database <SAPSID>.world to online in the Oracle Fail Safe Manager

OracleAgent<virtual DB host name>

<ORACLE_HOME>Agent (for 8.1.7)

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

OracleTNSListenerFsl<virtual DB host name> Set the corresponding resource in the groupORACLE<SAPSID> to online

OracleFailSafe Set the resource Oracle Fail Safe in theCluster group to online

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

8/4/2019 UPG_817


3.2 MSCS Tasks SAP AG

3.2.4 Stopping the Cluster Server Service

40 March 2001

3.2.4 Stopping the Cluster Server 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 Server Service is stopped. To restart the service, choose File → = Start Cluster Service.

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

3.2.5 Moving Groups for MSCS

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

Procedure

Cluster Administrator

1. Start the Cluster Administrator with Start → Programs → Administrative Tools → Cluster Administrator.

2. On the left-hand pane, under Groups select the cluster group you want to move. Press theright mouse button and click Move group on the context menu.

The group is now moved to the other node.

Fail Safe Manager 2.1.3

1. Start the Fail Safe Manager 2.1.3 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 andclick Move to different node on the context menu.


Fail Safe Manager 3.0.41. Start the Fail Safe Manager 3.04 with Start → Programs → Oracle- FailSafe → 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 different node on the context menu.


8/4/2019 UPG_817



3.2.6 Starting or Stopping the SAP System for MSCS

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

\WINNT Backing up the NT system NTBACKUP

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

NTBACKUP

UPG_817

Documents

Transcript of UPG_817