UPG_WN_E

Component Upgrade GuideComponent Upgrade GuideComponent Upgrade GuideComponent Upgrade Guide

SAPSAPSAPSAP Web Application Web Application Web Application Web Application

Server 6.20: WindowsServer 6.20: WindowsServer 6.20: WindowsServer 6.20: Windows

Copyright 2002 SAP AG. All rights reserved.

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

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint andSQL Server 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, Informix and Informix Dynamic Server

TM are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE is a registered trademark of ORACLE Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks ofthe Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood , MetaFrame,WinFrame, VideoFrame, MultiWin and other Citrix product namesreferenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registeredtrademarks of W3C, World Wide Web Consortium, MassachusettsInstitute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

J2EE 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 byNetscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,Management Cockpit, mySAP, mySAP.com, and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. MarketSet and EnterpriseBuyer are jointly owned trademarks of SAP Markets and CommerceOne. All other product and service names mentioned are thetrademarks of their respective owners.

DisclaimerSome components of this product are based on Java. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java Source Code delivered with this product is only to be usedby SAPs Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguides

SAP AGSAP AGSAP AGSAP AGNeurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.comwww.sap.comwww.sap.comwww.sap.com

Typographic Conventions

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 otherdocumentation

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

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

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Upgrading to SAP Web Application Server 6.20: Windows

4 March 2002

Contents

Upgrading to SAP Web Application Server 6.20: Windows ......... 8Introduction............................................................................................ 9

How to Use this Documentation................................................................10New Features in the SAP Web Application Server Upgrade...................12Naming Conventions for the SAP Web Application Server Upgrade.....13

Upgrade Step by Step ...................................................................... 15SAP Notes for the SAP Web Application Server Upgrade .............. 26Product-Specific Information for the SAP Web AS Upgrade .......... 31

Planning the SAP Web Application Server Upgrade ...............................32Planning the Upgrade Strategy ............................................................................................32Upgrade Schedule Planning ................................................................................................33Runtime for the Import of the Substitution Set .....................................................................33Checking Hardware Requirements ......................................................................................34Checking the Source Release of the SAP System ..............................................................35Upgrading the Operating System and Database System: Overview ...................................35

Preparing the SAP Web Application Server Upgrade .............................41Creating the Upgrade Directory............................................................................................41Checking Database-Specific Requirements for PREPARE.................................................42Making Entries for the Parameter Input Module ..................................................................44

SAP Web Application Server Upgrade: Post-Upgrade Activities ...........45DB2 UDB for UNIX and Windows: Specific Actions.............................................................45

General Upgrade Information............................................................. 49Planning the Upgrade ................................................................................50

Time Frame for Upgrading the Frontend Software ..............................................................52System Switch Upgrade.......................................................................................................53Planning the Upgrade Strategy ............................................................................................55Database Backup.................................................................................................................59Database-Specific Aspects ..................................................................................................60Upgrades in an MCOD System Landscape .........................................................................64Incremental Table Conversion .............................................................................................65Upgrade Schedule Planning ................................................................................................67Runtime for the Import of the Substitution Set .....................................................................70Upgrading in an SAP System Group....................................................................................70Planning the Modification Adjustment ..................................................................................71Check structural requirements .............................................................................................73Checking Hardware Requirements ......................................................................................74Checking Software Requirements........................................................................................74

Checking the Source Release of the SAP System............................................................75Meeting the Requirements for the Upgrade Assistant.......................................................75Upgrading the Operating System and Database System: Overview ................................76

Accessing Documentation Before and During the Upgrade ................................................76Meeting the Requirements for the SAP Internet Solution ....................................................77Importing Additional Languages...........................................................................................78

Upgrade Preparations ................................................................................79


March 2002 5

Determining the Host for the Upgrade Preparations............................................................81Making Preparations for Reading the Upgrade CDs............................................................81Creating the Upgrade Directory............................................................................................82Checking Database-Specific Requirements for PREPARE.................................................83Substituting the SAP Kernel (Source Release 3.x)..............................................................83Importing the Latest SPAM Update (Source Release 4.x and Higher)................................84Checking SAP Programs (Source Release 4.x and Higher)................................................85Windows NT 4.0: Checking the Consistency of the Host Name..........................................89Starting PREPARE for the First Time ..................................................................................90Starting the Upgrade Assistant Server.................................................................................91Starting the Upgrade Assistant GUI .....................................................................................91Starting the Upgrade Assistant ............................................................................................92Restarting PREPARE from the Upgrade Assistant GUI ......................................................93Restarting PREPARE...........................................................................................................94Resetting PREPARE............................................................................................................94Importing Software After Starting PREPARE.......................................................................95General Input for PREPARE ................................................................................................95Making Entries for the Parameter Input Module ..................................................................96Making Entries for the Initialization Module........................................................................100Making Entries for the Import Module ................................................................................101Making Entries for the Extension Module...........................................................................101Making Entries for the Installation Module .........................................................................107Making Entries for the MSCS Configuration ......................................................................109Evaluating the Results of PREPARE .................................................................................109Making Preparations at the Operating System Level.........................................................114Making Preparations at the Database Level ......................................................................114Making Preparations at the SAP System Level .................................................................116

Deleting the AUTOSTART Parameter.............................................................................117Checking the User for the Upgrade .................................................................................117Checking Requirements for the Modification Adjustment................................................117Setting the Operation Mode for the Upgrade ..................................................................118Processing Batch Input Sessions (Source Release 3.x) .................................................119Converting the Translation Proposal Pool (Source Release 3.x) ....................................119Processing Direct Input Error Data (Source Release 3.x)...............................................120

The Upgrade..............................................................................................121Upgrading with Microsoft Cluster Server............................................................................123Starting the Upgrade ..........................................................................................................123Stopping the Upgrade ........................................................................................................124Restarting the Upgrade ......................................................................................................124Monitoring the Upgrade......................................................................................................126

Alert Function...................................................................................................................126Upgrade Logs ..................................................................................................................127

Phase INITPUT ..................................................................................................................130Phase PATCH_CHK ..........................................................................................................130Phase KEY_CHK ...............................................................................................................131Phase INITSUBST .............................................................................................................131Phase CONFCHK_X..........................................................................................................133Phase VIEWCHK1 .............................................................................................................133Phase REPACHK1.............................................................................................................133Phase JOB_RSVBCHCK2 .................................................................................................134Phase FREECHK_X...........................................................................................................134Phase LOCKEU_PRE........................................................................................................135EU_IMPORT Phases .........................................................................................................136Phase REPACHK2.............................................................................................................137Phase CNV_CHK_XT ........................................................................................................138


6 March 2002

Phase ADJUSTCHK...........................................................................................................138Phase ACT_...............................................................................................................138Phase VIEWCHK2 .............................................................................................................140Phase MODPROF_TRANS................................................................................................140Phases JOB_RSVBCHCK3 and JOB_RSVBCHCK4 ........................................................141Continuing the Upgrade After the MODPROFP_UPG Phase............................................142Phase CHK_POSTUP........................................................................................................143

Post-Upgrade Activities ...........................................................................144DB2 UDB for UNIX and Windows: Specific Actions...........................................................146DB2 UDB for OS/390: Specific Actions..............................................................................146Informix: Specific Actions ...................................................................................................147MS SQL Server: Specific Actions.......................................................................................148Oracle: Specific Actions .....................................................................................................148SAP DB: Backing Up the Database ...................................................................................150Post-Upgrade Activities for the Microsoft Cluster Server...................................................150Upgrading the Application Servers.....................................................................................151Checking Profile Parameters with Transaction RZ10 ........................................................153Installing the SAP J2EE Engine .........................................................................................154Reimporting Additional Programs ......................................................................................154Adjusting Repository Objects .............................................................................................155Performing Post-Upgrade Activities for the Applications ...................................................155Configuring Single Sign-On with the Microsoft NT LAN Manager SSP .............................157Adjusting Start and Stop Procedures (Source Release Lower than 4.6A) ........................162Rescheduling Background Jobs.........................................................................................162Rescheduling DB13 Jobs (Source Release 3.x) ................................................................163Migrating Matchcodes to Search Help Objects (Source Release 3.x)...............................164Informix: Updating Statistics...............................................................................................164Oracle: Actions for the Cost-Based Optimizer ...................................................................165SAP DB: Updating Optimizer Statistics..............................................................................167Generating ABAP Loads ....................................................................................................167Generating BSP Applications.............................................................................................168Performing Actions for the SAP Online Documentation.....................................................168Performing Post-Upgrade Activities in the Authorizations Area.........................................169Processing Table Clusters After the Upgrade (Source Release 3.x).................................171Installing More Dialog Instances ........................................................................................172Importing Support Packages After the Upgrade ................................................................172Transport Management System: Distributing the Configuration ........................................173Perform post-upgrade activities for the language transport ...............................................173DB2 UDB for OS/390: Removing Empty Database Objects ..............................................174Oracle: Deleting Tablespaces ............................................................................................174Converting Batch Input Logs..............................................................................................175Evaluating the Upgrade Runtime .......................................................................................175

Troubleshooting ................................................................................ 177Analyzing the ELG Log Files ................................................................................................178Correcting Errors in the RFCCHK Phase .............................................................................180Correcting Entries from the INITPUT and INITSUBST Phases............................................180Correcting Errors in the DBCHK Phase................................................................................181Correcting Errors in the BATCHCHK Phase.........................................................................182Correcting Errors in the INTCHK and INTCHK_SW Phases................................................183Correcting Errors in the SPACECHK_ALL Phase ................................................................183Correcting Errors in the JOB Phases....................................................................................185Cleaning Up Terminated Conversions in the DB Conversion Phases .................................186Correcting Errors in the TRBATCHK_XT Phase ..................................................................188Correcting Errors in the RUN_RDDIT006 Phase .................................................................189


March 2002 7

Correcting Errors in the ACT Phase .....................................................................................190Correcting Lost Field Problems in the PARDIST Phase.......................................................191Correcting Conversion Problems in the PARCONV Phase..................................................192Correcting Errors in the XPRAS Phase ................................................................................193Preparing the Restart of the Upgrade After a System Failure ..............................................195Resetting the Upgrade..........................................................................................................196Correcting Problems when Processing ABAP Steps............................................................199Correcting Problems when Starting the SAP System...........................................................200Correcting Problems when Copying SAP Programs ............................................................201Providing SAP Support with Information...............................................................................201

Upgrade Administration ................................................................... 203Determining Versions............................................................................................................203Setting the Environment of the SAP Kernel..........................................................................205Creating Shares and Directories and Checking Authorizations............................................205Changing the Virtual Memory/Paging File Size ....................................................................206Isolating the Central Instance ...............................................................................................207Extending Free Space in the Database................................................................................209Changing the Database Recovery Mode..............................................................................212Using a Different Upgrade Directory.....................................................................................214Releasing and Confirming Open Repairs and Requests......................................................215Sending a Message when User Action Is Required .............................................................217

Upgrade Tools ................................................................................... 218PREPARE ..................................................................................................218

Phase List PREPARE for the SAP Web Application Server Upgrade ...............................221R3up ..........................................................................................................235

Phase List R3up for the SAP Web Application Server Upgrade........................................236Upgrade Phases: Preparations ..........................................................................................237Upgrade Phases: Shadow System ....................................................................................244Upgrade Phases: Conversions and Import ........................................................................248Upgrade Phases: Post-Upgrade Activities .........................................................................252

Upgrade Assistant....................................................................................255Using the Upgrade Assistant..............................................................................................256

Upgrade Monitor.......................................................................................258Starting the Upgrade Monitor .............................................................................................259Understanding the Upgrade Monitor Display .....................................................................260

Introduction

8 March 2002

Upgrading to SAP Web ApplicationServer 6.20: WindowsPurposeThis documentation describes the procedure for upgrading from SAP Basis 4.6D and higherto SAP Web Application Server 6.20. It also contains additional useful information about theupgrade. The information in this documentation is intended for SAP system administratorswith operating system, database, and SAP Web Application Server knowledge.

The Upgrade Step by Step [Page 15] section is a list of all actions that you must perform toupgrade your system successfully. The actions are placed in chronological order, so that youcan work through them just like a checklist.

The following two sections of this documentation explain the upgrade procedure in detail:

Product-Specific Information for the SAP Web Application Server Upgrade [Page 31]

General Upgrade Information [Page 49]

The next three sections of this documentation give you additional information ontroubleshooting, the administration tasks you need to perform before and after the upgrade,and the tools that you use to upgrade the system:

Troubleshooting [Page 177]

Upgrade Administration [Page 203]

Upgrade Tools [Page 218]

Both the structure of the documentation [Page 10] and the upgrade procedure[Page 53] itself have changed significantly for SAP Web Application ServerRelease 6.10.

ConstraintsThis documentation only applies if you are upgrading your SAP system on Windows.In addition to this documentation, you require some other information, such as the ReleaseNotes for the applications that you implement, the SAP Implementation Guide (IMG), the SAPNotes that are specific to this upgrade [Page 26], and any other documentation referred to inthis documentation.

Introduction

March 2002 9

IntroductionThis section of the documentation contains general information on:

Using the documentation [Page 10]

In SAP Web Application Server Release 6.10 the structure of the upgrade documentationhas been changed from a process flow description with additional information to aninformation pool.

New features in the upgrade procedure [Page 12]

The upgrade procedure is continually being enhanced. This section contains the mostimportant changes to the procedure, for both current and previous releases.

Naming conventions [Page 13]

This section explains the terminology and abbreviations used in this documentation.

Introduction

10 March 2002

How to Use this DocumentationThe documentation on upgrading the SAP system contains a large amount of information. Itsaim is to give you both the information you need immediately at your fingertips, as well asproviding additional background information when required. Treat the documentation as apool of information.

If you have a lot of experience in upgrading the SAP system, you will probablyonly need the parts Upgrade - Step by Step [Page 15], Product-SpecificInformation [Page 31] and SAP Notes [Page 26].

Structure of the Documentation

Product-specific

information

Introduction

Upgrade Documentation

Upgrade - Step by Step

Minimum processinformation required

Legend:Generalprocess flowof upgrade

Problems and solutionsUpgrade administration

Upgrade toolsLinks to references

Additionalinformation

Austausch-SAP

Notes

The documentation consists of the following parts:

Introduction

The first sections of this documentation are as follows:

New Features [Page 12]

Naming Conventions [Page 13]

They contain information on new features in the upgrade for the last few releases, and onthe naming conventions used in the documentation.

Upgrade Step by Step [Page 15]

This section is the core of the documentation. It is a list of all actions that you mustperform to upgrade your system successfully The short descriptions of the individualactions contain the following:

Important information, such as user entries

Links to a detailed description of the action

Introduction

March 2002 11

Links to any product-specific information about the action

The upgrade actions are listed chronologically. Use the Upgrade Step byStep section as a checklist for upgrading the system. This ensures that youdo not miss important information.Use the links to the general descriptions of the actions and to any additionalproduct-specific information to help you perform the actions.

SAP Notes for the Upgrade [Page 26]

This section contains a list of SAP Notes relevant for the upgrade.

Product-Specific Information [Page 31]

This part of the documentation contains additional information or restrictions on thedescriptions under General Upgrade Information, which only affect this specific SAPproduct.The headings of the sections are the same as the corresponding sections in GeneralUpgrade Information. Each product-specific text contains a link to the general descriptionof the action.

The information in the product-specific sections takes priority over theinformation in the general sections of the documentation.

General Upgrade Information [Page 49]

This part of the documentation is a general description of the upgrade of an SAP system.It contains procedures and background information about the upgrade process flow andthe individual actions. However, it does not contain all the information you need for theupgrade of your specific SAP product. Any extra details about the upgrade of yourproduct are in the Product-Specific Information [Page 31] part of the documentation.

Additional Information

The next three parts of this documentation are as follows:




These sections contain information on troubleshooting, the administration tasks you needto perform before and after the upgrade, and the tools that you use to upgrade thesystem.

Use the links from the Upgrade Step by Step [Page 15] section to the general descriptionsof the actions and to any additional product-specific information to help you perform theactions.

Introduction

12 March 2002

New Features in the SAP Web ApplicationServer UpgradeNew Features in the Upgrade to SAP Web Application Server 6.20 Reading the upgrade CDs

The contents of the upgrade CDs are read using a new procedure. You have to install aJava Runtime Environment (JRE) on the host where the upgrade is performed, and youhave to adjust certain environment variables.

New procedure for dealing with add-ons

In the IS_SELECT phase, you can also include SAINT packages in the upgrade thatwere previously in the transport directory.

Calculating an add-on queue

If you made a decision in the IS_SELECT phase for all add-ons, a new queue calculationis triggered. This calculation checks whether the import prerequisites can be met for theadd-ons, and determines the sequence in which the corresponding requests areimported.

New functions for including Support Packages

To import Support Packages in the BIND_PATCH phase, the following Support Packagelevels are determined and taken into consideration for each component:

a. Minimum required Support Package level

Support Package level that the included add-ons of the target release require as animport prerequisite. The add-on queue calculation determines the minimum requiredSupport Package level.

You are not allowed to select a Support Package level that is lower than theminimum level.

b. Equivalence Support Package level

You can define attributes for the Support Packages of the source release thatdetermine which Support Package in a higher release corresponds to the one in thesource release. This Support Package must be included so that no data is lost in theupgrade.

PREPARE determines this equivalence Support Package level in the PATCHK_EQUIVphase.

The minimum and the equivalence Support Package level for each component aredisplayed on the dialog screen (wizard).

Conflict check

To check whether the add-on requests and CRTs are complete, PREPARE triggers aconflict check. You are then prompted to include the corresponding CRTs for the includedadd-ons, if necessary.

Introduction

March 2002 13

Modifications

Modifications cannot be recovered during the upgrade. A consistent SAP system withoutmodifications is available to you after the upgrade. You can recover any necessarymodifications by using the modification adjustment (transaction SPAU or SPDD).

This new procedure may cause more objects to be offered in the modification adjustmentthan was previously the case. Customer objects are not affected by this change and areretained as usual.

Naming Conventions for the SAP WebApplication Server UpgradeSAP Basis and SAP Web Application ServerRelease 6.10 renames the SAP Basis Component as the SAP Web Application Server. Thefollowing documentation uses SAP Basis (or the abbreviation Basis) when referring toRelease 4.6D and lower, and SAP Web Application Server (or the abbreviation SAP Web AS)when referring to Release 6.10 and higher.

ReleaseUnless otherwise specified, the term release is used in the product-specific part of thisdocumentation to refer to the release of the SAP R/3 Enterprise System.

In the general part of the documentation, release is used to refer to the release of the Basisor SAP Web Application Server System.

SAP Web Application Server System and SAP SystemIn this documentation, the term SAP system is the same as SAP Web Application ServerSystem. Similarly, SAP is also used as a synonym for SAP Web Application Server in termssuch as SAP start profile or SAP system language.

SAP System IDThe SAP system ID is abbreviated as SAPSID or sapsid in this documentation. The SAPsystem ID is entered in uppercase in the following. If is used, you must write inuppercase letters, for example PRD.

Always enter the user name adm in lowercase for the standalonedatabase server.

ID for the SAP Web Application Server ReleaseIn this documentation, stands for the relevant SAP Web Application Server, without adecimal point, such as 620.

Support Packages and PatchesAs of Basis Release 4.6, SAP uses the term Support Packages instead of SAP patches.There are various types of Support Packages, such as Basis Support Packages or Add-OnSupport Packages.

Introduction

14 March 2002

DB6, DB2 Universal Database for UNIX and Windows and DB2 commonserverIn this documentation and in the upgrade dialogs, DB2 UDB for UNIX and Windows (or theabbreviation DB2 UDB) is used to describe the database DB2 Universal Database for UNIXand Windows, and, in certain cases, the SAP ID DB6 is used as well. In older versions of thisdocumentation, DB2 Universal Database for UNIX and Windows was known as DB2 commonserver (DB2/CS) or DB2 Universal Database for UNIX and Windows.

DB2, DB2 UDB for OS/390 and DB2 Universal DatabaseIn this documentation and in the upgrade dialogs, DB2 UDB for OS/390 is used to describethe database DB2 Universal Database for OS/390, and in certain cases, the SAP ID DB2 isused as well.

Upgrade Step by Step

March 2002 15

Upgrade Step by StepPurpose

If you have a lot of experience in upgrading the SAP system, you will probablyonly need the parts Upgrade Step by Step, Product-Specific Information[Page 31], and SAP Notes [Page 26]. All other sections contain additionalinformation on the upgrade, troubleshooting, and administration tasks.

This section is constructed as a checklist and contains all the actions you need to do thefollowing:

Find SAP Notes [Page 26]

Plan (SAP Web Application Server-specific [Page 32]/general [Page 50])

Prepare (SAP Web Application Server-specific [Page 41]/general [Page 79])

Upgrade the system [Page 121]

Perform post-upgrade activities (SAP Web Application Server-specific [Page 45]/general[Page 144])

for the upgrade. The actions are placed in chronological order, so that you can work throughthem just like a checklist. Use the links to the general descriptions of the actions and to anyadditional product-specific information to help you perform the actions.

The following three sections contain information on how to proceed with errors, upgradeadministration, and on how to use the upgrade tools:





16 March 2002

SAP Notes for the UpgradeThis upgrade documentation is enhanced and updated by SAP Notes in SAPNet R/3Frontend. These SAP Notes are an important source of information when you plan andprepare your upgrade, and also help you perform the actual upgrade.

Action

You request the current SAP Notes for the upgrade [Page 26]. You require at least thefollowing SAP Notes:

General Upgrade Note 484876

The relevant database-specific SAP Note

490095 (DB2 UDB for UNIX and Windows)

490065 (DB2 UDB for OS/390)

486274 (Informix)

490482 (MS SQL Server)

491598 (Oracle)

490325 (SAP DB)

Planning the UpgradeBefore you start the actual upgrade, you must plan it carefully so that downtime is reduced toa minimum, and the upgrade runs as efficiently as possible.

The Planning the Upgrade section contains additional SAP Web Application Server-specific[Page 32] and general [Page 50] information.

Action

You can upgrade the frontend software [Page 52] as soon as you receive the softwarepackage.

You familiarize yourself with the features of the System Switch Upgrade [Page 53] and itseffect on the way you upgrade the system.

You decide on an upgrade strategy, taking into account your operating system anddatabase upgrade (SAP Web Application Server-specific [Page 32] and general [Page55]).

You define an archiving strategy [Page 59] for your database.

Before you start the upgrade, you check the database-specific aspects [Page 60] andinclude them in your upgrade schedule, if necessary.

You check whether your system is an MCOD system [Page 64].

You plan the incremental table conversion [Page 65], if necessary.

You draw up an upgrade schedule (SAP Web Application Server-specific [Page33]/general [Page 67]).


March 2002 17

Depending on your chosen upgrade strategy, you plan the runtime for the import of thesubstitution set (SAP Web Application Server-specific [Page 33]/general [Page 70]).

You decide on the sequence of upgrades in your SAP system group [Page 70].

You plan the modification adjustment [Page 71], if necessary.

You check the structural requirements [Page 73].

You check the hardware requirements (SAP Web Application Server-specific [Page34]/general [Page 74]):

CPU, main memory, and page file see the SAP Service Marketplace underservice.sap.com/quicksizing

Space requirements in the database:

DB2 UDB for UNIX and Windows: Maximum of 9 GB, of this 5 GB permanent

DB2 UDB for OS/390: See SAP Note 490057

Informix: At least 10 GB, of this 6.5 GB permanent

MS SQL Server: 8 GB

The option Automatically grow file is set for the SAP database during theupgrade. This makes the database adjust its size to the requirements of theupgrade.

Oracle: 9 GB, of this 5.5 GB permanently

SAP DB: Maximum of 7 GB, of this 6.4 GB permanently

You check the software requirements [Page 74].

Source release of the SAP system (SAP Web Application Server-specific [Page35]/general [Page 75]):

SAP Basis 4.6D

SAP Web AS Release 6.10

Upgrade Assistant [Page 75]: Java Virtual Machine (at least Version 1.1x, Version 1.3is recommended)


18 March 2002

You upgrade the operating system and database system, if necessary (SAP WebApplication Server-specific [Page 35] and general [Page 76]).

Operating system version

The SAP Web Application Server 6.20 is supported under Windows 2000 with thecurrent Service Pack and under Windows XP for 64 bit.

For the operating system requirements, see the SAP Service Marketplace underservice.sap.com/platforms.

Database version:

DB2 UDB for UNIX and Windows

At least Version 7, FixPak 4b; migrate before PREPARE

DB2 for OS/390

Version 6.1.0; migrate before PREPARE

Informix

See SAP Note 486274; migrate after PREPARE and repeat the GeneralChecks module.

MS SQL Server

Version 2000; migrate before PREPARE

Oracle

At least Version 8.10.7; migrate before PREPARE

SAP DB

At least Version 7.3.0.20Prerequisites for PREPARE: at least Version 7.2.05.012 and newestversion of DB client softwareMigrate before PREPARE

You meet the requirements for installing the online documentation [Page 76] as describedin the documentation Installing the SAP Library.

You meet the requirements for the SAP Internet Transaction Server and the SAP@WebStudio [Page 77] according to the SAP@Web Installation Guide, if necessary.

If necessary, meet the prerequisites for importing additional languages [Page 78]

Upgrade PreparationsYou can prepare for the upgrade while the system is operating productively.The PREPARE program supports you here by making most of the necessary checksautomatically. Start PREPARE as soon as possible before the upgrade so that you can initiateor perform the necessary preparations in time.

The Preparing the Upgrade section contains additional SAP Web Application Server-specific[Page 41] and general [Page 79] information.


March 2002 19

Preparations for PREPARE

Action

You choose the host [Page 81] for PREPARE and the Upgrade Assistant.

You make preparations for reading the upgrade CDs [Page 81].

You create an empty upgrade directory on the host with the central instance (SAP WebApplication Server-specific [Page 41] and general [Page 82]):

With a total of 1,080 MB free disk space

Include 20% extra space on the database if you have made a lot of your owndevelopments. Also do this if you want to include Support Packages and add-ons.

If you want to import languages other than English and German, provide an extra 75MB of memory for each language.

You check the database-specific prerequisites for PREPARE (SAP Web ApplicationServer-specific [Page 42]/general [Page 83]). The following free space must be available:

DB2 UDB for UNIX and Windows/DB2 UDB for OS/390/MS SQL Server/Oracle: 500MB

Informix: At least 200 MB

SAP DB: 160 MB (corresponds to 20,000 pages)

You import the latest SPAM update [Page 84].

You check the version of individual SAP programs [Page 85].

Actions for Starting PREPARE

Action

When you start PREPARE for the first time, you must start it from the CD [Page 90].

1. You insert the SAP Kernel CD.

2. You log on to the host with the central instance as user ADM.

3. In the Windows NT Explorer, change to subdirectory \NT\I386\ (Windows XP for 64bit: \NT\IA64) on the CD drive and start PREPARE.EXE.

4. You exit PREPARE with EXIT.

5. You start the Upgrade Assistant server [Page 91].

6. You start the GUI of the Upgrade Assistant [Page 91].

7. You start the Upgrade Assistant [Page 92].

If you want to restart PREPARE [Page 94], for example, if the results from its first run makeyou want to repeat some checks, enter the command PREPARE.EXE REPEAT.You can reset PREPARE [Page 94] at any time, for example, if you want to use it foranother system.If you need extra software after starting PREPARE, you import it now [Page 95].

PREPARE needs certain information from you so that it can run the modules. If possible,default values appear that you can confirm or change. For a complete list of all PREPAREmodules and phases, see PREPARE Phase List [Page 221].


20 March 2002

User Actions During PREPARE

Action

You make the entries for the Parameter Input module (SAP Web Application Server-specific[Page 44]/general [Page 96]). This includes entering CD mount directories.You need the following CDs for PREPARE:CD SAP Kernel, Upgrade CD 1, language CD(s), any add-on CDs

You make entries for the initialization module [Page 100].DB2 UDB for OS/390: Among other things, create or extend stogroups if necessary.

Make entries for the import module [Page 101].

You make entries for the extension module [Page 101], such as including SupportPackages.

Make entries for the installation module [Page 107].SAP DB: If necessary, you change the database parameters MAXUSERTASKS andMAXLOCKS.

Microsoft Cluster Server (MSCS)You make the entries for the MSCS Configuration [Page 109].

End of Microsoft Cluster Server (MSCS)

Manual Checks

Action

You evaluate the results of PREPARE [Page 109] in the log file CHECKS.LOG.

You make sure that the page file [Page 206] is large enough.

You make preparations at the operating system level [Page 114]:

You make a backup copy of the old SAP Kernel.

You make preparations at the database level [Page 114].

You make sure that you can recover the database to the state it had before theupgrade.

You make the database-specific preparations.

You make preparations at the SAP system level [Page 116].

You delete the AUTOSTART parameter [Page 117].

You make sure that the user DDIC [Page 117] can log on to client 000.

You make sure that the requirements for the modification adjustment [Page 117] havebeen met.

You use transaction RZ04 to set the operation mode [Page 118] for the upgrade.

You import the new front-end software [Page 52], if necessary.


March 2002 21

The UpgradeThe part of the documentation on actually upgrading the system [Page 121] containsadditional information.

Action

You check the General Upgrade Note and your database-specific SAP Note for newinformation and changes [Page 26].

You choose the host for the upgrade [Page 81].

You get the following CDs ready [Page 44]:CD SAP Kernel, Upgrade CDs 1-2, any language CDs

You start R3up [Page 123] from the host with the central instance.You can stop [Page 124] and restart [Page 124] the upgrade if errors occur.

Phase INITPUT [Page 130]:

You enter the system-specific parameters.

Phase PATCH_CHK [Page 130]:

You confirm any unconfirmed Support Packages.

Phase KEY_CHK [Page 131]:

You enter the key word from the current Upgrade Note 484876.

Phase INITSUBST [Page 131]:

You choose your upgrade strategy. If you choose downtime-minimized, you determinethe runtime for the import of the substitution set (around 10 hours).

If you choose resource minimized, you determine the number of parallel processes forimporting the substitution set.

You determine the number of parallel background processes.

DB2 UDB for OS/390: You enter the number of parallel tp processes in thePARCONV_UPG phase, and define any indexes.

Phase CONFCHK_X [Page 133]:

Now, at the latest, you upgrade your operating system or database to the required version.You import the required software.

Phase REPACHK1 [Page 133]:

You release the locked objects and confirm repairs. You must do this in the REPACHK2phase at the latest.

Phase JOB_RSVBCHK2 [Page 134]:

You clean up outstanding updates. You must do this in the JOB_RSVBCHK3 phase at thelatest.

Phase FREECHK_X [Page 134]:

Free space check in the log subdirectory and the Kernel directory. You make sure that youcan recover the old Kernel if this becomes necessary.


22 March 2002

Phase LOCKEU_PRE [Page 135]:

For downtime minimized: You lock the ABAP Workbench. You must do this in theREPACHK2 phase at the latest.

Phase EU_IMPORT1 [Page 136]:

For resource-minimized: You isolate the central instance, stop the application server andchange the database recovery mode, if necessary.

Phases EU_IMPORT4 and EU_IMPORT5 [Page 136]:

If the CD is not in one of the specified mount directories, you are prompted to change theCD.

Phase REPACHK2 [Page 137]:

You release and confirm all open repairs in this phase at the latest.

For downtime-minimized: You lock the ABAP Workbench in this phase at the latest.

Phase CNV_CHK_XT [Page 138]:

You process any uncompleted conversion requests and restart logs.

Phase ADJUSTCHK [Page 138]:Modifications: You confirm the request, if necessary.

Phase START_SHDI_FIRST:

As of this phase you can only log on with the new frontend software [Page 52].

Phase ACT_: [Page 138]

Modifications: You adjust modified SAP objects with the SAP standard versions.

Phase VIEWCHK2 [Page 140]:

You remove conflicts between customer tables and new views by deleting the customertables in this phase at the latest.

Phase MODPROF_TRANS [Page 140]:

For downtime-minimized: You isolate the central instance, stop the application serverand change the database recovery mode, if necessary. Also make sure that you canrecover the database to its current state.

You back up the upgrade directory.

You check the percentage of tables converted in transaction ICNV, if necessary.

Phases JOB_RSVBCHK3 and JOBS_RSVBCHK4 [Page 141]:

You clean up outstanding updates in this phase at the latest.

Phase MODPROFP_UPG [Page 142]:

In the phases MODPROFP_UPG, STARTR3_PUPG, and CHK_POSTUP

You back up the database.

You determine P errors

You change the database recovery mode

You start the secondary application servers.


March 2002 23

Phase CHK_POSTUP [Page 143]:

Remove the P errors before you restart production operation of the system.

Post-Upgrade ActivitiesThe Post-Upgrade Activities section contains additional SAP Web Application Server-specific[Page 45] and general [Page 144] information.R3up stops at the latest in the MODPROFP_UPG phase and prompts you to start the post-upgrade activities. R3up then executes the last phases and completes the upgrade. At thesame time you can perform the post-upgrade activities specified by R3up.

Activities Before Starting Production Operation

Action

You perform the database-specific actions:

DB2 UDB for UNIX and Windows (SAP Web Application Server-specific [Page45]/general [Page 146]): You install or update the DB2 administration tools, switch onlog archiving, back up the database, delete substitution tablespaces, update statistics,and schedule update statistics jobs.

DB2 UDB for OS/390 [Page 146]: You back up and reorganize the database, schedulean update statistics job, and tune new tables.

Informix [Page 147]: You delete the empty dbspaces for the substitution tables and backup the database.

MS SQL Server [Page 148]: You back up the database. Start the SQL Server Agent, if itis not running.

Oracle [Page 148]:You check the environment variables for SAPDBA and back up the database.

SAP DB [Page 150]:You set the database parameters to their pre-upgrade state and restore the ability of thedatabase to be recovered.

Microsoft Cluster Server (MSCS)You perform the post-upgrade activities [Page 150]. See SAP Note 144031.End of Microsoft Cluster Server (MSCS)

If there is no central software storage point: You distribute the SAP programs [Page 151].

You upgrade the application servers [Page 151].

You use transaction RZ10 to check the profile parameters [Page 153] and reset them totheir default values, if necessary.

You install the SAP J2EE Engine [Page 154]. This action is not optional.

You reimport additional programs [Page 154] such as RFC-SDK or CPIC-SDK from thePresentation CD, if necessary.

You use transaction SPAU to adjust modifications to Repository objects [Page 155], ifnecessary.


24 March 2002

You perform application-specific [Page 155] post-upgrade activities.

Configure Single Sign-On with the NT LAN Manager SSP [Page 157], if necessary.

You can perform the following post-upgrade activities during limited production operation[Page 144] of the system.

Actions After Restarting Limited Production Operation

Action

You reschedule background jobs [Page 162] whose release you reset when you isolated thecentral instance.

You perform database-specific actions:

Informix [Page 164]: You update statistics.

Oracle: You perform actions for the Cost-Based Optimizer [Page 165].

SAP DB [Page 167]: You update the optimizer statistics.

You use transaction SGEN to generate ABAP loads [Page 167].

If necessary, you generate the BSP applications [Page 168] with transaction SGEN.

You perform actions for the online documentation [Page 168] according to the documentationInstalling the SAP Library.

You install the SAP Internet Transaction Server [Page 77] and the SAP@Web Studioaccording to the documentation SAP@Web Installation, if necessary.

You perform post-upgrade authorization activities [Page 169].

You adjust the assignments between check flags and transactions.

Upward compatibility for authorization checks: You adjust SAP_NEW.

You handle problems with user buffers.

Use SAPinst to install more dialog instances [Page 172], if necessary.

You can perform the following post-upgrade activities during normal production operation ofthe system.

Actions After Starting Production Operation

Action

You import Support Packages [Page 172], if necessary.

If you want to install additional languages, you import them before you import the SupportPackages as described in the Language Transport documentation.

Transport Management System (TMS) [Page 173]: You distribute the configuration to allsystems in the transport domain.

Language transport [Page 173]: You copy glossary and terminology data from containertables to database tables.


March 2002 25

You perform database-specific actions:

DB2 UDB for OS/390 [Page 174]: You remove database objects that you no longerneed.

Oracle: You delete old tablespaces [Page 174].

You convert old batch input logs [Page 175] to the new procedure in all clients, if necessary.

There are some post-upgrade activities that you do not need to perform directly after theupgrade. You can leave these activities until later.

Evaluating the Upgrade Runtime

Action

Use the report RSUPGSUM to evaluate the runtime of the upgrade [Page 175] and send thelist to SAP with your SAPNet - R/3 Frontend connection.

SAP Notes for the SAP Web Application Server Upgrade

26 March 2002

SAP Notes for the SAP Web ApplicationServer UpgradeDefinitionTo prepare and perform the upgrade of your system, you require some additional information,not included in the documentation. This information is in a range of SAP Notes in SAPNet R/3 Frontend. You must read the general Upgrade Note before you prepare the upgrade.This SAP Note also contains current cross-database information on preparing the upgrade.There are separate SAP Notes for the database-specific sections. When you actuallyupgrade the system you need information from some additional SAP Notes. These SAPNotes are named at the appropriate places in this documentation.

SAP Notes for Preparing the UpgradeYou must request the SAP Note for the upgrade (general) and the SAP Note for yourdatabase from SAPNet - R/3 Frontend before you start your upgrade. Since these SAP Notesare updated regularly, make sure you always use the newest version. The following is a list ofthe SAP Notes you need to prepare for the upgrade:

SAP NoteNumber

Topic SAP Note Type

484876 All databases Specific to this upgrade

490095 DB2 UDB for UNIX andWindows

DB2 UDB for UNIX and Windows-specific/specific to this upgrade

490065 DB2 UDB for OS/390 DB2-UDB-for-OS/390-specific / specific tothis upgrade

486247 Informix Informix-specific / specific to this upgrade

490482 MS SQL Server MS SQL Server-specific / specific to thisupgrade

491598 Oracle Oracle-specific / specific to this upgrade

490325 SAP DB SAP DB-specific / specific to this upgrade

Keyword for the UpgradeWhen you start the upgrade, you are asked to enter a keyword, which you can get from thecurrent general Upgrade Note 484876. You cannot start the upgrade until you have enteredthe keyword.


March 2002 27

Other SAP NotesAs well as the SAP Notes you need for preparing the upgrade, this documentation also refersyou to other SAP Notes, which give you additional information, if necessary. The following isa list of these SAP Notes, organized by database:

SAP Notes for All Databases

SAP NoteNumber

Topic SAP Note Type

26417 SAP GUI resources: Hardware andSoftware

Frontend/SAP GUI

86985 Release SAP Releases for SAP add-ons(IS)

IS-specific

76431 Measures for optimizing upgrade runtime4.x

Upgrade to Release 4.x

83458 Downloading Support Packages from theSAP Service Marketplace

SAP Support Packages

125971 Service connection in Upgrade Assistant inSAPNet - R/3 Frontend

Remote support for upgrade

33888 Central Basis objects are modified General upgrade

62519 Correction locks do not belong to system Transport Organizer

51046 Copying the modification adjustmentwithout a central transport directory

Change and TransportSystem

96905 Error message TG063 in theJOB_RADDRCHK phase

ABAP Dictionary

144031 Supplement to Upgrade MSCS R/3upgrade to cluster

Windows NT Cluster

97032 Conversion of address tables, runtime Address management

82167 Conversion of address tables, runtime Address management

24864 No conversion of table BSEG ABAP Dictionary/phasePARCONV_UPG

10187 User buffer too small User administration

143124 Installing a dialog instance R/3 installation

197746 Maintenance Strategy Internet TransactionServer (ITS)

SAP@Web

399578 Publishing IAC objects on the ITS after theupgrade

SAP@Web

86627 Transaction types: Customizing for releaseupgrades

Customizing

98752 Migrating the proposal pool Translation tools

482462 Current Note on the 6.20 language import Language transport

352941 Language import and Support Packages Language transport

322982 Install language during upgrade Language transport


28 March 2002

485741 Dealing with customer translations in theupgrade

Language transport

73999 Upgrade phase PARDIST_SHD: TG450 toTG453

General upgrade

177680 Correcting conversion problems in thePARCONV_UPG phase

General upgrade

40024 Transferring Customer Files to sapservUsing ftp

General upgrade

417670 Additional Information About Resetting theUpgrade

General upgrade

186066 Increased freespace requirements duringthe upgrade

General upgrade

493387 Potential effects of changes totables/structures

Activation

490788 ICNV in the upgrade to SAP Web AS 6.20 ICNV

48550 CD problems in the phases PREPARE andLANG_REQ

General upgrade

94998 Requesting a license key for a system General upgrade

SAP Notes for DB2 UDB for UNIX and Windows

SAP NoteNumber

Topic SAP Note Type

407322 Released operating systems for SAPKernel 6.x DB2 UDB

DB2 UDB for UNIX andWindows-specific

SAP Notes for DB2 UDB for OS/390

SAP NoteNumber

Topic SAP Note Type

81737 DB2/390: APAR list DB2 UDB for OS/390-specific

183311 DB2/390: Automatic PTF Check DB2 UDB for OS/390-specific

113008 Maintaining catalog statistics DB2 UDB for OS/390-specific

136806 DB2/390: Upgrade, ICLI servers DB2 UDB for OS/390-specific

103135 DB2/390: Manual saposcol installation DB2 UDB for OS/390-specific

122599 DB2/390: Performance of the update DB2 UDB for OS/390-specific


March 2002 29

434946 DB2/390: R3szchk & R3ldclt for upgrade to>= 6.10

DB2 UDB for OS/390-specific

184399 DB2/390: DDIC corrections (4.6A, 4.6B,4.6C, 4.6D)


407663 DB2/390: DDIC corrections (6.10, 6.20) DB2 UDB for OS/390-specific

490057 DB2/390: Upgrade to Web AS 6.20 freespace


400565 DB2/390 upgrade: Optional checks DB2 UDB for OS/390-specific

493577 DB2/390: Transports for 6.20 DB2 UDB for OS/390-specific

407325 Released operating systems for SAPKernel 6.x DB2/390


SAP Notes for Informix

SAP NoteNumber

Topic SAP Note Type

50157 Using recommended versions of Informix Informix-specific

407317 Released operating systems for SAPKernel 6x Informix

Informix-specific

22941 Reorganization of tables and dbspaces Informix-specific

115619 Informix Client versions Informix-specific

SAP Notes for MS SQL Server

SAP NoteNumber

Topic SAP Note Type

407328 SAP Kernel 6.x MS SQL Server: Releasedoperating systems

MS SQL Server-specific

154686 Long data type conversion MS SQL Server-specific

62988 Service Packs for MS SQL Server MS SQL Server-specific

209596 Microsoft SQL Server 2000 For database release MSSQL Server 2000

327494 Configuration parameters for MS SQLServer 2000

For database release MSSQL Server 2000


30 March 2002

SAP Notes for Oracle

SAP NoteNumber

Topic SAP Note Type

407314 Released operating systems for SAPKernel 6.x Oracle

Oracle-specific

11777 Changing the storage parameters NEXTand MAX EXTENTS

Oracle-specific

16951 Oracle - Problems with Rollback segments Oracle-specific

94801 Environment variables for Windows NT Oracle-specific

SAP Notes for SAP DB

SAP NoteNumber

Topic SAP Note Type

407320 Released operating systems for SAPKernel 6.x SAP DB

SAP DB-specific

458553 SAP DB upgrade to 7.3.0 B20 SAP DB-specific

34690 Add Devspace under SAP DB (ADABASfor R/3)

SAP DB-specific

46430 SAP DB load with parallel R3LOADS SAP DB-specific

201388 Change a database parameter in SAP DBRelease

SAP DB-specific

201390 Back up the database SAP DB SAP DB-specific

352081 Additional functions relevant to services forSAP DB

SAP DB-specific

362542 Analysis of table sizes and growth SAP DB-specific

Optional SAP Notes for Windows

SAP NoteNumber

Topic SAP Note Type

169468 Windows 2000 support Windows 2000-specific

28781 Central transport directory NT/UNIX Mixed systems

65761 Configuration problems under Windows NT System configuration

430992 Shadow instance on another host:Windows

Upgrade under Windows

33772 Configuring Dr. Watson Correctly System administration

Product-Specific Information for the SAP Web AS Upgrade

March 2002 31

Product-Specific Information for theSAP Web AS UpgradeThis part of the documentation describes the information and restrictions specific to anupgrade of the SAP Web Application Server system.

Among other things, this includes SAP Web Application Server system upgrade-specificdirectory sizes, database and operating system versions, as well as restrictions on andadditions to the general upgrade procedure.

The information in the product-specific sections takes priority over theinformation in the general sections of the documentation.

This part of the documentation has a similar structure to the General UpgradeInformation [Page 49]. The same section headings contain comments,additional information or restrictions on the upgrade. Each product-specifictext contains a link to the description of the procedure in the general part ofthe documentation.

The following parts of the documentation contain additional information:

Planning the SAP Web Application Server Upgrade [Page 32]

Preparing the SAP Web Application Server Upgrade [Page 41]

SAP Web Application Server Upgrade: Post-Upgrade Activities [Page 45]


32 March 2002

Planning the SAP Web Application ServerUpgradeThis part of the documentation gives you SAP Web Application Server-specific information onplanning the upgrade of your system. The following sections include additional information, orrestrictions placed on the general procedures:

Planning the Upgrade Strategy [Page 32]

Upgrade Schedule Planning [Page 33]

Runtime for the Import of the Substitution Set [Page 33]

Checking Hardware Requirements [Page 34]

Checking the Source Release of the SAP System [Page 35]

Upgrading the Operating System and Database System: Overview [Page 35]

Start planning your upgrade at least two to three weeks before you want tostart.

See alsoPlanning the Upgrade (General Information) [Page 50]

Planning the Upgrade StrategyThe downtime depends on the selected upgrade strategy and the amount of time required tocreate the database archives.

The following table shows the sizes of the archives created for the different upgradestrategies, archiving strategies, and databases. These sizes are based on sample data.

The archives can be made larger by importing additional languages, or a large amount ofSupport Packages or add-ons.

Comparison of the Archives in GB

Up tophase

MODPROF_TRANS

Up to the end of theupgrade

DB2 UDB for UNIX and Windows 5,0 7,0

Informix 6,0 8,0

MS SQL Server 6,0 8,0

Oracle 7,0 9,0

SAP DB 5,0 7,0

See also:Planning the Upgrade Strategy (General Information) [Page 55]


March 2002 33

Upgrade Schedule PlanningRemember the following points when you draw up a schedule for your upgrade:

Upgrade preparations (see step 1 in the general description [Page 67])

Start your preparations for the upgrade [Page 79] at the latest one week before youupgrade your system.

Starting the upgrade (see step 2 in the general description [Page 67])

If you decide to use upgrade strategy resource-minimized, start the upgrade on the lastday of production operation with the old release. If you decide to use the upgradestrategy downtime-minimized, start the upgrade on the next to last day of productionoperation with the old release.

At the start of the phases EU_IMPORT1, EU_IMPORT4 and EU_IMPORT5, youare prompted to change the CD. The runtime of the EU_IMPORT4 phase isapproximately 30 minutes, and the runtime of the EU_IMPORT5 phase isapproximately 1.5 hours. If you miss this prompt, your time schedule could beseriously disrupted.

The minimum runtime of the import in the SHADOW_IMPORT_ALL phase increases withevery Support Package, add-on, and language that is included. Each language that youimport increases the minimum duration of the import by about 30 minutes.

See also:Drawing Up an Upgrade Schedule (General Information) [Page 67]

Runtime for the Import of the Substitution SetThe import of the substitution set takes about 2 hours, depending on your hardware.

The downtime-minimized upgrade strategy prompts you to specify a total runtime for theimport of the substitution set. Set the time required for the import so that it ends at least 5hours before the planned shutdown of production operation. Depending on the start time ofthe upgrade, specify total runtimes of about 10 hours.

See also:Importing the Substitution Set (General Information) [Page 70]


34 March 2002

Checking Hardware RequirementsChecking CPU, Main Memory, and Page FilesExact information about sizing the SAP Web Application Server does not exist at themoment. For information about the minimum prerequisites, see the SAP Notes aboutdatabase and operating systems in the SAP Service Marketplace at the following address:service.sap.com/platforms.

Space Requirements in the File SystemMake sure that you have about 1,080 MB of temporary disk space in the file system for theupgrade. You need this free space to create the upgrade directory.

Space Requirements in the DatabaseDuring the upgrade, you require the following amount of disk space for the database.

DB2 UDB for UNIX and WindowsThe database is extended by a maximum of 7 GB. 5 GB are occupied permanently. You canfree space after the upgrade by deleting the substitution tablespaces of the source release.

DB2 UDB for OS/390SAP Note 490057 describes the free space requirements in the database.InformixThe database is extended by at least 10 GB. Approximately 6.5 GB of this amount is filledpermanently. The space requirements could be higher, depending on how much data youhave.

You can recover the difference between the maximum disk space requirements and thepermanent disk space requirements by deleting the old substitution dbspaces.

MS SQL ServerThe database requires 8 GB of free disk space for the upgrade.During MS SQL Server 2000 runtime, the option Automatically grow file is set. This makesthe database adjust its size to the requirements during the upgrade if enough disk space isavailable.

OracleYou require a maximum of 9 GB of space in the database for the upgrade. Approximately 6.5GB of this amount is filled permanently. The space requirements could be higher, dependingon how much data you have.

Make sure that there is enough free space in the database.

You can recover the difference between the minimum disk space requirements and thepermanent disk space requirements by deleting the old substitution tablespaces.


March 2002 35

SAP DBYou require a maximum of 7 GB of space in the database for the upgrade. Approximately 6.4GB of this amount is filled permanently. The space requirements could be higher, dependingon how much data you have.

The difference between the maximum disk space requirements and the permanent diskspace requirements is available as free space in the database as soon as the upgrade iscomplete.

End of the database-specific explanations

The PREPARE program also gives you information on how much free space is needed in thedatabase.

See also:Checking Hardware Requirements (General Information) [Page 74]

Checking the Source Release of the SAP SystemBefore the upgrade, your SAP system must have one of the following source releases, whichhave been released for this upgrade and which depend on your database:

Release 4.6D of SAP Basis

Release 6.10 of the SAP Web Application Server

See also:Checking the Source Release of the SAP System (General Information) [Page 75]

Upgrading the Operating System and DatabaseSystem: OverviewPurposeA requirement for the SAP Web Application Server 6.20 is that the operating system isWindows 2000 with the current Service Pack, or Windows XP for 64 bit.

When you upgrade an SAP system, you may have to update your operating system anddatabase to a new version.

For the latest information on which combinations of operating systems and databases aresupported, see the SAP Service Marketplace: service.sap.com/platforms.

If you need to upgrade an operating system or database, or migrate a database, then thetiming and the sequence of the individual upgrades is of great importance. The procedurediffers according to the database you use. We have described the process flows specificallyfor each database in this section.


36 March 2002

Process FlowThe upgrade is performed in separate steps.

MSCS ClusterIn an MSCS cluster configuration, all the steps, except the SAP upgrade andKernel upgrade, need to be performed on each node of the cluster.

1. Operating system upgrade

2. Database migration or database upgrade3. PREPARE

4. SAP upgrade

You must also perform different steps to prepare for running the PREPARE program or theupgrade. For more information, see Preparing the Upgrade (SAP Web Application Server-specific [Page 41]/general [Page 79]).

DB2 UDB for UNIX and WindowsProceed as follows:

1. Migrate the database to at least Version 7, Fixpak 4b if you have not already done so.

The migration guide is a PDF document on the software CD that contains Version 7 ofthe database.

2. Start PREPARE and analyze the results.

3. Upgrade the system with your choice of upgrade strategy. Both strategies (downtime-minimized and resource-minimized) are supported.

DB2 UDB for OS/390

Make sure that you meet the following requirements before you start PREPARE for the firsttime:

1. Database: DB2 Version 6.1.0.

2. Operating system: z/OS Version 1.2 or higher

3. PTFs and APARs for operating system and database

SAP Note 81737 (APAR list) contains information on the PTFs that you need to importbefore the upgrade. A PTF Check Tool is available for all source releases. This tool isdescribed in SAP Note 183311. Any missing PTFs can lengthen the runtime of theupgrade significantly.

4. ICLI

The first time you start PREPARE, a 6.20 ICLI server is started for the upgrade toolsalongside the ICLI server of the source release.

The ICLI software is delivered using PTF. You must install this before you startPREPARE for the first time.


March 2002 37

The ICLI software must be in the following data sets after you have installed the PTFs:

.SFOMDATA.SAMPLIB.LINKLIB

is identical for all three data sets and its default value is SYS1.

For more information, see SAP Notes 81737 and 136806, and the IBM documentationSAP Web Application Server 6.20 on IBM eServer zSeries: Planning Guide.

5. RACF or other security products

During the upgrade, a shadow system is created with its own schema name. This nameconsists of the schema name of the outbound system, and has an "S" appended to it(SAPR3 becomes SAPR3S or SAPPRO becomes SAPPROS, for example). If you useRACF, you therefore have to do the following for this additional schema:

Define a secondary authorization ID

Create an RACF group with the same name

Enter the user IDs that communicate with the database (ADM or ICLIRUN)as members of this RACF group

For more information about the general procedure, see the SAP Web ApplicationServer 6.20 on IBM eServer zSeries: Planning Guide.

If you use a different security product, perform the relevant steps according to the productdocumentation.

6. Current downward-compatible SAP Kernel and required transports for source release

Make sure that all required transports and the minimum required patch level of thecurrent downward-compatible SAP Kernel for the source release have been imported intoyour system. The import of the current downward-compatible SAP Kernel is described inSAP Note 102445. Depending on your source release, the transports, the release andthe minimum required patch level of the kernel are described in one of the following SAPNotes:

Source Release SAP Note Number

4.6D 184399

6.10, 6.20 407663

For Source Release 4.6D, you require the latest versions of the executables R3ldctland R3szchk. Copy them into the \usr\sap\\SYS\exe\run directory.

7. Indexes in SYSIBM.SYSTABLES and SYSIBM.SYSTABLESPACE

The indexes that were created in the catalog tables SYSIBM.SYSTABLES andSYSIBM.SYSTABLESPACE have to be checked and increased, if necessary. Theindexes have the following names:

SYSTABLE~0 or SYSTABLE__0

SYSTBLSP~0 or SYSTBLSP__0

8. Gigabit Ethernet

If you use Gigabit Ethernet, the performance level of the upgrade is increased by 40% incomparison to other network protocols (Fast Ethernet, for example).


38 March 2002

9. DB2 Performance Monitor (DB2 PM)

Since the DB2 PM is not required by the upgrade or the target production system, theDB2 PM-supported transaction ST04 of the upgrade phase KX_SWITCH can no longer beused. Alternatively, you can use transaction SE38 to call the RSDB3001_OLD report.

10. Stored Procedures

As of Release 4.6B, stored procedures are used for DB2 UDN for OS/390, StoProcs(DSNUTILS) are used for DB2 Utilities, and StoProcs for the DB2/390 Control Center.The prerequisites and preparations are described in the SAP Web Application Server6.20 on IBM eServer zSeries: Planning Guide.

InformixTo find out which version of the Informix Dynamic Server you must import for this release,see SAP Note 486274, or SAP Note 50157: Using Recommended Informix Versions.Proceed as follows:


2. If you have not done so, upgrade Informix as described in the guide Installing Version9.30 of the Informix Dynamic Servers: Windows.

3. Repeat the module General Checks to run through the CONFCHK phase oncemore and if the module ran successfully, exit it.


MS SQL Server

1. Make sure that you meet the following requirements before you start PREPARE for thefirst time:

a. The required database version MS SQL Server 2000 is installed.

SAP Note 209596 describes the upgrade from MS SQL Server 7.0 to MS SQLServer 2000. Also read the supplementary SAP Note 139945.If the source release of your system is released for MS SQL Server 7.0 only, thenyou must upgrade your database to MS SQL Server 2000 before the SAP upgrade.For more information, see SAP Note 399341.SAP Note 417089 describes the procedure for installing the service packs on MSSQL Server 2000.

Make sure that you have installed all the required service packs for MS SQLServer. For a list of the MS SQL Server service packs required by SAP, seeSAP Note 62988.

b. The startup parameter p must not be set (standard MS SQL 2000 works with amaximum precision of 38 characters).




March 2002 39

OracleFor SAP Web Application Server 6.20 you need Oracle Version 8.1.7, which has to beimported before PREPARE runs. Production operation of the system is supported in the firsthalf of the upgrade.

1. Meet the requirements for starting PREPARE.

Operating system: Windows 2000

Database: Oracle Version 8.1.7 or higher

2. Migrate your Oracle database.

You can migrate directly to Oracle Version 8.1.7 from Oracle Version 8.1.6. Migrate thedatabase as described in the guide Upgrade to Oracle8i Release 8.1.7.



Use of the Oracle DBMS is included in the price of the SAP System. Thefollowing Oracle options are available at an extra charge:

Advanced Replication Distributed Parallel Query

If you want to install one of these options, you must contact DevelopmentSupport for database development at SAP before the Oracle migration. Youcan either call SAP Support or enter a message in SAPNet R/3 Frontend.You cannot install the above options directly.

SAP DBYou require at least Version 7.3.0.020 for SAP Web Application Server 6.20 on SAP DB.

For PREPARE you require the following:

At least SAP DB version 7.2.05.012

Newest version of DB client software on the application servers For information about theprocedure, see SAP Note 458553 Upgrading to SAP DB 7.3.0.B20.

Proceed as follows:

1. If the minimum prerequisites for PREPARE have not been met, upgrade the SAP DB asdescribed in SAP Note 458553.


3. If necessary, upgrade the operating system to Windows 2000.

Then repeat the PREPARE module General checks to run through the CONFCHK phaseonce more and if the module ran successfully, exit it.


40 March 2002

4. If the minimum prerequisites for the SAP DB version for the upgrade have not been met,upgrade the SAP DB as described in SAP Note 458553.


End of the database-specific explanationsSee also:Upgrading the Operating System and Database System: Overview (General Information)[Page 76]


March 2002 41

Preparing the SAP Web Application ServerUpgradeThis part of the documentation gives you SAP Web Application Server-specific information onpreparing your upgrade. The following sections include additional information, or restrictionsplaced on the general procedures:

Creating the Upgrade Directory [Page 41]

Checking Database-Specific Requirements for PREPARE [Page 42]

Making Entries for the Parameter Input Module [Page 44]

See also:Upgrade Preparations: General Information [Page 79]

Creating the Upgrade DirectoryNote the following when you create the upgrade directory:

The disk space required by the upgrade directory is distributed among severalsubdirectories. The following table shows the sizes of these subdirectories. The sizesmay vary by up to 25%, depending on your database and source release.

Disk Space Requirements in the Subdirectories of the Upgrade Directory

data exe log Remaining Total

200 MB 300 MB 250 MB 100 MB 230 MB 1080 MB

You also require an additional 75 MB in the upgrade directory for each language otherthan English or German.

See also:Creating the Upgrade Directory (General Information) [Page 82]


42 March 2002

Checking Database-Specific Requirements forPREPAREYou must meet the following database-specific requirements before you start PREPARE forthe first time.

DB2 UDB for OS/390, DB2 UDB for UNIX and Windows, MS SQL Server, Oracle

There must be 500 MB of free space for PREPARE in the database. The spacerequirements for each tablespace are returned by PREPARE.

Informix

Make sure that you have at least 200 MB of free space available in the temporarydbspaces (such as TMPDBS1).

You can start PREPARE before and after upgrading the database version, except in a veryfew situations. These situations are described in SAP Note 486274.

MS SQL Server

Check the login of the user ADM.

This security procedure was introduced with Release 4.5A. In this procedure, the SAPexecutable logs on to the SQL Server database under the Windows user under which it iscalled. Therefore it is necessary that the MS SQL Server contains a login for eachWindows user under which SAP processes are started. These are usually the usersadm and SapService.

During the upgrade, the SAP tools use the Windows user ADM to log on to thedatabase. This means that you must make sure before the upgrade that a login exists forthe user ADM in the database and that it has the required settings.

Check the login in the SQL Enterprise Manager as follows:

1. Start the SQL Server Enterprise Manager.

2. In the Console Root tree, choose:

Microsoft SQL Servers SQL Server Group Security

3. Choose Logins.

The right side of the window displays the available logins. The login for the userADM must exist here. Check that the database is the defaultdatabase for this login and that System Administrators is set as the server role.If you are upgrading an MCOD system, make sure that the default database namecorresponds to the rsdb/dbid parameter. If necessary, correct the settings andconfirm your changes with OK.


March 2002 43

If there is no login for the user ADM, you have to create one:

a) From the menu, choose Action New Login.

The window SQL Server Login Properties - New Login appears.

b) On the General tab:

Enter the name of the login: ADM.

For authentication, choose Windows NT. Enter theaccompanying domain and choose Grant Access.

Under Defaults, specify the database as the defaultdatabase.If you are upgrading an MCOD system, the name of thedatabase in your system may not be . For the correctname, see the rsdb/dbid parameter in the instance profile.

c) On the Server Roles tab, choose the server role System Administrators.

d) Confirm your selection with OK.

Check the environment variables.

Check whether the environment variable MSSQL_DBNAME is set correctly. To do so,execute the following command:

set MSSQL_DBNAME

The variable must contain the database name of your system. If necessary, set thevariable with the command set MSSQL_DBNAME=database name (in upper case) inthe command prompt by starting PREPARE.

If you are upgrading an MCOD system, you must also check the environment variableMSSQL_SCHEMA and set it accordingly. This variable must contain the system ID in lowercase.

If the variables MSSQL_DBNAME and MSSQL_SCHEMA contain incorrect values, oreven no values at all, this causes errors during the upgrade.

SAP DB

PREPARE requires 160 MB of free space in the database. This corresponds to 20000 pages.

Standalone Database Server on UNIX Platforms

Before the upgrade, the password for the database user sapr3 must be reset to sap,otherwise the link to the databas

UPG_WN_E

Documents

Transcript of UPG_WN_E