UPG_UX_E

Component Upgrade GuideComponent Upgrade GuideComponent Upgrade GuideComponent Upgrade Guide

SAPSAPSAPSAP Web Application Web Application Web Application Web Application

Server 6.20: UNIXServer 6.20: UNIXServer 6.20: UNIXServer 6.20: UNIX

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

4 March 2002

Contents

Upgrade to SAP Web Application Server 6.20: UNIX.................... 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 .....................................14

Upgrade - Step by Step....................................................................... 16SAP Notes for the SAP Web Application Server Upgrade .............. 26Product-Specific Information for the SAP Web ApplicationServer 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 ............................................................39Creating the Upgrade Directory............................................................................................39Checking Database-Specific Requirements for PREPARE.................................................40Making Entries for the Parameter Input Module ..................................................................40

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

General Upgrade Information............................................................. 45Planning the Upgrade .............................................................................................................46

Time Frame for Upgrading the Frontend Software ..............................................................48System Switch Upgrade.......................................................................................................48Planning the Upgrade Strategy ............................................................................................51Database Backup.................................................................................................................54Database-Specific Aspects ..................................................................................................55Upgrades in an MCOD System Landscape .........................................................................57Incremental Table Conversion .............................................................................................58Upgrade Schedule Planning ................................................................................................60Runtime for the Import of the Substitution Set .....................................................................62Upgrading in an SAP System Group....................................................................................63Planning the Modification Adjustment ..................................................................................64Checking Structural Requirements ......................................................................................66Checking Hardware Requirements ......................................................................................67Checking Software Requirements........................................................................................68

Checking the Source Release of the SAP System............................................................68Meeting the Requirements for the Upgrade Assistant.......................................................68Meeting the Operating System-Specific Requirements.....................................................69Upgrading the Operating System and Database System: Overview ................................72

Accessing Documentation Before and During the Upgrade ................................................72Meeting the Requirements for the SAP Internet Solution ....................................................72Importing Additional Languages...........................................................................................74

Upgrade Preparations.............................................................................................................75


March 2002 5

Determining the Host for the Upgrade Preparations............................................................76Making Preparations for Reading the Upgrade CDs............................................................77Creating the Upgrade Directory............................................................................................78Checking Database-Specific Requirements for PREPARE.................................................79Switching the SAP Kernel (Source Release 3.x) .................................................................80Importing the Latest SPAM Update (Source Release 4.x and Higher)................................80Checking SAP Programs (Source Release 4.x and Higher)................................................81Starting PREPARE from the CD ..........................................................................................84Starting the Upgrade Assistant Server.................................................................................85Starting the Upgrade Assistant GUI .....................................................................................86Starting the Upgrade Assistant ............................................................................................87Restarting PREPARE from the Upgrade Assistant GUI ......................................................88Resetting PREPARE............................................................................................................89Importing Software After Starting PREPARE.......................................................................89Making Entries for the Parameter Input Module ..................................................................90Making Entries for the Initialization Module..........................................................................96Making Entries for the Import Module ..................................................................................97Making Entries for the Extension Module.............................................................................98Making Entries for the Installation Module .........................................................................103Evaluating the Results of PREPARE .................................................................................105Making Preparations at the Operating System Level.........................................................112Making Preparations at the Database Level ......................................................................113Making Preparations at the SAP System Level .................................................................115

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

The Upgrade .........................................................................................................................119Starting the Upgrade ..........................................................................................................121Stopping the Upgrade ........................................................................................................121Restarting the Upgrade ......................................................................................................122Phase INITPUT ..................................................................................................................124Phase PATCH_CHK ..........................................................................................................124Phase KEY_CHK ...............................................................................................................125Phase INITSUBST .............................................................................................................125Phase CONFCHK_X..........................................................................................................127Phase VIEWCHK1 .............................................................................................................127Phase REPACHK1.............................................................................................................127Phase JOB_RSVBCHCK2 .................................................................................................128Phase FREECHK_X...........................................................................................................128Phase LOCKEU_PRE........................................................................................................128EU_IMPORT Phases .........................................................................................................129Phase REPACHK2.............................................................................................................130Phase CNV_CHK_XT ........................................................................................................131Phase ADJUSTCHK...........................................................................................................131Phase ACT_...............................................................................................................132Phase VIEWCHK2 .............................................................................................................133Phase MODPROF_TRANS................................................................................................133Phases JOB_RSVBCHCK3 and JOB_RSVBCHCK4 ........................................................134Phase ENVCHK .................................................................................................................135Continuing the Upgrade After the MODPROFP_UPG Phase............................................136Phase CHK_POSTUP........................................................................................................136

Post-Upgrade Activities.........................................................................................................137Executing the saproot.sh Script .........................................................................................139


6 March 2002

DB2 UDB for UNIX and Windows: Specific Actions...........................................................141DB2 UDB for OS/390: Specific Actions..............................................................................141Informix: Specific Actions ...................................................................................................143Oracle: Specific Actions .....................................................................................................144SAP DB: Backing Up the Database ...................................................................................146Distributing SAP Programs ................................................................................................147Renaming the Local System Log (Source Release 3.0x) ..................................................147Checking Profile Parameters with Transaction RZ10 ........................................................148Installing the SAP J2EE Engine .........................................................................................149Reimporting Additional Programs ......................................................................................149Adjusting Repository Objects .............................................................................................150Performing Post-Upgrade Activities for the Applications ...................................................150Rescheduling Background Jobs.........................................................................................151Rescheduling DB13 Jobs (Source Release 3.x) ................................................................152Migrating Matchcodes to Search Help Objects (Source Release 3.x)...............................152Informix: Updating Statistics...............................................................................................153Oracle: Actions for the Cost-Based Optimizer ...................................................................153SAP DB: Updating Optimizer Statistics..............................................................................155Generating ABAP Loads ....................................................................................................156Generating BSP Applications.............................................................................................156Performing Actions for the SAP Online Documentation.....................................................157Performing Post-Upgrade Activities in the Authorizations Area.........................................157Processing Table Clusters After the Upgrade (Source Release 3.x).................................159Installing More Dialog Instances ........................................................................................160Importing Support Packages After the Upgrade ................................................................160Transport Management System: Distributing the Configuration ........................................161Perform post-upgrade activities for the language transport ...............................................161DB2 UDB for OS/390: Removing Empty Database Objects ..............................................162Oracle: Deleting Tablespaces ............................................................................................162Converting Batch Input Logs..............................................................................................163Evaluating the Upgrade Runtime .......................................................................................163

Troubleshooting ................................................................................ 165Upgrade Logs .......................................................................................................................166Analyzing the ELG Log Files ................................................................................................168Correcting Errors in the RFCCHK Phase .............................................................................169Correcting Entries from the INITPUT and INITSUBST Phases............................................170Correcting Errors in the DBCHK Phase................................................................................171Correcting Errors in the BATCHCHK Phase.........................................................................172Correcting Errors in the INTCHK and INTCHK_SW Phases................................................173Correcting Errors in the SPACECHK_ALL Phase ................................................................173Correcting Errors in the JOB Phases....................................................................................174Cleaning Up Terminated Conversions in the DB Conversion Phases .................................175Correcting Errors in the TRBATCHK_XT Phase ..................................................................177Correcting Errors in the RUN_RDDIT006 Phase .................................................................178Correcting Errors in the ACT Phase .....................................................................................179Correcting Lost Field Problems in the PARDIST Phase.......................................................180Correcting Conversion Problems in the PARCONV Phase..................................................181Correcting Errors in the XPRAS Phase ................................................................................182Preparing the Restart of the Upgrade After a System Failure ..............................................184Resetting the Upgrade..........................................................................................................185Scroll Mode: Restart .............................................................................................................188Correcting Problems when Processing ABAP Steps............................................................188Correcting Problems when Starting the SAP System...........................................................190


March 2002 7

Correcting Problems when Copying SAP Programs ............................................................191Correcting Administrator Profile Problems on Application Servers ......................................192Providing SAP Support with Information...............................................................................193

Upgrade Administration ................................................................... 195Alert Function........................................................................................................................196Determining Versions............................................................................................................197Executing PREPARE and R3up in Scroll Mode ...................................................................198Isolating the Central Instance ...............................................................................................199Changing the Database Recovery Mode..............................................................................202Deleting Archived Upgrade Logs ..........................................................................................204Using a Different Upgrade Directory.....................................................................................205Releasing and Confirming Open Repairs and Requests......................................................206

Upgrade Tools ................................................................................... 208PREPARE.............................................................................................................................209

Phase List PREPARE for the SAP Web Application Server Upgrade ...............................211R3up......................................................................................................................................223

Phase List R3up for the SAP Web Application Server Upgrade........................................224Upgrade Phases: Preparations .......................................................................................225Upgrade Phases: Shadow System..................................................................................231Upgrade Phases: Conversions and Import .....................................................................235Upgrade Phases: Post-Upgrade Activities ......................................................................238

Upgrade Assistant.................................................................................................................241Using the Upgrade Assistant..............................................................................................242

Upgrade Monitor ...................................................................................................................244Starting the Upgrade Monitor .............................................................................................245Understanding the Upgrade Monitor Display .....................................................................246

Introduction

8 March 2002

Upgrade to SAP Web ApplicationServer 6.20: UNIXPurposeThis 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 16] 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 parts of this documentation explain the upgrade procedure in detail:

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

General Upgrade Information [page 45]

The next three parts of this documentation give you additional information on troubleshooting,the administration tasks you need to perform before and after the upgrade, and the tools thatyou use to upgrade the system:

Troubleshooting [page 165]

Upgrade Administration [page 195]

Upgrade Tools [page 208]

Both the structure of the documentation [page 10] and the upgrade procedure[page 48] itself have changed significantly for SAP Web Application Server6.10.

ConstraintsThis documentation only applies if you are upgrading your SAP system on UNIX.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 6.10 the structure of the upgrade documentation hasbeen 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 14]

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 16], Product-SpecificInformation [page 31] and SAP Notes [page 26].

Structure of the Documentation

Product-specific

information

Introduction

Upgrade Documentation

Upgrade - Step by Step

Minimuminformation required

Legend:Generalupgrade

procedure

Problems and solutionsUpgrade administration

Upgrade toolsLinked byreferences

Additionalinformation

Austausch-SAP

Notes

The documentation consists of the following parts:

Introduction

The first sections of this documentation are as follows:

New Features in the SAP Web Application Server Upgrade [page 12]

Naming Conventions for the SAP Web Application Server Upgrade [page 14]

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

Upgrade Step by Step [page 16]

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:

Introduction

March 2002 11

Important information, such as user entries

Links to a detailed description of the action

Links to any product-specific information about the action

The upgrade actions are listed chronologically. Use the Upgrade - Step byStep [page 16] section as a checklist for upgrading the system. This ensuresthat you do 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 part of the documentation.

General Upgrade Information [page 45]

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

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

Introduction

March 2002 13

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.

Introduction

14 March 2002

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 Web Application Server 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. If isused, your SAP system ID must be in lowercase letters, for example prd. If isused, you must write in uppercase letters, for example PRD.

ID for the SAP Web Application Server ReleaseIn this documentation, stands for the relevant SAP Web Application Server Release,without a decimal 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.

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, Windows, or DB2 Universal Databasefor UNIX & 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.

Introduction

March 2002 15

OS/390 CI Host and AIX CI HostThis documentation describes the host computers as AIX central instance hosts (AIX CI host)and OS/390 central instance hosts (OS/390 CI host). This means you can distinguishbetween the AIX host and the OS/390 host if your source release is lower than 4.6A.


16 March 2002

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 the upgrade (SAP Web Application Server-specific [page 32]/general [page 46])

Prepare for the upgrade (SAP Web Application Server-specific [page 39]/general [page75])

Upgrade the system [page 119]

Perform post-upgrade activities (SAP Web Application Server-specific [page 42]/general[page 137])

The actions are placed in chronological order, so that you can work through them just like achecklist. Use the links to the general descriptions of the actions and to any additionalproduct-specific information to help you perform the actions.

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




Process Flow

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)

491598 (Oracle)

490325 (SAP DB)


March 2002 17

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 part of the documentation contains additional SAP WebApplication Server-specific [page 32] and general [page 46] information.

Action

You can upgrade the frontend software [page 47] as soon as you receive the softwarepackage.

You familiarize yourself with the features of the System Switch Upgrade [page 48] 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 [page51]).

You define an archiving strategy [page 54] for your database.

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

You check whether your system is an MCOD system [page 57].

You plan the incremental table conversion [page 58], if necessary.

You draw up an upgrade schedule (SAP Web Application Server-specific [page33]/general [page 60]).

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 62]).

You decide on the sequence of upgrades in your SAP system group [page 63].

You plan the modification adjustment [page 64], if necessary.

You check the structural requirements [page 66].

You use transaction RZ10 to check the values of the profile parameters rsdisp/mshostand rsdisp/wp_no_vb.

You check the hardware requirements (SAP Web Application Server-specific [page34]/general [page 67]):

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

UNIX kernel parameters according to SAP Software on UNIX - OS Dependencies

Disk space in the file system for the upgrade directory

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

Oracle: 9 GB, of this 5.5 GB permanently

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


18 March 2002

You check the software requirements [page 68].

Source release of the SAP system (SAP Web Application Server-specific [page35]/general [page 68]):

SAP Basis 4.6D

SAP Web AS 6.10

Upgrade Assistant [page 68]: Java Virtual Machine (at least Version 1.1x if you usethe standard procedure for reading the upgrade CDs then you need Version 1.3)

Operating system [page 69]:

AIX: AIX perfagent package must be installed.

HP-UX and HP-64: at least HP-UX 11 with 64 bit

OS/390 USS: at least z/OS Version 1.2

ReliantUNIX: ReliantUNIX C++ Runtime System Version 2.0A00 or higher

You plan or perform the upgrade of the operating system and database system, ifnecessary (SAP Web Application Server-specific [page 35]/general [page 72]):

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.

Oracle

At least Version 8.1.7 (more information in SAP Note 407314); migrateafter PREPARE, and repeat the General Checks module.

SAP DB

At least Version 7.3.0.20, for PREPARE at least Version 7.2.05.012 andnewest version of DB client software; migrate before PREPARE

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

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

You meet the requirements for importing additional languages [page 74], if necessary.


March 2002 19

Upgrade PreparationsYou can prepare for the upgrade while the system is in production operation. The PREPAREprogram supports you here by making most of the necessary checks automatically. StartPREPARE as soon as possible before the upgrade so that you can perform the necessarypreparations in time.

The Preparing the Upgrade part of this documentation contains additional SAP WebApplication Server-specific [page 39] and general [page 75] information.

Preparations for PREPARE

Action

You choose the host [page 76] for PREPARE and the Upgrade Assistant.

You make preparations for reading the upgrade CDs [page 77].

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

With adm as owner

With a total of 2,800 MB free disk space

DIR_PUT has the value in the instance profile of the centralinstance.

Include approximately 20% extra space in the file system if you have made a lot ofyour own developments. Also do this if you want to include Support Packages andadd-ons.

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

OS/390 Unix System Services: Use a local file system

You check the database-specific prerequisites for PREPARE (SAP Web Application Server-specific [page 40]/general [page 79]). The following free space must be available:

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

Informix: At least 200 MB

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

You import the latest SPAM update [page 80].

You check the version of individual SAP programs [page 81].

Actions for Starting PREPARE

Action

When you start PREPARE for the first time, you must start it from the CD.

1. You start PREPARE from the SAP Kernel CD [page 84] as user adm on thehost with the central instance.

2. You start the Upgrade Assistant server [page 85].

3. You start the GUI of the Upgrade Assistant [page 86].

4. You start the Upgrade Assistant [page 87].


20 March 2002

If you want to restart PREPARE [page 88], for example, if the results from its first run makeyou want to repeat some checks, you can execute it directly.

You can reset PREPARE [page 89] at any time.

If you need extra software after starting PREPARE, you import it now [page 89].

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

User Actions During PREPARE

Action

You make the entries for the Parameter Input module (SAP Web Application Server-specific [page 40]/general [page 90]). This includes entering CD mount directories. Yourequire the following CDs for PREPARE:

CD SAP Kernel, Upgrade CD 1, language CD(s), any add-on CD(s)

You make entries for the initialization module [page 96].DB2 UDB for OS/390: Create or extend stogroups, if necessary.

Make entries for the import module [page 97].

You make entries for the extension module [page 98], such as including SupportPackages.

You make the entries for the installation module [page 103], such as the instance numberand port numbers for the shadow system.SAP DB: If necessary, you change the database parameters MAXUSERTASKS andMAXLOCKS.

Checks Not Supported by PREPARE

Action

You evaluate the results of PREPARE [page 105] in the log file CHECKS.LOG.

You make preparations at the operating system level [page 112]:

You make a backup copy of the old SAP Kernel.

If changes are made to the standard SAP system, you back up the SAP start and stopscripts.

You make the operating system-specific preparations.

You make preparations at the database level [page 113].

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.

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

You make sure that the requirements for the modification adjustment [page 115] havebeen met.


March 2002 21

You use transaction RZ04 to set the operation mode [page 116] for the upgrade.

You import the new front-end software [page 47], if necessary.

The UpgradeThe part of the documentation on actually upgrading the system [page 119] 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 76].

You get the following CDs [page 40] ready, if you have not already stored them in mountdirectories:

CD SAP Kernel, Upgrade CDs 1-2, any language CD(s)

You start R3up [page 121] from the central instance as user adm.

You can stop [page 121] and restart [page 122] the upgrade if errors occur.

Phase INITPUT [page 124]:

You enter the system-specific parameters.

Phase PATCH_CHK [page 124]:

You confirm any unconfirmed Support Packages.

Phase KEY_CHK [page 124]:

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

Phase INITSUBST [page 125]:

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 choose the time when you want database archiving to be switched off.DB2/390: Logging is always activated.

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 127]:

You update your operating system or database to the required version now at the latest, orimport any software you still need.

Phase REPACHK1 [page 127]:

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


22 March 2002

Phase JOB_RSVBCHCK2 [page 128]:

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

Phase FREECHK_X [page 128]:

You make sure that you can recover the old kernel if this becomes necessary.

Phase LOCKEU_PRE [page 128]:

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

Phase EU_IMPORT1 [page 129]:

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

Phases EU_IMPORT2 through EU_IMPORT5: [page 129]

If the relevant CD is not in one of the specified mount directories, you are prompted tochange the CD.

Phase REPACHK2 [page 130]:

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 131]:

You process any uncompleted conversion requests and restart logs.

Phase ADJUSTCHK [page 131]:

Modifications: You confirm the request, if necessary.

Phase START_SHDI_FIRST:

As of this phase you can only log on with the new front-end software [page 47].

Phase ACT_ [page 132]:

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

Phase VIEWCHK2 [page 133]:

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

Phase MODPROF_TRANS [page 133]:

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_RSVBCHCK3 and JOB_RSVBCHCK4 [page 134]:

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

Phase ENVCHK [page 135]:

You repeat any changes made to the environment of user adm before theupgrade, if necessary.


March 2002 23

Phase MODPROFP_UPG [page 136]:

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.

Phase CHK_POSTUP [page 136]:

You remove the P errors before you restart production operation of the system.

Post-Upgrade ActivitiesThe Post-Upgrade Activities part of this documentation contains additional SAP WebApplication Server-specific [page 42] and general [page 137] 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.

Actions Before Restarting Production Operation

Action

You execute the saproot.sh script [page 139].

You perform the database-specific actions:

DB2 UDB for UNIX and Windows (SAP Web Application Server-specific [page42]/general [page 141]): 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 141]: You back up and reorganize the database, schedulean update statistics job, import correction transports, and tune new tables.

Informix [page 143]: You delete the dbspaces and back up the database.

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

SAP DB [page 146]: You set the database parameters to their pre-upgrade state andrestore the ability of the database to be recovered.

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

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

You install the SAP J2EE Engine [page 149]. This action is not optional.

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

You use transaction SPAU to adjust modifications to Repository objects [page 150], ifnecessary.

You perform application-specific [page 150] post-upgrade activities.


24 March 2002

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

Actions After Restarting Limited Production Operation

Action

You reschedule background jobs [page 151] whose release you reset when you isolatedthe central instance.

You perform database-specific actions:

Informix [page 153]: You update statistics.

Oracle: You perform actions for the Cost-Based Optimizer [page 153].

SAP DB [page 155]: You update the optimizer statistics.

You use transaction SGEN to generate ABAP loads [page 156].

If necessary, you generate the BSP applications [page 156] with transaction SGEN.

You perform actions for the online documentation [page 157] according to thedocumentation Installing the SAP Library.

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

You perform post-upgrade authorization activities [page 157].

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 160], if necessary.

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

Actions After Restarting Production Operation

Action

You import Support Packages [page 160], 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 161]: You distribute the configuration to allsystems in the transport domain.

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

You perform database-specific actions:

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

Oracle: You delete old tablespaces [page 162].

You convert old batch input logs [page 163] to the new procedure in all clients, ifnecessary.


March 2002 25

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

You use the report RSUPGSUM to evaluate the runtime of the upgrade [page 163] andsend the list 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 Note Number Database 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 to this upgrade

486274 Informix Informix-specific / specific to thisupgrade

491598 Oracle Oracle-specific / specific to thisupgrade

490325 SAP DB SAP DB-specific / specific to thisupgrade

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.

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 Note Number Topic SAP Note Type

26417 SAP GUI resources: Hardware andsoftware

Frontend/SAP GUI

86985 Release SAP Releases for SAP add- IS-specific


March 2002 27

ons (IS)

76431 Measures for optimizing upgraderuntime 4.x

Upgrade to Release 4.x

83458 Downloading Support Packages fromthe SAP Service Marketplace

SAP Support Packages

125971 Service connection in UpgradeAssistant in SAPNet - R/3 Frontend

Remote support forupgrade

33888 Central Basis objects are modified General upgrade

62519 Correction locks do not belong tosystem

Transport Organizer

51046 Copying the modification adjustmentwithout a central transport directory

Change and TransportSystem

96905 Error message TG063 in the upgradephase JOB_RADDRCHK

ABAP Dictionary

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

137478 Installing a dialog instance/gateway -6.10, 4.6x, 3.1I SR1

R/3 installation

197746 Maintenance Strategy InternetTransaction Server (ITS)

SAP@Web

399578 Publishing IAC objects on the ITS afterthe upgrade

SAP@Web

86627 Transaction types: Customizing forrelease upgrades

Customizing

98752 Migration of the proposal pool Translation tools

482462 Current Note on the 6.20 languageimport

Language transport

352941 Language import and SupportPackages

Language transport

322982 Install language during upgrade Language transport

485741 Dealing with customer translations inthe upgrade

Language transport

73999 Upgrade phase PARDIST_SHD: TG450to TG453

General upgrade

177680 Correcting conversion problems in thePARCONV_UPG phase

General upgrade

40024 Transferring customer files tosapserv using ftp

General upgrade

417670 Additional Information About Resetting General upgrade


28 March 2002

the Upgrade

39473 Locale and TCPOC ReliantUNIX

39745 SETLOCALE on ReliantUNIX andTCPOC table

ReliantUNIX

186066 Increased freespace requirementsduring the upgrade

General upgrade

493387 Potential effects of changes totables/structures

Activation

490788 ICNV in the upgrade to SAP Web AS6.20

ICNV

48550 CD problems in the phases PREPAREand LANG_REQ

General upgrade

430318 Shadow instance on another operatingsystem

General upgrade

94998 Requesting a license key for a system General upgrade

SAP Notes for DB2 UDB for UNIX and Windows


407322 Released operating systems for SAPKernel 6.x DB2 UDB

DB2 UDB for UNIX andWindows-specific

SAP Notes for DB2 UDB for OS/390


400797 DB2/390: Problems when upgrading toOS/390 UNIX System Services

DB2 UDB for OS/390-specific

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

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

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


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


March 2002 29

490057 DB2/390: Upgrade to Web AS 6.20 free space


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


50157 Using recommended versions ofInformix

Informix-specific

407317 Released operating systems for SAPKernel 6.x Informix

Informix-specific

22941 Reorganization of tables and dbspaces Informix-specific

115619 Informix Client versions Informix-specific

SAP Notes for Oracle


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 Rollbacksegments

Oracle-specific

303238 Installation of the Oracle ClientSoftware

Oracle-specific

SAP Notes for SAP DB


407320 Released operating systems for SAPKernel 6.x SAP DB

SAP DB-specific

458553 SAP DB upgrade to 7.3.0.20 SAP DB-specific

34690 Add Devspace under SAP DB(ADABAS for R/3)

SAP DB-specific

46430 SAP DB load with parallel R3LOADS SAP DB-specific

201388 Change a database parameter in SAPDB Release

SAP DB-specific

201390 Back up the database SAP DB SAP DB-specific


30 March 2002

352081 Additional functions relevant to servicesfor SAP DB

SAP DB-specific

362542 Analysis of table sizes and growth SAP DB-specific

Product-Specific Information for the SAP Web Application Server Upgrade

March 2002 31

Product-Specific Information for theSAP Web Application Server 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 part of the documentation.

This part of the documentation has a similar structure to the General UpgradeInformation [page 45]. 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 39]

SAP Web Application Server Upgrade: Post-Upgrade Activities [page 42]


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 also:Planning the Upgrade (General Information) [page 46]

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 to phase MODPROF_TRANS Up to the end of the upgrade

DB2 UDB 5,0 7,0

Informix 6,0 8,0

Oracle 7,0 9,0

SAP DB 5,0 7,0

See also:Planning the Upgrade Strategy (General Information) [page 51]


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 60])

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

Starting the upgrade (see step 2 in the general description [page 60])

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:Upgrade Schedule Planning (General Information) [page 60]

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


34 March 2002

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

OS/390 UNIX System ServicesTo upgrade to OS/390 Unix System Services (OS/390 USS), you need an S/390 G5processor, or another OS/390-compatible processor.

For more information about hardware requirements, see the IBM documentation SAP WebApplication Server 6.20 on IBM eServer zSeries: Planning Guide.

End of the operating system-specific explanations

Space Requirements in the File SystemMake sure that you have about 2,800 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 DatabaseDB2 UDB for UNIX and WindowsThe database is extended by a maximum of 7 GB, of which approximately 5 GB is filledpermanently.

You can free space after the upgrade by deleting the substitution tablespaces of the sourcerelease.

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

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

OracleYou require a maximum of 9 GB of space in the database for the upgrade. Approximately 5.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.

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.


March 2002 35

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

Checking the Source Release of the SAP SystemBefore the upgrade, your system must have the following source release, which has beenreleased for this upgrade and depends on your database system:

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

Upgrading the Operating System and DatabaseSystem: OverviewPurposeWhen 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 FlowDB2 UDB for UNIX and WindowsProceed as follows:

1. Migrate your 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 version: DB2 Version 6.1.0.

2. Operating system of the S/390 server: z/OS Version 1.2 or higher

On UNIX, the upgrade is supported for the OS/390 Unix System Services (OS/390 USS)operating system only. If your central instance is on another UNIX derivative (AIX orSolaris, for example), you have to move the central instance to OS/390 USS beforePREPARE begins.

For information about this, see the Meeting the Operating System-Specific Requirements[page 69] section of this documentation.

3. Required PTFs and APARs:

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. 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 orICLIRUN) as members of this RACF group

For more information about the general procedure, see the IBM documentation SAP R/3on DB2 UDB for OS/390: Planning Guide.

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

5. 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. Depending on your source release, the transports, the release and theminimum required patch level of the kernel are described in one of the following SAPNotes:


March 2002 37

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 to the /usr/sap//SYS/exe/run directory.

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

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

8. Stored Procedures:

As of 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. Theprerequisites and preparations are described in the SAP Web Application Server 6.20 onIBM eServer zSeries: Planning Guide.

InformixFor information on which version of the Informix Dynamic Server you need for this release,see SAP Note 486274.Proceed as follows:


2. If necessary, upgrade the operating system.

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

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


OracleAt the time of going to print, at least Version 8.1.7 is required for SAP Web Application Server6.20 on Oracle for the majority of operating systems.

Proceed as follows:



3. If you have not already done so, migrate Oracle as described in the guideMigrating/Upgrading to Oracle Version 8.x: UNIX.

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


38 March 2002


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 requirements for PREPARE have not been met yet, upgrade the SAP DBnow to the version that is required for the upgrade (7.3.0.020). For more information, seeSAP Note 458553.



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

4. If you have not already done so, upgrade the SAP DB to the version that is required bythe upgrade, or to an even higher database version. The procedure is described in SAPNote 458553.


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


March 2002 39

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

Checking Database-Specific Requirements for PREPARE [page 40]

Making Entries for the Parameter Input Module [page 40]

See also:Upgrade Preparations: General Information [page 75]

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

700 MB 400 MB 300 MB 1,000 MB 400 MB 2,800 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 78]


40 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, 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 (TMPDBSx).

SAP DB

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

End of the database-specific explanationsSee also:Checking Database-Specific Requirements for PREPARE - General Information [page 79]

Making Entries for the Parameter Input ModuleWhen you make entries for the Parameter Input module under Mount Directories for CDs,remember that you need the following CDs as well as the SAP Kernel CD.

CDs Required by PREPARE

CD Title Contents

SAP Kernel Programs and configuration files for the upgrade

Upgrade CD1 Transport requests imported during the upgrade

Language Disc Standard languages English and German

CDs Required by R3up

CD Title Contents

SAP Kernel Programs and configuration files for the upgrade



Language Disc Standard languages English and German


March 2002 41

Optional CDs for the Upgrade

CD Title Contents

Language Disc(s) for thelanguages you want toinstall

Languages other than English and German

For the exact contents, see the file README on the CD.

Add-On CDs Add-ons

See also:Making Entries for the Parameter Input Module (General Information) [page 90]


42 March 2002

SAP Web Application Server Upgrade: Post-Upgrade ActivitiesThis part of the documentation gives you SAP Web Application Server-specific information onactivities you need to perform after you upgrade your system. The following section includesadditional information, or restrictions placed on the general procedures:

DB2 UDB for UNIX and Windows: Specific Actions [page 42]

See also:Post-Upgrade Activities (General Information) [page 137]

DB2 UDB for UNIX and Windows: Specific ActionsDB2 UDB for UNIX and Windows

PrerequisitesYou have not started to operate the system productively.

The variables and are used in the following. Replace the variables asfollows:

If there is more than one SAP system on the database

Use the command echo $DB2DBDFT as user adm to display the value of theenvironment variable DB2DBDFT, and set the value as follows

=

=

If there is only one SAP system on the database =

=

Installing and Updating the DB2 Administration ToolsInstall the administration tools as follows:

Installation of the administration front end

Install the new administration front end as described in the BC R/3 Database Guide: IBMDB2 Universal Database for UNIX and Windows.

You can install the front end either during or after the upgrade. These functions areavailable only after you execute the script saproot.sh.

Creation/update of the administration database

To store administration data (for log file handling, for example), data is stored in the SAPdatabase and in another administration database on the database server under the SAPdatabase instance. The administration database is called ADM and is used tostore data while the SAP database is not available (for example, during a backup).


March 2002 43

1. Log on as user adm and change to the user root with su root (not su -root).

2. Execute the following command://UNIX//DBTOOLS/SDDB6INS -u

This creates the database ADM with standard contents, if it does not yetexist. Otherwise, the database objects are adjusted to the new release in theADM database.

sddb6ins exchanges the program userexit. This program saves the log files tothe log archive directory. The userexit program logs its actions in the databaseADM.

Activating Log ArchivingIf you did not reactivate log archiving for the database with R3up, you must convert thedatabase parameters LOGRETAIN and USEREXIT.

To do this, enter the following commands in the DB2 command line:db2 update db cfg for using LOGRETAIN ON

db2 update db cfg for using USEREXIT ON

For DB2 UDB EEE Only: If you have configured your database with multiple partitions,you must adapt the database parameters on all partitions. To do this, execute thefollowing commands on partition 0 (catalog node):su - db2

db2_all "db2 update db cfg for using LOGRETAIN ON"

db2_all "db2 update db cfg for using USEREXIT ON"

You must then make a complete database backup before DB2 can permitnew database connections.

Backing Up the DatabasePerform a complete backup of the database.

Deleting Substitution TablespacesAfter the upgrade, a number of tablespaces are no longer used and you can delete them.This applies to the following tablespaces in a System Switch Upgrade:

For Non-MCOD Systems For Systems with MCOD LayoutPSAPESD #ES D

PSAPESI #ES I

PSAPELD #ELD

PSAPELI #ELI

where is the source release for the current upgrade.


44 March 2002

To delete a tablespace, enter the following command at the operating system level:db2 drop tablespace

DB2 checks whether there are still database objects in the specified tablespace before itexecutes this command. If there are, the command is not executed.

Updating StatisticsProceed as follows:

1. Log on to the SAP system.You require the authorizations for database administration and background jobs.

2. Call transaction DB13.

3. Double-click a cell in today's date to display a dialog box for scheduling actions.

4. In the list field, choose the action RUNSTATS and REORGCHK for all tables.

5. Set the parameters Maximum runtime and Maximum runtime for long fieldsto 0.This removes runtime restrictions for the job.

6. Select Execute.Runstat_all is scheduled for today and started immediately.

The time required to update statistics depends on the size of the database. You needabout an hour for a database of 2 GB.

7. Check the progress of the job.

To do this, double-click the entry for the action in the calendar. The dialog box with thedetails of the action contains the log file of the job.

Scheduling Update Statistics JobsTo schedule update statistics jobs:

1. Log on to the SAP system.

You require the authorizations for database administration and background jobs.

2. Call transaction DB13.

3. Choose Pattern Setup.

Several defined database actions appear.

4. Choose the following actions:

Check Tables for Statistic

UPG_UX_E

Documents

Transcript of UPG_UX_E