Upgrading to 4.

6C Support Release 2: UNIX

Release 4.6C SR2

SAP AG • Neurottstr. 16 • D-69190 Walldorf 51 013 879

®

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Copyright
©Copyright 2001 SAP AG. All rights reserved. No part of this brochure may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX®-OnLine for SAP and Informix® Dynamic Server Informix Software Incorporated. are registered trademarks of

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139. JAVA® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. ADABAS® is a registered trademark of Software AG. SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, SAP DB are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

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

2

April 2001

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

Typographic Conventions
Type Style Interface Text Represents Words or characters that appear on the screen. This includes system messages, field names, screen titles, pushbuttons, menu names, and menu options. Cross-references to other documentation Exact user entry. These are words and characters that you enter exactly as they appear in the documentation. File names, batch files, paths or directories, and screen messages Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Names of elements in the SAP System. These include report names, program names, transaction codes, table names, and ABAP language elements. Keys on your keyboard. These include function keys (for example, F2) and the ENTER key.

Document Title User Entry File Name <Variable User Entry> NAME

KEY

Icons
Icon Meaning Caution Example Note Recommendation Syntax Tip

April 2001

3

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Contents Upgrading to 4.6C Support Release 2: UNIX ................................. 8
New Features ......................................................................................... 9 Naming Conventions........................................................................... 12 Checklist for the Upgrade................................................................... 13 Planning the Upgrade ......................................................................... 18
Planning the Upgrade Strategy...............................................................................................20 When to Restart Production Operation...................................................................................25 Runtime for the Import of the Substitution Set........................................................................26 Database-Specific Aspects .....................................................................................................27 Incremental Table Conversion................................................................................................30 Drawing Up an Upgrade Schedule .........................................................................................32 Examples of Upgrade Scheduling........................................................................................34 Upgrading in an SAP System Group ......................................................................................36 Planning the Modification Adjustment.....................................................................................37 Time Frame for Upgrading the Frontend Software.................................................................39 Notes for the Upgrade.............................................................................................................40 Checking Structural Requirements .........................................................................................44 Checking Hardware Requirements.........................................................................................45 Checking Software Requirements ..........................................................................................47 Checking the SAP Source Release .....................................................................................47 Meeting the Requirements for the Upgrade Assistant .........................................................48 Meeting the Operating System-Specific Requirements .......................................................49 Accessing Documentation Before and During the Upgrade ...................................................50 Meeting the Requirements for the SAP Internet Solution.......................................................51 Importing Additional Languages .............................................................................................52 Upgrading the Operating System and Database System: Overview......................................53

Upgrade Preparations ......................................................................... 57
Determining the Host for the Upgrade Preparation ................................................................59 Creating the Upgrade Directory ..............................................................................................60 Checking Database-Specific Prerequisites for PREPARE .....................................................62 Substituting the SAP Kernel (Source Release 3.x) ................................................................63 Checking SAP Programs (Source Release 4.x) .....................................................................64 Starting PREPARE from the CD.............................................................................................66 Starting the Upgrade Assistant Server ...................................................................................67 Starting the Upgrade Assistant GUI........................................................................................68 Starting the Upgrade Assistant ...............................................................................................69 Restarting PREPARE from the Upgrade Assistant GUI .........................................................72 Resetting PREPARE...............................................................................................................73 Importing Software After Starting PREPARE .........................................................................74 Making Entries for the Parameter Input Module .....................................................................75 Making Entries for the Initialization Module ............................................................................80

4

April 2001

........................................................................................................................................................................127 Phase CNV_CHK_XT ...........................................................................................1x Only) ........................................................................................114 Phase PATCH_CHK .................................................................... 106 Starting the Upgrade.....131 Phase VIEWCHK2 ...............................................................................................132 Phase ENVCHK.......128 Phase TRBATCHK_XT.............................................120 Phase JOB_RSVBCHCK2...0x/3.................82 Evaluating the Results of PREPARE............................................................................119 Phase REPACHK1 ............................................................105 The Upgrade..................................................................................................................................................................................................................134 Continuing the Upgrade After Phase PRODCHK_<rel>........117 Phase CONFCHK_X..................................................................................................116 Phase INITSUBST ....................................................116 Phase KEY_CHK ..................................................................................................................................................123 Phase LOCKEU_PRE..............................................................131 Phase MODPROF_TRANS .120 Phase JOB_RSVBCHCK3..........................119 Phase VIEWCHK1 ........................................................................................................................................................................................111 Phase DBCHK ...........................................................................................................95 Making Preparations at the SAP System Level ..............................................................1x) ................................................129 Phase RUN_RDDIT006 ....126 Phase REPACHK2 ..................................94 Making Preparations at the Database Level............................0x/3.........................................................................................................................................................................122 Phase FREECHK_X ..................107 Stopping the Upgrade ...................................................................................................................................109 Phase INITPUT.........................................................................................................124 Phase EU_IMPORT0............101 Processing Batch Input Sessions (Source Releases 3....................125 Phase EU_IMPORT4.................................................................126 Phase EU_IMPORT5......................................................................................................................99 Checking Requirements for the Modification Adjustment .................................................................................................................................115 Phases INTCHK and INTCHK_SW .......................................................................................................................100 Setting the Operation Mode for the Upgrade ........................................................................................................................................................113 Phase BATCHCHK ................................................................................................................................................6C Support Release 2: UNIX Making Entries for the Read CD Module .....112 Phase RFCCHK...........................................................................................1x)..104 Processing Direct Input Error Data (Source Releases 3.................................................................................................................................................................133 Phase ACT_<rel> ...........................................................................130 Phase ADJUSTCHK ..............................................87 Making Preparations at the Operating System Level ................................................................................................................................121 Phase SPACECHK_ALL.............135 April 2001 5 ..............................................................................................................................................................................................................................102 Backing Up Wage Types in HR (T512W) (HR Customers) .........................98 Checking the User for the Upgrade ..................................................................................................................................................................................103 Printing the Default Values for Document Type and Posting Key (FI Customers) ..................................................................................................SAP AG Upgrading to 4......102 Converting the Translation Proposal Pool (Source Releases 3.................................................................0x/3......................................................................................................................................108 Restarting the Upgrade..............

........................................................................................................................................................156 Migrating Matchcodes to Search Help Objects (Source Releases 3.............................................. 170 Upgrade Logs ............147 Distributing SAP Programs .....................................186 Resetting the Upgrade ..................................................................................163 Converting Batch Input Logs ...................................................................................................................177 Cleaning Up Terminated Conversions in the DB Conversion Phases ..........149 Renaming the Local System Log (For Source Releases 3....191 Correcting Problems when Processing ABAP Steps.............................................................................. 137 Actions Before Starting Production Operation .......................................................................................................182 Correcting Conversion Problems in the PCON Phase ................................136 Post-Upgrade Activities .................................................................................158 SAP DB: Updating Optimizer Statistics.....173 Correcting Errors in the ACT Phase .................................................................................166 Processing Table Clusters After the Upgrade (Source Release 3................................................................................................................................0x/3.........................................................................................................0x/3.............156 Reimporting Additional Programs .......164 Performing Post-Upgrade Activities for the Application .......................................................................159 Informix: Performing an Update Statistics.............sh ..................................................................................................153 Transport Management System: Distributing the Configuration ......................................185 Preparing the Restart of the Upgrade After a System Failure ...................142 DB2 for OS/390: Preparations ....141 DB2 Universal Database .159 DB2 for OS/390: Actions ..................................................................................................1x) .....................................................179 Correcting Lost Field Problems in the PCON Phase.........................................184 Correcting Entries from the INITPUT and INITSUBST Phases.....................................................................................................................................................1x Only)........................................................................................155 Adjusting Repository Objects ..........................................................160 Oracle: Actions .............................153 Rescheduling Background Jobs..................................................................168 Evaluating the Upgrade Runtime ......146 Oracle: Preparations ......164 Performing Post-Upgrade Activities in the Authorizations Area............................145 Informix: Preparations ...........154 Rescheduling Jobs with Transaction DB13 (Source Releases 3.......Upgrading to 4................187 Scroll Mode: Restart .......................169 Troubleshooting .................................................................175 Correcting Errors in the ADOIM Phase.................................................................................................................................................................................................................138 Executing the Script saproot.............................................................................................................................................1x)........................................................................................................................183 Correcting Errors in the Job Phases..............................................157 Performing Post-Upgrade Activities for the Language Transport ........................................................6C Support Release 2: UNIX SAP AG Phase CHK_POSTUP .....................0x/3....................................................................................................................................160 Generating ABAP Loads ....................................................176 Correcting Errors in the XPRAS Phase ............................................................................................................150 Checking the Profile Parameters with Transaction RZ10 ....................................................................................163 Actions for the SAP Online Documentation ................................................................................................139 SAP DB: Backing Up the Database ...........................................................................................................................................................167 Installing More Dialog Instances ............................................................................1x)................0x/3............................151 Actions During Production Operation ....171 Analyzing the ELG Log Files .......................................................................................................... 152 Importing Support Packages After the Upgrade .............................................192 6 April 2001 ..........................

......................................................... 198 Alert Function............................................................................................................................................................................................................................202 Changing the Database Recovery Mode.....241 Upgrade Monitor ....................212 PREPARE Phase List .....................................................................................224 R3up Phase List ..........................................................................................................................196 Upgrade Administration ...................................................210 Upgrade Tools ...................................................214 R3up......................................................................................................6C Support Release 2: UNIX Correcting Problems when Starting the SAP System.....................................................................................................................................................................................................206 Using a Different Upgrade Directory..................................................................................................................................207 Releasing and Confirming Open Repairs and Requests...SAP AG Upgrading to 4....205 Deleting Archived Upgrade Logs .....................................199 Determining Versions...............................................................................................................................244 April 2001 7 ......................................................243 Understanding the Upgrade Monitor Display ........................................................................................239 Using the Upgrade Assistant.............................................................................242 Starting the Upgrade Monitor ...................225 Upgrade Assistant.............................................201 Isolating the Central Instance ................ 211 PREPARE ................208 Reducing Upgrade Runtime in Modified Systems .....195 Providing SAP Local Support with Information .......................................................................................................193 Correcting Problems when Copying SAP Programs ...........................................194 Correcting Administrator Profile Problems on Application Servers ..........................200 Executing PREPARE and R3up in Scroll Mode ............................................................................................................................................................................................................................................................................................................................................................................................................

and any other documentation referred to in this documentation. performing and following up the upgrade. preparing. The following four sections explain the procedure for the upgrade. and SAP Basis knowledge. such as the Release Notes for the applications that you implement.6C Support Release 2: UNIX Purpose This documentation describes the upgrade and provides you with additional information on upgrade topics.Upgrading to 4. database. The information in this documentation is intended for SAP system administrators with operating system. the administration tasks you need to perform before and after the upgrade. during and after the upgrade: • • • • Planning the Upgrade [Page 18] Upgrade Preparations [Page 57] The Upgrade [Page 106] Post-Upgrade Activities [Page 137] The next three sections of this documentation give you additional information on troubleshooting. this documentation also includes a checklist for the upgrade [Page 13] with all the necessary actions for planning. you require some other information. In addition to this documentation. the SAP Implementation Guide (IMG). the Notes that are specific to this upgrade [Page 40]. 8 April 2001 . Read these sections for an overview of the actions required before. Constraints This documentation only applies if you are upgrading your SAP System on UNIX.6C Support Release 2: UNIX SAP AG Upgrading to 4. and the tools that you use to upgrade the system: • • • Troubleshooting [Page 170] Upgrade Administration [Page 198] Upgrade Tools [Page 211] As well as detailed descriptions of all the procedures.

The number of parallel processes is controlled by the work process resources and the estimated capacity needed to activate the objects in one level. SAP_ABA. • Using a Package Key to include Basis Support Packages To include the Basis Support Packages in the upgrade. April 2001 9 . SAP_APPL and SAP_HR. you need a Package Key. before downtime begins. New Features in 4. • As of source release 4. As of target release 4. Instead you can search for them and include them directly from the BIND_PATCH phase. These levels are then activated in sequence. but can be made unstable by any changes to the ABAP Dictionary that are delivered with the Basis Support Packages. SAP_APPL and SAP_HR. unlike other tools (such as the conversion program).6C Support Release 1 already includes Support Packages 1 through 6 of the components SAP_BASIS.6C • Including Support Package 1 To be able to use GA Release 4. New Features in Release 4. This ensures that Add-On Patches (AOPs) and Conflict Resolution Transports (CRTs) are imported consistently. SAP_ABA. This procedure reduces the downtime during the upgrade. You can now also reduce the number of Support Packages that you want to include without having to reset PREPARE. you must include Support Package 1 in the upgrade for each of the components SAP_BC. This means that you must only include Basis Support Packages that have been released and listed in the above SAP Note. with each of the levels being made parallel with asynchronous RFC. The objects are sorted by their dependencies and split into different levels. the Support Packages are imported directly into the Shadow Repository in the SHADOW_IMPORT phase.6C Support Release 2: • Including Support Packages In the phase BIND_PATCH. • Mass activation of Dictionary objects The mass activation of Dictionary objects is performed in parallel.SAP AG Upgrading to 4.6C productively without restrictions. you now enter all Support Package types on one wizard screen.6C Support Release 1: • • 4. New procedure for including Support Packages in the upgrade You no longer have to use the report RSSPDASS to confirm the Support Packages. The exact procedure is described in the section Making Entries for the CD Read Module. too. which is in SAP Note 119738. The dependencies among the Dictionary objects do not allow multiple activation programs to be started as background jobs in parallel. This is done during the BIND_PATCH phase of PREPARE.6B.6C Support Release 2: UNIX New Features New Features in 4.0B: queue calculation when you include Support Packages The sequence in which you import Support Packages is now determined by the queue calculation function in the Support Package Manager (SPAM).

This makes the separate language import phases obsolete. This shadow import is performed in the SHADOW_IMPORT upgrade phase. Instead it occurs in the shadow repository (new Repository of the target release). 32-Bit Windows is the only supported frontend platform.6A The development of the UNIX frontend was frozen in Release 4. Instead.6A. the transport requests for Support Packages. For more information on transaction ICNV. For more information. R3up informs you if not enough data has been converted incrementally. • Integration of the incremental table conversion function (transaction ICNV) Transaction ICNV is now integrated in the upgrade. Languages are now imported with the transport programs R3trans and tp as part of the table import phases. shadow imports are used as of Release 4. a cross-platform Java implementation is being developed that will also cover UNIX platforms. For the A_switch and A_on strategies.6A • New Upgrade Monitor The Upgrade Monitor lets you follow the progress of the upgrade. The import (Dictionary and main import) is not made into the original Repository (source release). New Features in Release 4. For information on the language transport.6B • Shadow import To minimize the longer downtimes caused by including transport requests. see the SAP Library under Help → SAP Library → Basis Components → Change and Transport System → Language Transport.6C Support Release 2: UNIX SAP AG The minimum number of dialog processes needed to start the mass activation in parallel is six. • No UNIX frontend available for 4.6B when upgrading the SAP System. Industry Solutions. PREPARE determines the tables that would benefit from being converted incrementally and prompts you to start the transaction ICNV. and the modification adjustment are now imported into the SAP System during production operation.5B. New technology implemented in R3trans allows you to use the shadow import and include the transport requests during production operation. R3up checks the progress of transaction ICNV. The upgrade tools provide this resource automatically if at least three background processes are permitted for the upgrade. and helps you recognize processes that are hanging. see Planning the Upgrade → Incremental Table Conversion. This Java GUI is not yet available in Release 4. In the CD Read module. For more information. New Features in Release 4. 10 April 2001 .Upgrading to 4. see The Upgrade → Monitoring the Upgrade → Upgrade Monitor. see SAP Note 26417. This technology will also be used in other cases to minimize upgrade downtime as much as possible. • Language transport The technical basis of the language transport has been changed completely. This makes sure that the conversion during downtime is as short as possible. which is loaded into the SAP System during the EU_IMPORT phase.

the JOB_BTCTRNS2 phase deschedules them. see the online documentation in the transaction by choosing Info. you had to manually deschedule background jobs during the upgrade (when you isolated the central instance). you had to manually schedule the jobs again.SAP AG Upgrading to 4. After the upgrade. April 2001 11 . For a detailed description of transaction SGEN.6C Support Release 2: UNIX • As of Source Release 4. The Job Monitor (transaction SM37) gives the automatically descheduled jobs a special status.5B or higher.5B: Automatic scheduling and descheduling of background jobs Previously. • Transaction SGEN for generating ABAP loads Transaction SGEN replaces the report RDDGENLD. The upgrade program now performs this task for you if your source release is 4. It offers you many more options for selecting the amount of objects that need to be generated and for controlling the background job that generates the objects. The JOB_BTCTRNS1 phase schedules the background jobs.

SAP-System-ID The SAP System ID is abbreviated as SAPSID or sapsid in this documentation. The abbreviation 4. DB2 for OS/390 and DB2 Universal Database In this documentation and in the upgrade dialogs. DB2 Universal Database for UNIX & Windows was known as DB2 common server (DB2/CS) or DB2 Universal Database for UNIX. This documentation only uses the name SAP DB. Hot Packages are now called R/3 Support Packages. SAP is also used as a synonym for R/3 in terms such as SAP start profile or SAP System language. the SAP ID DB6 is used as well. In older versions of this documentation.Upgrading to 4. such as Basis Support Packages or AddOn Support Packages.6C is also used as a synonym for the abbreviation 4. SAP uses the term Support Packages instead of SAP patches. and Legal Change Patches are called R/3 HR Support Packages. the term SAP System is the same as R/3 System. SAP DB and ADABAS SAP now offers the database SAP DB.6C SR2. in certain cases. the term Release 4. for example prd.6.6C Support Release 2. Windows.6C is the same as 4. R/3 System and SAP System In this documentation. DB2 for OS/390 is used to describe the database DB2 Universal Database for OS/390. SAP plans to support all SAP Releases on SAP DB that were supported on ADABAS. DB2 Universal Database (or the abbreviation DB2 UDB) is used to describe the database DB2 Universal Database for UNIX & Windows. SAP DB is an enhanced and extended database offered by SAP since 1997 that is based on ADABAS database technology. for example PRD. DB2 Universal Database for UNIX & Windows and DB2 common server In this documentation and in the upgrade dialogs. 12 April 2001 . Support Packages and Patches As of Release 4. DB6.6C and 4. If <SAPSID> is used. Existing customers on SAP DB/ADABAS receive SAP DB as a part of their maintenance contract. and. your SAP system ID must be in lowercase letters. DB2.6C Support Release 2 In this documentation.6C Support Release 2: UNIX SAP AG Naming Conventions Release 4. and in certain cases. you must write in uppercase letters. If <sapsid> is used. the SAP ID DB2 is used as well. There are other types of Support Packages.

SAP AG Upgrading to 4. It is not intended to replace the documentation Upgrade to 4. operating system) Meet the requirements for installing the online documentation according to the guide Installing the SAP Library. preparing. If necessary. If necessary.6C. Make sure that DIR_PUT in the instance profile of the central instance has the value <upgrade_directory> Include 20% extra space on the database if you intend to carry out a lot of development April 2001 13 .6C Support Release 2: UNIX Checklist for the Upgrade Definition This checklist includes all activities necessary for planning. since it does not include all the information relevant to the upgrade. meet the requirements for the SAP Internet Transaction Server and the SAP@Web Studio according to the installation guide SAP@Web Installation Guide. Prepare the empty upgrade directory with <sapsid>adm as the owner. and following up the upgrade. make preparations for importing additional languages If necessary. plan the modification adjustment Before you start the upgrade decide which database-specific actions you need to take and include them in your upgrade schedule Checking Structural Requirements Checking Hardware Requirements Check software requirements (SAP source release. Planning the Upgrade Meeting the Requirements Activity You can upgrade the frontend software as soon as you receive the upgrade package Request current upgrade notes Define the upgrade strategy in connection with the operating system upgrade and the database upgrade Draw up the upgrade schedule If necessary. Upgrade Assistant. performing. upgrade the operating system and database system Preparations for PREPARE Preparing for PREPARE Activity Choose the correct host for PREPARE and the Upgrade Assistant.

1x.0x. material master (industry): process the direct input error data If necessary.Upgrading to 4.1x in translation systems. process batch input sessions For source releases 3. upgrade frontend software 14 April 2001 . 3.1x. start transaction ICNV Checks Not Supported by PREPARE Preparing the Upgrade Activity Analyze the results of PREPARE Make a backup copy of the old SAP Kernel If changes are made to the standard SAP System. Make database-specific preparations Check the users and authorizations needed for the upgrade Make sure that the requirements for modification adjustment have been met Set the operation mode for the upgrade For source releases 3. Also do this if you want to include Support Packages and add-ons.6C Support Release 2: UNIX SAP AG work. check the version of each SAP program Start PREPARE from the CD SAP Kernel User Actions During PREPARE Activity Make entries for the Parameter Input module.1x. back up the SAP start and stop scripts. such as entering CD mount directories Making Entries for the Initialization Module Make entries for the Read CD module. check version of SAP Kernel For source release 4.0x/3.0x/3. Make operating system-specific preparations: Make sure that you can recover the database to the state it had before the upgrade. Make database-specific preparations for PREPARE For source releases 3.0x/3. such as including Support Packages. convert proposal pool For HR customers only: save table T512W (Wage Types in HR) For FI customers only: print out the default values for document type and posting key For source releases 3. provide an extra 300 MB of memory for each language in the database. If you want to import languages other than English and German.x.

if necessary For ICNV. lock the ABAP Workbench if necessary Phase EU_IMPORT0: For A_off. change database recovery mode. and change database recovery mode. check converted percentage rate Phase REPACHK2: For A_switch and A_on. change database recovery mode. stop application server.6C Support Release 2: UNIX The Upgrade Activities Activity Check the general upgrade note and the database-specific upgrade notes for new entries or changes Select the correct host for the upgrade Start R3up Phase INITPUT: enter system-specific parameters Phase KEY_CHK: enter keyword from the current Upgrade Note If necessary. adjust any modified SAP objects with the SAP standard Phase PRODCHK_<Rel>: Choose a new time for restarting production operation or: For A_on. change the database recovery mode if necessary Phase ENVCHK: if necessary. start secondary application server April 2001 15 . last chance to lock the ABAP Workbench Phase ADJUSTCHK: If there are modifications. and back up upgrade directory For A_switch. repeat changes to the environment Phase KX_SWITCH: as of this phase you can only log on with the new frontend software Phase ACT_<Rel>: For modifications. confirm the transfer request if necessary Phase VIEWCHK2: delete customer tables if necessary Phase MODPROF_TRANS: For A_switch and A_on. specify the runtime of the import of the substitution set Phase LOCKEU_PRE: For A_switch and A_on. back up database. stop application server. enter keyword for industry solution Phase INITSUBST: Determine when to restart production operation For A_switch and A_on. start secondary application server For A_switch and A_off. determine P errors. determine P errors. isolate central instance.SAP AG Upgrading to 4. isolate central instance.

import them before you import the Support Packages as described in the guide Language Transport Perform post-upgrade activities for the Transport Management System (TMS) Reschedule background jobs whose released status was reset when isolating the central instance For source releases 3. distribute SAP programs For source releases 3. post-upgrade activities: If necessary.sh Perform database-specific actions If there is no central software storage point. reset to default value Actions After Starting Production Operation Activity Import any Support Packages that you need If you want to install additional languages.6C Support Release 2: UNIX SAP AG Post-Upgrade Activities Activities Before Starting Production Operation Activity Execute the script saproot. adjust Repository objects with transaction SPAU If necessary. reschedule jobs with transaction DB13 If necessary.0x/3. install the SAP Internet Transaction Server and SAP@Web Studio according to the upgrade guide SAP@Web Installation Perform post-upgrade activities in the authorization area Perform application-specific.1x. rename local system logs Check profile parameters using transaction RZ10 and if necessary.Upgrading to 4. perform upgrade and delta Customizing For HR customers: reload table T512W (Wage Types in HR) 16 April 2001 .0x/3. migrate matchcodes in search help objects. re-install additional programs such as RFC-SDK or CPIC-SDK from the CD Presentation For source releases 3.1x: if remote application servers exist. if necessary Performing Post-Upgrade Activities for the Language Transport Perform database-specific actions Generate ABAP loads with transaction SGEN Converting Batch Input Logs Install the online documentation according to the installation guide Installing the SAP Library If necessary.1x.0x/3.

0x/3.R/3 Frontend connection April 2001 17 .SAP AG Upgrading to 4.6C Support Release 2: UNIX Actions Before the Next Upgrade Activity For source releases 3.1x only: perform post-processing for table clusters EDIDOC and CDCLS If necessary. install more dialog instances Evaluating the Upgrade Runtime Activity Analyze the runtime of the upgrade using report RSUPGSUM / Send list to SAP with SAPNet .

and also means you must pay attention to certain database-specific aspects [Page 27]. 2. A team of experts checks the parameter settings of your system in one session before the upgrade. You plan the upgrade of the frontend software [Page 39]. 4. You draw up your upgrade schedule [Page 32]. If necessary. see SAPNet under Services → Consulting Services → SAP GoingLive Functional Upgrade Check. you must first plan it carefully. After the upgrade. the hardware requirements [Page 45] and the software requirements [Page 47] are met. You make sure that the structural requirements [Page 44]. Process Flow Do not perform any additional actions during the upgrade that could place it at risk. You must decide on an upgrade strategy [Page 20]. Your local support is your contact for ordering service. When you plan the upgrade. For information on services. You make sure that you can access the online documentation [Page 50]. To make sure that the requirements are met. You can repeat the program as often as you need before starting the actual upgrade. Do not forget the sequence of the upgrades in an SAP system group [Page 36]. TeamSAP offers the free upgrade service SAP GoingLive Functional Upgrade Check. 7. The successful execution of PREPARE is a prerequisite for starting the upgrade. All the times specified in this guide are based on hardware with average performance. 3. the parameters and the entire system status are checked again in a second session. you plan a modification adjustment [Page 37]. 5. and gives you detailed recommendations on the configuration. This is the prerequisite for a successful SAP System upgrade. You can also convert some of the tables before you start the upgrade using incremental table conversion [Page 30]. run the PREPARE [Page 212] program as soon as possible. This section helps you plan your upgrade so that downtime is reduced to a minimum. You request the necessary Notes [Page 40].6C Support Release 2: UNIX SAP AG Planning the Upgrade Purpose Before you begin the actual upgrade. 6. Start planning your upgrade at least two to three weeks before you want to start. It is aimed in particular at SAP system administrators who are upgrading a system with the Repository Switch procedure for the first time.Upgrading to 4. The strategy you choose influences the time needed for the upgrade. you must do the following: 1. and the upgrade runs as efficiently as possible. 18 April 2001 .

If you are upgrading a modified system where changes have been made to the standard system. April 2001 19 . 9. This procedure eliminates the need for time-consuming adjustments to the production system. If necessary. We recommend testing the upgrade in a development system.6C Support Release 2: UNIX 8. and contains the same modifications. which you can use to monitor your progress in the upgrade project. The adjustments you perform manually for the new standard in this system can be automatically exported to the global transport directory and are integrated in the production system upgrade from there. you plan the installation of the SAP Internet Solution [Page 51]. If necessary. preparing. you upgrade the operating system and database system [Page 53]. you have to start by upgrading a development or quality assurance system that has the same SAP release (including Support Packages). performing and following up the upgrade. The checklist for the upgrade [Page 13] is a concise overview of all required actions for planning.SAP AG Upgrading to 4.

Database mechanisms save database actions that occur in the first half of the upgrade. The upgrade strategy also determines the times at which you must make a complete backup of the system.6C Support Release 2: UNIX SAP AG Planning the Upgrade Strategy Purpose Choose the upgrade strategy best suited for your SAP System. SAP Upgrade Strategies There are three upgrade strategies available: A_switch • • • Imports the substitution set during production operation. You can no longer operate the system productively. • The time intervals in which the actions are saved on the database by database mechanisms This mode is database-specific and is defined as follows: SAP DB DB2 Universal Database DB2 for OS/390 Informix Oracle Logging is activated LOGRETAIN and USEREXIT set to ON No mode for deactivating logging Database backup mode activated Database is operated in ARCHIVELOG mode This determines whether the database system can recover lost data.Upgrading to 4. This part of the procedure can run during production operation. You can recover the database to its current state during the first half of the upgrade. The most suitable upgrade strategy depends on two factors: • • • The maximum downtime permitted in the system The size of the database The upgrade strategy defines: whether the substitution set is imported into the shadow tables during production operation or during downtime. 20 April 2001 . you can recover the database to its state after the import of the substitution set. "Shadow tables" are tables which the running SAP System does not recognize at this point. In the second half of the upgrade. − The Repository Switch can be divided into two parts: • Importing the substitution set into the shadow tables The database tables referred to as the substitution set comprise almost the complete SAP Repository. • Substituting the old Repository with the new Repository This part of the Repository Switch substitutes the Repository by deleting the old Repository and renaming the shadow tables.

6C Support Release 2: UNIX A_on • • • Imports the substitution set during production operation. Database mechanisms save database actions that occur in the during the entire upgrade. Database mechanisms do not save database actions during the upgrade. April 2001 21 . Comparing the Strategies A brief overview of the advantages and disadvantages of the individual strategies: Strategy A_switch Advantages Short downtime Medium storage requirements for ensuring database recovery Disadvantages Offline backup necessary after upgrade Monitoring necessary to determine if disks for ensuring recovery are full Greatest additional space requirements to ensure database recovery Monitoring necessary to determine if disks for ensuring recovery are full A_off No additional space requirements for ensuring possible recovery Offline backup necessary after upgrade Longest downtime No monitoring necessary to determine if disks for ensuring recovery are full.SAP AG Upgrading to 4. the downtime begins in phase EU_IMPORT0. You can only recover the database to its state before the import of the substitution set. A_off • • • Production operation ends before the substitution set is imported. The graphic below shows the upgrade procedure for the different strategies. You can recover the database to its current state during the entire upgrade. The upgrade is divided into phases. since these mark the beginning of downtime. A_on and A_switch are identical until phase MODPROF_TRANS. The procedure is the same for all the strategies up to phase EU_IMPORT0. It does not take differences in the duration of the upgrade into consideration. For A_switch the mode in which the database operates is changed. The mode in which the database operates changes. Then downtime begins for both. A_on Shortest downtime No offline backup necessary after upgrade The runtime of the upgrade and the amount of uptime or downtime involved are heavily dependent on the upgrade strategy you choose. With strategy A_off. depending on the strategy chosen. but not for A_on. The important phases are EU_IMPORT2 and MODPROF_TRANS.

0 0.0 0.6C Support Release 2: UNIX SAP AG Upgrade Process Flow A_switch Start PREPARE Start R3up A_on PREPARE A_off R3up check phases Choose upgrade strategy Phase EU_IMPORT0 Import substitution set Phase MODPROF_TRANS Import substitution set Repository Switch Legend: Actions by R3up or PREPARE User actions Prompt for upgrade strategy Default: A_switch Repository Switch Repository Switch End of R3up Offline backup Online backup Offline backup Downtime Production The total runtime of R3up depends on how long it takes to import the substitution set. database type.0 0. If you choose the strategies A_switch or A_on.5 7. The following table shows the sizes of the archives created for the different upgrade strategies and databases.0 The following graphics show an analysis of the upgrade runtimes and downtimes registered by SAP customers for Releases 4. the better the performance during production operation.4.5 15. The longer the runtime you choose. 22 April 2001 . Comparison of the Archives in GB A_switch SAP DB DB2 UDB Informix Oracle 7.5 A_on 9.0 13. you choose the runtime of the import [Page 26] yourself.5 A_off 0. and the time it takes to create the database archives. These sizes are based on sample data.0 .0 22. The downtime depends on the upgrade strategy you choose. source release or database size.0 12.Upgrading to 4. Each additional language that you import increases the minimum duration of the import by about an hour.6. This data has not been sorted by operating system.5 7.

SAP AG Upgrading to 4.6C Support Release 2: UNIX Runtime Distribution 250 Number of upgrades 200 150 100 50 0 0-4 4-8 8-12 1216 1620 2024 2428 2832 3236 3640 4044 4448 Runtime (hours) Downtime Distribution 300 Number of upgrades 250 200 150 100 50 0 0-4 4-8 8-12 1216 1620 2024 2428 2832 3236 3640 4044 4448 Downtime (hours) April 2001 23 .

The following factors can also influence runtime and downtime of the upgrade: • • • • • • • Hardware Installed languages Number of clients A significant amount of customer developments Modifications to the standard SAP tables Add-on software Integrated Support Packages The hardware that you use has the greatest influence on total runtime and downtime. 24 April 2001 .6C Support Release 2: UNIX SAP AG Your source release can influence the runtime and downtime of the upgrade by up to approximately 25%. Both strategies allow you to work productively during the first half of the upgrade. even though R3up is still running. The size of your database only has a secondary role in determining the runtime of the upgrade. Strategy A_on also allows you to work productively at the end of the upgrade. Guideline for the Duration of Production Operation During the Upgrade A_switch A_on From: Start of R3up To: Start of downtime Duration can be configured From: End of downtime To: End of R3up 1) 34 hours 1) 34 hours 1) 0 hours 1 hour 1) Minimal reduction in performance will occur during production operation.Upgrading to 4. The following table shows you how much time you can gain for production operation by using strategy A_switch or A_on.

SAP AG Upgrading to 4.6C Support Release 2: UNIX When to Restart Production Operation Process Flow All three strategies allow you to enter the latest date and time by which you want to resume production operation of your SAP System. You are also requested to carry out certain actions (for strategies A_off and A_switch. it is necessary to make an offline backup). even if the time you entered is earlier. In this case R3up informs you that the SAP System can resume production operation although R3up is still active. for example. If R3up has reached the post-upgrade phases when this time is reached. This reduces the downtime towards the end of the upgrade and during post-upgrade activities. When selecting this time. you do not need to wait until R3up completes its run before resuming production operation. pay attention to the following: Production operation is only possible from upgrade phase PRODCHK_46C onwards. The upgrade always executes up to the PRODCHK_46C phase. April 2001 25 .

If you enter a longer runtime. Depending on the hardware. This enables you to sustain the performance of the system and also to reduce the number of archives (Oracle) or log files (SAP DB. Depending on the start time of the upgrade. the import will be slowed down accordingly. 26 April 2001 . specify total runtimes of about 24 hours.Upgrading to 4. DB2 for OS/390 and Informix) that need to be saved per hour.6C Support Release 2: UNIX SAP AG Runtime for the Import of the Substitution Set Process Flow With strategies A_switch and A_on you are asked to specify the total runtime for the import of the substitution set. an import takes about six hours without delays. DB2 Universal Database.

After the log backup has been confirmed and checked. This means that you must back up the database for all strategies. R3up switches the log mode to DEMO for the strategies A_off and A_switch. April 2001 27 . R3up waits for your confirmation before it stops the central instance. You must be able to recover the database to the state it has at this point. DB2 Universal Database • Isolating the central instance When the central instance is isolated (in the MODPROF_TRANS phase with A_on and A_switch. For all strategies. R3up switches the parameters LOGRETAIN and USEREXIT to OFF after confirmation. When the central instance is isolated (in the MODPROF_TRANS phase with A_on and A_switch. in the EU_IMPORT2 phase with A_off).6C Support Release 2: UNIX Database-Specific Aspects SAP DB The performance for the development environment (DE) import (mass insert) depends largely on the log devspace. The concatenated archive logs can be located on one disk without a loss of performance. At this point the tables relevant to the upgrade are checked to see if they contain sufficient statistical information. If the statistics for less than 15 tables are out-of-date. their mirrors should be on other disks. when the system stops operating productively. however. you are requested to stop all work in the system. To activate these parameters. The statistics values for newly imported tables are updated automatically after the DE import. • Database backup before the upgrade You must be able to recover the database to its state before the upgrade was started. the contents of the log are permanently lost. an incremental backup is sufficient (save updated pages). create an online backup before the system starts operating productively again. To ensure this. With the strategies A_off and A_switch. R3up waits for your confirmation before it stops the central instance. shut down the database and reboot it. you can choose to update them or to terminate the upgrade. they are updated automatically. You can decide if you want a very fast import which switches logging off completely for the import. The log configuration can be changed with the database command alter log in the database tool xcontrol. you need to create an online backup before you stop operating the system productively.SAP AG Upgrading to 4. Make sure that the log devspaces are on different hard disks. at the latest. We recommend that you update the statistics values with the tool xpu shortly before the upgrade. After the mode has been switched. If the statistics for more than 15 tables are out-of-date. in the EU_IMPORT2 phase with A_off). If large amounts of data are involved. you are requested to stop all work in the system.

You can find a description under Changing the Database Recovery Mode [Page 205]. You can also make an online backup after an upgrade with the strategies A_switch and A_on. You can find the necessary commands under Changing the Database Recovery Mode [Page 205]. you do not have to import all logical log files written until this time. R3up waits for your confirmation before it stops the central instance. You must be able to recover the database to the state it has at this point. For strategy A_on we recommend that you create a full online backup at the end of downtime. The database forces you to create a complete backup (otherwise a CONNECT to the database is not possible). This makes sure that you do not need to perform a recovery that uses the logical log files created during the upgrade. You must make the offline backup before you confirm that you want to deactivate archiving. After the database backup. Logging is always switched on regardless of the upgrade strategy. R3up switches the parameters LOGRETAIN and USEREXIT to ON for strategies A_off and A_switch after confirmation. but not the database logging. you must make an online backup. You can recover the database to its current state during the entire upgrade. You can choose an online or an offline backup. You must be able to recover the database to the state it has at this point. you must now create a complete backup for the strategies A_off and A_switch. including those written during the previous import. Oracle At the start of the downtime (in the MODPROF_TRANS phase with A_switch and A_on. This makes sure that in the event of a database crash. You can choose between an online and an offline backup. • A_switch You are then asked to switch off database archiving. You are prompted to deactivate the database backup mode. you are asked to stop all work with the system. Informix When the central instance is isolated. in the EU_IMPORT0 phase with A_off) you are asked to stop all work with the system. The upgrade strategy influences the downtime. Now make a complete backup of your database so that if you need to recover it you do not have to import all the archives created so far. continue in R3up. 28 April 2001 . This has the following effects: • • • • There is no difference between the strategies A_switch and A_on.6C Support Release 2: UNIX SAP AG • Database backup at the end of the upgrade At the end of the upgrade. DB2 for OS/390 Database actions are backed up during the entire upgrade by database mechanisms. After the upgrade. For this reason. You must make the online backup before the central instance is stopped.Upgrading to 4. R3up waits for your confirmation before it stops the central instance.

• A_off You must be able to recover the database to the state it has at this point. make a new complete backup now. create a complete online backup (possibly as a postupgrade activity) to avoid a recovery based on upgrade database archives. You can find a description under Changing the Database Recovery Mode [Page 205].SAP AG Upgrading to 4. If some time has elapsed since the last complete backup of your database. so that you do not have to import all the archives created up to this point if there is a database failure. At the end of downtime.6C Support Release 2: UNIX • A_on With strategy A_on you do not switch off database archiving. Note that a large number of database archives have to be saved at regular intervals during downtime. You can choose an online or an offline backup. End of the database-specific explanations April 2001 29 . You are then asked to switch off database archiving.

you may need to completely restructure the relevant tables by converting each data record. Incremental conversion is optional. End of SAP DB Prerequisites To be able to use this function. which modified tables you want to return to the SAP standard and convert incrementally. If you do not want to use this function. Monitor the conversion. you must first run PREPARE. you can convert many of these data records before the upgrade. In some cases. the tables are converted in the phase PCON<rel>.Upgrading to 4. PREPARE asks you to start the incremental conversion. If these checks return positive values. By using incremental conversion. Estimate the runtime of the conversion. • • • Start the conversion.6C Support Release 2: UNIX SAP AG Incremental Table Conversion Represents With each new release. You can use the following functions: • • Display the tables determined by PREPARE (tables for conversion with ICNV) Choose − − which non-modified tables you want to convert incrementally. 30 April 2001 . the structure of the tables in your database changes. This gives you several advantages: • • • Reduced downtime during the upgrade You can return to the SAP standard more easily for modified tables You can use incremental conversion for large tables as well SAP DB SAP DB does not support incremental table conversions. More information is available online in transaction ICNV by pressing F1 or selecting the i button. These table conversions used to only occur during the downtime of the upgrade (phase PCON_<rel>). Examples of these are tables that contain large amounts of data and would significantly extend downtime if they were converted. Functions Incremental table conversion is performed using transaction ICNV. PREPARE checks whether the system: • • runs on a database platform that supports incremental conversion contains tables for which an incremental conversion is useful. The necessary data is converted during production operation.

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

What to look for: •

Whereas the PREPARE actions have an analyze function, the ICNV does not. Transaction ICNV already makes modifications to the database tables that you want to convert during the Initialization step. These modifications are not canceled by resetting PREPARE. In particular, you cannot directly upgrade the release of these modifications. For this reason, only start the incremental table conversion if you then want to perform the upgrade. If you use incremental table conversion, do not start an SAP archiving program for these tables in parallel, since this can lead to performance bottlenecks. Therefore, archive as much as possible before starting the conversion. After the incremental conversion starts, you cannot change any more Dictionary definitions for the relevant tables until the upgrade is complete. This affects changing, deleting or adding field definitions. Transaction SE11 is locked for these tables. Pay special attention to the resource usage of your database management system to detect bottlenecks early on. Incremental conversion requires double the space in the relevant database container (tablespace, dbspace, and so on) for each affected table during the conversion. The continuous data transfer results in more transactions. Therefore, also monitor the space for the rollback information. Do not begin the upgrade before at least 95% of the total data has been converted. R3up checks this at the beginning of downtime. If this percentage has not been reached, R3up displays a corresponding message. This gives you the advantage of reducing critical downtime. You can monitor the progress of the conversion using transaction ICNV. You can start the upgrade even if the 95% minimum is not reached. However, the remaining data is transferred entirely during the downtime.

Incremental conversion requires a sufficient number of background work processes. Ideally, there should be one process for each table to be converted. If you cannot have one process for each table due to a large number of tables, you can still convert the tables since transaction ICNV distributes the tables itself to the available background processes. However, the incremental conversion takes longer to complete, and the time for beginning the upgrade is pushed back.

April 2001

31

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Drawing Up an Upgrade Schedule
Purpose
Create an exact schedule for your SAP System upgrade.

Prerequisites
You have decided on one of the three upgrade strategies A_on, A_switch or A_off.

Process Flow
1. You decide when you want to begin the preparations for the upgrade.
At the latest, start preparing for your upgrade a week before starting the upgrade.

2. You decide when you want to begin the upgrade. If you have decided to use the A_off upgrade strategy, start the upgrade on the last day of production operation with the old release. If you have decided to use strategy A_switch or A_on, start the upgrade on the second to last day of production operation with the old release. In all cases, you can start the import of the substitution set with the phases EU_IMPORT0 to EU_IMPORT5 towards the end of the day.

You are prompted to change the CD at the beginning of the phases EU_IMPORT4 and EU_IMPORT5. Phase EU_IMPORT4 has a runtime of about 30 minutes, phase EU_IMPORT5 has a runtime of about 3-4 hours. If you miss this prompt, your time schedule could be seriously disrupted. 3. Take the necessary measures to extend the time in which the upgrade can run unmonitored. a. Specify all CD mount directories at the start of the upgrade
R3up lets you specify up to 16 CD mount directories when you start upgrading. This significantly increases the amount of time R3up can run without user input.

The prompt for the mount directories occurs during the INITPUT phase, which runs during PREPARE and during the upgrade itself. You are only prompted for the mount directories, which means that it does not matter where the CDs are mounted. As long as the program finds a CD with the correct label, it does not prompt the user to change the CD. If you do not have enough CD disk drives, you can copy the contents of each CD to separate directories on your hard disk (providing you have sufficient disk space). A maximum of 650 MB per CD is required. You then enter these directory names when prompted for the mount points. b. For a list of the CDs that PREPARE needs, see Making Entries for the Parameter Input Module. For a corresponding list for R3up, see The Upgrade. c. Early locking of the ABAP Workbench If you have decided to use upgrade strategy A_switch or A_on:

32

April 2001

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

The phase LOCKEU_PRE is directly before the phase EU_IMPORT0. In LOCKEU_PRE you are asked when the ABAP Workbench can be locked. If you are sure that you do not need the ABAP Workbench from phase EU_IMPORT0 onwards, confirm the lock in LOCKEU_PRE. If you do not confirm the lock in LOCKEU_PRE, you are asked to confirm the lock in REPACHK2. Since phase REPACHK2 is after the last CD change (phase EU_IMPORT5), you may not want to do this. d. Avoiding long upgrade downtimes. The Upgrade Assistant can inform you if R3up waits for a long period of time for an entry. This can be either a standard user entry or an action taken to correct an error. To receive this alert information, you have to activate the alert function and supply the relevant parameters. You can specify an external program to be started if R3up has been waiting too long for an entry. This then triggers a communications service that informs the system administrator. You must provide this external program yourself. You can find more information on the alert function in the online help in the Upgrade Assistant in the section Set Alert Window. To access the online help, go to the main menu and choose Help → Introduction. Whether you use the Upgrade Assistant or not, the R3up control program stops the upgrade if errors occur so that you can take action. R3up indicates that you should take action as follows:
− −

A message appears on the screen. The file upalert.log is created in sub-directory tmp of the upgrade directory.

If you do not notice these errors, significant delays can occur in your time schedule. To avoid losing time unnecessarily, you can arrange to be notified automatically, for example, by telephone, that the upgrade has stopped. You can use the alert file to do this. You must provide the appropriate software for using the alert file. 4. You decide when you want to back up the database after the upgrade. If you decide to use upgrade strategy A_off, start the complete backup after the end of the upgrade on the evening of the second day. If you decide to use upgrade strategy A_switch, start on the morning of the third day. For all the upgrade strategies, you can resume production operation at the beginning of or during the third day. 5. Extend the time for the import of the substitution sets during production operation. You need approximately 6.5 hours to import the substitution sets. To avoid lowering system performance, extend this time. Set the time required for the import so that it ends at least 5 hours before the planned shutdown of production operation. At the latest, system downtime begins in the MODPROF_TRANS phase. The earliest you can resume production operation is approximately 10 hours later. During this time the SAP System is started up several times. 6. You decide when production operation resumes. If possible, do not resume production operation until all the necessary post-upgrade activities have been performed. The same applies to the complete backup of the database, which is a requirement for resuming production operation for upgrade strategies A_off and A_switch.

April 2001

33

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

This has the advantage that all database changes resulting from post-upgrade activities are included in the complete backup. The earliest possible point for continuing with production operation is PRODCHK_<release>.

Examples of Upgrade Scheduling
The tables below show examples of an upgrade schedule for each of the three strategies. The modification adjustment was run during the night in order to show the shortest possible runtime. You can also run it during the day. The schedule would then take correspondingly longer. The language import was not taken into consideration in these examples. For SAP System languages other than 'EN' (English) and 'DE' (German), add approximately 1 hour. In the A_off strategy the import period is during the downtime, whereas in the A_on and A_switch strategies half of the import is while the system is operating productively, and half during downtime.
Example Schedule for Strategy A_switch Day Time Actions

Thursday Thursday

9:00 10:00

Start R3up Start import of the substitution set (slow) with R3up in phase EU_IMPORT0 Insert the last CD (title: Upgrade CD5) at the beginning of phase EU_IMPORT5 Stop production operation at the beginning of phase MODPROF_TRANS by isolating the central instance, as described under Isolating the Central Instance. Adjust modifications, if required. Back up database offline System in production operation

Thursday

19:00

Friday

20:00

Friday Saturday Saturday

23:00 9:00 After offline backup has been completed

Example Schedule for Strategy A_on Day Time Actions

Thursday Thursday

9:00 10:00

Start R3up Start import of the substitution set (slow) with R3up in phase EU_IMPORT0

34

April 2001

if required. Start the import of the substitution set with R3up Friday 17:00 Insert the last CD (title: Upgrade CD5) at the beginning of phase EU_IMPORT5 Adjust modifications. as described under Isolating the Central Instance. Adjust modifications. Start post-upgrade activities Back up the database online Friday 20:00 Friday Saturday Saturday 22:30 10:00 After starting to operate the system productively Example Schedule for Strategy A_off Day Time Actions Friday Friday 15:00 16:00 Start R3up Stop production operation at the beginning of phase EU_IMPORT0 by isolating the central instance. if required.6C Support Release 2: UNIX Thursday 19:00 Insert the last CD (title: Upgrade CD5) at the beginning of phase EU_IMPORT5 Stop production operation at the beginning of phase MODPROF_TRANS by isolating the central instance. Start post-upgrade activities Back up database offline Friday Saturday Saturday 21:00 9:00 April 2001 35 .SAP AG Upgrading to 4. as described under Isolating the Central Instance.

Only this SAP System offers you optimal support when you adjust modifications. you must proceed with the upgrades in the above sequence. Use this procedure to avoid making time-consuming adjustments in the production system. Development system 2. Quality assurance system 3. make sure that your development system remains in existence. If you have modified SAP objects. Process Flow If you have a development system and a production system. upgrade your systems as follows: 1. Production system If you have made modifications to SAP objects that you want to retain. Development system 2. To test the upgrade with realistic production data. Production system If your system group consists of three SAP Systems and includes a quality assurance system that has been set up between the development and production system. Do not copy your production system to your development system to test the upgrade. set up a quality assurance system between the development system and production system.Upgrading to 4. for example a production system and a development system. The version management functions of the SAP System only record all the changes you make in the system in which you made them (the development system). Changes made in the development system after the upgrade can be transported automatically to your other SAP Systems. This system can be a copy of the production system. upgrade the systems as follows: 1. 36 April 2001 . you must consider the entire system group when you upgrade.6C Support Release 2: UNIX SAP AG Upgrading in an SAP System Group Purpose If you have more than one SAP System. You should upgrade your systems in the same sequence in which you transport your modifications.

You can identify modifications as repairs to the SAP standard or as imports of SAP objects. For more information. which you should obtain before upgrading. If the development system contains more modifications.Basis Components →ABAP Workbench → BC . you can skip this section. The modification adjustment lets you make your modifications to the appropriate new objects in the upgrade. the error message TG140 appears in phase RUN_RDDIT006. All other requests are dealt with as preliminary corrections. then contact an experienced Basis consultant for help. Process Flow Adjusting Modifications in the First System (Development System) You must test the modification adjustment in a development system that has the same SAP Release and that has been modified to the same extent as the production system. April 2001 37 . To safeguard existing modifications of this kind. Release 4. Requests in the customer namespace (number range 900000 to 999999) “modify” the SAP objects included in them. including Support Packages. During the Repository Switch.x Choose Help → R/3 library → BC .Basis Components → ABAP/4 Development Workbench → Enhancements to the SAP Standard → The SAP Software Change Registration Procedure (SSCR). you lose any modifications you made to objects that conflict with SAP modifications. the modifications have to be preliminary corrections. Objects belonging to the central Basis component are always returned to the SAP standard by the Repository Switch.Changing the SAP Standard → The SAP Software Change Registration Procedure (SSCR). you might need an SSCR key.6C Support Release 2: UNIX Planning the Modification Adjustment Purpose If you are sure that your SAP System corresponds exactly to the SAP standard. otherwise the SAP System would not be able to operate.SAP AG Upgrading to 4. a distinction is made between the following two classes of modification: • • Modification to an object from the central SAP Basis component Modification to an application object In the first case. Prerequisites To adjust modifications. see the SAP online documentation.x Choose Help → SAP Library → BC . When you upgrade the system. Any preliminary corrections that you have imported as transport requests from one of the sapserv(x) SAP Support Servers may be lost when you upgrade. Release 3. The following explanation assumes that the levels of modification are identical.

You can read documents on the 4. You must consult the authors of the modifications named in the log UMODPROT.6C Support Release 2: UNIX SAP AG 1. the upgrade will import changes which previously did not exist in the system. modified version is still available in the versions database. to get background information on the changes made. Adjusting Modifications in Subsequent Systems For the quality assurance and production system. screens. data elements. If you have not installed a central transport directory. instead it must be flagged for export in Transaction SPDD. This phase is executed in the PREPARE module Modification support and runs in the upgrade between the import of the substitution set and the end of the production period. you automatically transfer both the transport requests exported in the section Adjusting Modifications in the First System (Development System). If you confirm here. In the ADJUSTPRP phase you are presented with the requests from the development system and can decide whether you want to accept them. The adjusted objects are collected in a repair that is released to a transport request. all adjustments are released to a transport request that is noted and then exported and registered by R3up.<SID> in the sub-directory log of your upgrade directory. domains.6C documentation CD offline. If this is the case. A check is performed to see if all the modifications identified in the system are handled by transport requests. You can find a detailed description of modification adjustment in the current online documentation under Help → SAP Library → Basis Components → ABAP Workbench → Changing the SAP Standard (BC) → The Modification Assistant. 2. These steps are described in Note 51046. The procedure is described on the cover of the CD. and so on) are adjusted during downtime before the activation of the ABAP Dictionary. you must perform additional steps for automatic acceptance. However. Repository objects (reports. and so on) are adjusted towards the end of the upgrade. The ABAP Dictionary objects (tables. The list of objects that have to be adjusted in your SAP System is determined in the ADJUSTPRP phase. the transport requests are integrated into the upgrade.lst.Upgrading to 4. R3up exports this transport request into the transport directory /usr/sap/trans (UNIX) or \\$(SAPGLOBALHOST)\SAPMNT\TRANS (Windows NT). 38 April 2001 . 3. You cannot release this transport request. before you upgrade the system. the old. we recommend that instead of adjusting modifications manually. As with Dictionary objects. If the number of objects in the adjustment transport requests exceeds the number of modifications in the next system. and then registers it for transport in the file umodauto. no adjustment needs to take place. Towards the end of the upgrade. At this stage the import of SAP objects has already been completed.

logging on with an old version of SAP GUI may cause errors. Preparations Processing Post-upgrade Receive the software package R3up starts Downtime begins Phase R3up KX_SWITCH ends The frontend software is upgraded directly from CD or from a file server. For more information. The latest possible time for upgrading is before you log on to the new version of the SAP System for the first time. The new SAP kernel is imported by R3up in the KX_SWITCH phase. You can import the frontend software as soon as you receive the software package.SAP AG Upgrading to 4. see the SAP Frontend Installation Guide. This graphic shows the time period during which you can upgrade the frontend software: Time Frame for Upgrading the Frontend Software Earliest possible time Production operation Downtime As of this point.6C Support Release 2: UNIX Time Frame for Upgrading the Frontend Software The new SAP release cannot run until the new version of the frontend software (SAP GUI) has been installed. After this has taken place. log on only with new frontend software Production op. April 2001 39 .

There are separate SAP Notes for the database-specific sections. which give you additional information. This information is kept in a number of SAPNet – R/3 Frontend Notes. You must read the general Upgrade Note before you prepare the upgrade. you are asked to enter a keyword. you require some additional information. The following is a list of these SAP Notes. this documentation also refers you to other SAP Notes.6C Support Release 2: UNIX SAP AG Notes for the Upgrade Definition To prepare and perform the upgrade of your system. This SAP Note contains current non-database-specific information on preparing for the upgrade.Upgrading to 4. which you can get from the current general Upgrade Note 390062. use the fax request form included in the software package. These SAP Notes are named at the appropriate places in this documentation. not included in the documentation. Other SAP Notes As well as the SAP Notes you need for preparing the upgrade. When you actually upgrade the system you need the information from some additional SAP Notes. SAP Notes for Preparing the Upgrade You must request the general Upgrade Note and the SAP Note for your database from SAPNet – R/3 Frontend before you start your upgrade. You cannot start the upgrade until you have entered the keyword. If you do not have a SAPNet link. The following is a list of the SAP Notes you need to prepare for the upgrade: SAP Note Number Database SAP Note Type 390062 197901 202790 386570 326658 201874 All databases SAP DB DB2 Universal Database DB2 for OS/390 Informix Oracle Specific to this upgrade SAP DB-specific / specific to this upgrade DB2 Universal Database-specific / specific to this upgrade DB2-for-OS/390-specific / specific to this upgrade Informix-specific / specific to this upgrade Oracle-specific / specific to this upgrade Keyword for the Upgrade When you start the upgrade. organized by database: 40 April 2001 . if necessary.

R/3-Frontend Central Basis objects are modified Correction locks do not belong to system Copying the modification adjustment without a central transport directory Error message TG063 in the upgrade phase JOB_RADDRCHK Conversion of address tables.0B Preliminary information on freespace in the database System requirements for frontend workplaces / SAP GUI Installation of a 3.6B Resource requirements for Release 4.1I Kernel Release SAP Releases for SAP add-ons (IS) Collection of notes on upgrade problems for the SAP component HR (human resources) Measures for optimizing upgrade runtime 4.SAP AG Upgrading to 4. runtime No conversion of table BSEG User buffer too small Installing a dialog instance/gateway with R3SETUP Performance Performance Performance Performance Performance Specific to this upgrade Frontend/SAP GUI SAP Kernel IS-specific HR-specific Upgrade to Release 4.0A/4. runtime Conversion of address tables.x R/3 HR Support Packages SAP Support Packages Remote support for upgrade General upgrade Transport Organizer Change and Transport System ABAP Dictionary Address management Address management ABAP Dictionary / Phase PCON_<rel> User administration R/3 installation April 2001 41 .6C Support Release 2: UNIX SAP Notes for All Databases SAP Note Number Topic SAP Note Type 323263 178616 151508 113795 89305 203428 26417 102445 86985 156387 76431 73510 83458 125971 33888 62519 51046 96905 97032 82167 24864 10187 137478 Resource requirements for Release 4.6A Resource requirements for Release 4.6C Resource requirements for Release 4.5 Resource requirements for Release 4.x Problems when upgrading patched source releases Downloading Support Packages from the SAP Service Marketplace Service Connection Upgrade Assistant in SAPNet .

2.2 Back up the database SAP DB 7.6x SAP DB SAP DB database upgrade to 7.6C language import Space requirements for the 4.4/5 SAP DB-specific SAP DB-specific SAP DB-specific SAP DB-specific SAP DB-specific SAP DB-specific SAP DB-specific SAP Notes for DB2 Universal Database SAP Note Number Topic SAP Note Type 156553 Released operating systems for 4.1 SAP DB load with parallel R3LOADS Change a database parameter in SAP DB Release 7.2 New software structure as of SAP DB Version 7.2.6C Support Release 2: UNIX SAP AG 197746 86627 98752 195443 195446 195442 322982 73999 177680 Maintenance Strategy Internet Transaction Server Transaction types: Customizing for release upgrades Migrating the proposal pool Current SAP Note on the 4.5 B00 Add Devspace under SAP DB (ADABAS for R/3) 6.Upgrading to 4.6x DB2 UDB DB2 Universal Databasespecific 42 April 2001 .6C language import Language import and Support Packages Install language during upgrade Upgrade phase PCON: TG450 to TG453 Correcting conversion problems during the PCON 46B / PCON 46C phase SAP@Web Customizing Translation tools Language transport Language transport Language transport Language transport General upgrade General upgrade SAP Notes for SAP DB SAP Note Number Topic SAP Note Type 156551 382741 34690 46430 201388 201390 327578 Released operating systems for 4.

6B) DB2/390: Free space for 4.6x Oracle Changing the storage parameters NEXT and MAX EXTENTS Oracle .SAP AG Upgrading to 4.6x Informix Reorganization of tables and dbspaces Informix Client versions Informix-specific Informix-specific Informix-specific Informix-specific SAP Notes for Oracle SAP Note Number Topic SAP Note Type 156548 11777 16951 303238 Released operating systems for 4.6A.1I. 3.1H. ICLI servers DB2/390: Manual saposcol installation DB2/390: DDIC corrections (3.0F.6x DB2/390 DB2/390: APAR list Conversion of partitioned tables SQL error -540 Maintaining catalog statistics DB2/390: Upgrade. 4. 3.6C Support Release 2: UNIX SAP Notes for DB2 for OS/390 SAP Note Number Topic SAP Note Type 156554 81737 78354 83473 113008 136806 103135 162250 162818 184399 197772 Released operating systems for 4.5A.Problems with Rollback segments Installation of the Oracle Client Software Oracle-specific Oracle-specific Oracle-specific Oracle-specific April 2001 43 . 4.0B) DB2/390: DDIC corrections (4.6C upgrade DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific ABAP Dictionary / phase CNV_SUBMIT DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific DB2 for OS/390-specific SAP Notes for Informix SAP Note Number Topic SAP Note Type 50157 156549 22941 115619 Using recommended versions of Informix Released operating systems for 4. 4.5B) DB2/390: DDIC corrections (4.

If you have made modifications to the SAP standard. Check the profile parameter rdisp/mshost. you can check the structural requirements using the following procedure. • Update processes must run on the central instance when you make modifications to the standard. The profile parameters for this server are displayed with their values. because only the central instance runs during downtime. For this reason. Procedure 1. 4.Upgrading to 4. Therefore. It must run on the same host as the central instance. while the secondary instances are stopped. versions of the modified objects are created by Version Management during the upgrade. You can only guarantee this if the message server is located on the same host as the central instance. If you are not sure whether you have a standard installation. This parameter displays the number of update processes for the central instance. This parameter contains the host name where the message server is running. A standard installation meets the specified structural requirements. Call Transaction RZ10. the upgrade control program R3up uses Remote Function Call (RFC) to call function modules. 44 April 2001 . the message server must still be running after the secondary instances are stopped. The update program writes these versions.6C Support Release 2: UNIX SAP AG Checking Structural Requirements Use You must meet the following structural requirements before you upgrade your system: • The message server must run on the host with the central instance. the update program must be running on the central instance. check the profile parameter rdisp/wp_no_vb. Choose Goto → Profile values → Of a server. During the upgrade. The number must be greater than 0. 2. Choose the server (host) where the central instance is running. and temporarily schedules ABAP report programs for background processing. 3. If you have made changes to the SAP standard. This makes sure that the message server is active during downtime.

• SAP Note 323263 This Note explains the resource requirements for Release 4. Approximately 6.0B compared to Release 3. SAP Note 89305 This Note explains the resource requirements for Release 4.0A/4. disk space.5B.0B.6C Support Release 2: UNIX Checking Hardware Requirements CPU.OS Dependencies. Space Requirements in the Database SAP DB You require a maximum of 8 GB of space in the database for the upgrade.650 MB of temporary disk space in the file system for the upgrade. main memory. see the documentation SAP Software on UNIX . and Swap Space Before the upgrade. Space Requirements in the File System Make sure that you have about 1.sap. The difference between the maximum disk space requirements and the permanent disk space requirements is available as free space in the database as soon as the upgrade is complete.4 GB of this amount is filled permanently. You need this free space to create the upgrade directory. You can use the following to help you: • Quick Sizing in the SAP Service Marketplace This is an interactive tool for an approximate sizing of the required hardware.5x compared to Release 4. For more information. You can free space after the upgrade by deleting the substitution tablespaces of the source release. Main Memory. check whether you have enough hardware resources. such as CPU. DB2 Universal Database The database is extended by a maximum of 9 GB. DB2 for OS/390 April 2001 45 .SAP AG Upgrading to 4. • • SAP Note 113795 This Note explains the resource requirements for Release 4.com/quicksizing. of which approximately 5 GB is filled permanently. UNIX Kernel Parameters You may need different values for the UNIX kernel parameters for a new SAP Release.x. and swap space.6C SR2 compared to Release 4. You can find it at: http://service.

The space requirements could be higher. Oracle Make sure that the following amount of free space exists in the database. depending on how much data you have. If you cannot start PREPARE early enough.0x/3.1x 4. End of the database-specific explanations The PREPARE program gives you information on how much free space is needed in the database.0B 4. Approximately 7 GB of this amount is filled permanently. you can find the maximum free space requirements for the database in SAP Note 203428. You can recover the difference between the minimum disk space requirements and the permanent disk space requirements by deleting the old substitution tablespaces.5 GB The space requirements could be higher. PREPARE takes the status of your database into account and calculates the exact space requirements. Informix The database is extended by at least 13 GB.Upgrading to 4. 46 April 2001 . depending on how much data you have.5B 13 GB 11 GB 10 GB 9 GB 7 GB 6. You can recover the difference between the maximum disk space requirements and the permanent disk space requirements by deleting the old substitution dbspaces.6C Support Release 2: UNIX SAP AG SAP Note 197772 describes the free space requirements in the database. depending on the source release: Space Requirements in the Database Source Release Minimum Free Space for the Upgrade Space Filled Permanently 3. You can free space after the upgrade by deleting tablespaces that contain only substitution tables of your source release.

Release 3.6A 4. Meet the requirements for the Upgrade Assistant [Page 48]. Oracle and SAP DB 3.0B 4.5B 4. 2. April 2001 47 . Meet the operating system-specific requirements [Page 49].0B 4.1I 4.6A 4.0F 3.1H 3. 3.0D 3.6x The release is displayed in the field Component version. Checking the SAP Source Release Prerequisites Depending on the database system.5B 4.6C Support Release 2: UNIX Checking Software Requirements Use You must meet certain software requirements before you upgrade the SAP System. Release 4. choose System → Status.1H 3. your SAP System must have one of the following releases: Informix.0F 3.6B End of the database-specific explanations Procedure To find out the release of your SAP System. Procedure 1.x – 4.6B DB2 Universal Database and DB2 for OS/390 3.1I 4.5x The release appears in the SAP Release field. Check the SAP source release [Page 47].SAP AG Upgrading to 4.

At present.sun. Java Virtual Machine The Upgrade Assistant (server and GUI) is implemented in Java. SAP supports the following browsers: − − • Microsoft Internet Explorer as of Version 4. If you have any doubts. find out about the status of the Java porting for your operating system from your Competence Center or with the following Internet URL of Sun Microsystems Inc.6C Support Release 2: UNIX SAP AG Meeting the Requirements for the Upgrade Assistant Network If you do not operate the GUI and server on the same host.exe) by double-clicking it and make the installation.: http://java.4 or higher) Microsoft SDK for Java (Microsoft Virtual Machine) You can use this variant for Windows and Windows NT.1x or preferably higher). The prerequisite for the installation is Windows NT 4. Open the file msjavx86.1. This means that the browsers can only be used to execute the GUI and not the server.exe (DEC-ALPHA msjavaxp.com/cgi-bin/java-ports.7231x Netscape Communicator as of Version 4. SAP delivers a Microsoft Virtual Machine on the CD SAP KERNEL NT. Windows NT For Windows NT hosts. End of Windows NT 48 April 2001 . This means that it requires a Microsoft Virtual Machine for execution (Version 1.04 (Java AWT 1. You can also use a Java Development Kit (JDK) that contains the JRE.cgi Procedure You can provide the Java Virtual Machine in several ways: • Java Runtime Environment (JRE) There is porting for all relevant platforms.0. you must be able to set up a TCP/IP connection between the GUI host and the server host. Open the Windows NT Explorer and switch to the directory <CD_DRIVE>\NT\I386 (DEC-ALPHA: <CD_DRIVE>\NT\ALPHA). Service Pack 3. • Internet Browser with integrated Java Virtual Machine Strict security rules apply to the execution of Java programs in Internet browsers. Installation: Insert the CD SAP KERNEL NT into the CD drive. Restart your computer.Upgrading to 4.

contact your IBM or Bull Competence Center. Check this using the following UNIX command: pkginfo -l CDS++RTS If necessary. End of the operating system-specific explanations April 2001 49 .SAP AG Upgrading to 4.0 A00 or higher.Z.tar. you can install this software from the CD-ROM CD-DEV-MI. ReliantUNIX You must install the runtime system ReliantUNIX C++ Runtime System Version 2. Check this using the following UNIX command: lslpp -l | grep perfagent If you have any questions. The compressed file is called CDS_PL_PLRTS_NYMS_1_0C32.6C Support Release 2: UNIX Meeting the Operating System-Specific Requirements Procedure AIX You must install the AIX packet perfagent so that the SAP Performance Monitor can function. or which you can order from your technical consultant. which you received with your computer.

SAP Library offline before the upgrade.pdf or Onldoc_e.htm. If you are upgrading from a 4. You first have to choose Help → SAP Library. you can find most of the documentation online in the system before and during your upgrade to the new release.Upgrading to 4. However.x Release. you can make sure that you can read the CD Online Documentation . you can use the same paths to find the documents online in the SAP System. The documentation is not available online in your system until you have completed the upgrade and the installation procedure for the online documentation (SAP Library).SAP Library (for example.6C documentation from the CD Online Documentation . to modify adjustments).SAP Library CD in the file Onldoc_e.6C Support Release 2: UNIX SAP AG Accessing Documentation Before and During the Upgrade Use Before and during the upgrade you require 4. After the installation. This upgrade documentation includes the paths to specific information in the appropriate sections. Procedure The instructions for installing the documentation are on the Online Documentation . 50 April 2001 .

If you want to modify Internet application components delivered in the standard system. you overwrite the application component objects (IAC objects) that are in the Support Packages included in the upgrade. you can also install the development environment of the ITS. If you are already using the ITS and the SAP@Web Studio. April 2001 51 . The report IAC_PUBLISH_SP publishes the current version in the corresponding directories of the ITS.6C. 3. Execute the report IAC_PUBLISH_SP directly after installing the ITS. Read SAP Note 197746 to see if newer versions of the ITS and SAP@Web Studio are available. Prerequisites These prerequisites and the upgrade of customer-specific Internet application components are described in the guide SAP@Web Installation. Install the ITS and SAP@Web Studio as described in the SAP@Web Installation Guide. the SAP@Web Studio. you must install the SAP Internet Transaction Server (ITS). If you install the ITS at a later time.SAP AG Upgrading to 4.6C Support Release 2: UNIX Meeting the Requirements for the SAP Internet Solution Use To use the SAP Internet Solution. Execute the report IAC_PUBLISH_SP if you install the ITS later. Procedure 1. We recommend waiting until after the upgrade before you install the ITS and SAP@Web Studio. The IAC Object Receiver (IACOR) must be installed for the report to execute successfully. you must reinstall this software in connection with an upgrade to Release 4. 2.

For more information about this procedure. This is the case if you did not include any additional Support Packages in the upgrade. You cannot install any new languages during the upgrade.Upgrading to 4. However. SAP recommends that you only use this option if the system contains the Support Packages for the language CD you are using. see SAP Note 195442. 52 April 2001 . you do have the option of classifying new languages in the SAP System before the upgrade with transaction SMLT. For more information. see SAP Note 322982. The upgrade procedure itself only offers to update existing languages. If you intend to use additional languages in your system in the future. or did not import any additional Support Packages after the upgrade. or Support Packages you need to import after the upgrade.6C Support Release 2: UNIX SAP AG Importing Additional Languages After the upgrade you have the option of importing new languages into the SAP System. and importing them during the upgrade. Importing new languages during an upgrade is a highly efficient process. and is preferable to importing a language into a live system after an upgrade. import them during the upgrade. In this way you can avoid any sequencing problems arising from Support Packages included in the upgrade.

SAP AG Upgrading to 4. Proceed as follows: 1. you may have to update your operating system and database to a new version. April 2001 53 . Start PREPARE and analyze the results. If necessary. For information on which versions have been released. All strategies are supported (A_switch. The procedure differs according to the database you use. Upgrade the system with your choice of upgrade strategy. When you import the 7. Start PREPARE and analyze the results. exit it.sap.2.6x Informix 156548 Released Operating Systems R/3 4. update the SAP DB release.4x (or higher) database software. see the SAP Service Marketplace under: http://service. Migrate the database to Version 6 if you have not already done so.000 for Release 4.5. or migrate a database. A_on and A_off). 2.6C Support Release 2: UNIX Upgrading the Operating System and Database System: Overview Purpose When you upgrade the SAP System. then the timing and the sequence of the individual upgrades is of great importance. 5. 2.6x DB2/390 156549 Released Operating Systems R/3 4. DB2 Universal Database Proceed as follows: 1. see the following SAP Notes: 156551 Released Operating Systems R/3 4.2.6x DB2 UDB 156554 Released Operating Systems R/3 4.6C on SAP DB.6x SAP DB 156553 Released Operating Systems R/3 4. We have described the process flows specifically for each database in this section.com/dbosplatforms If you need to upgrade an operating system or database. you change the structure of the SAP DB software. 3. For more information. Repeat the PREPARE module General checks to run through the CONFCHK phase once more and if the module ran successfully. 4. The migration guide is a PDF document on the software CD that contains Version 6 of the database. Process Flow SAP DB You require at least Version 7.6x Oracle For more information. If you have not already done so. upgrade the operating system. as described in SAP Note 382741. see SAP Note 327578.

Upgrading to 4. Stored Procedures: 162250 162818 184399 As of Release 4. A_on and A_off).0. Depending on your source release.SFOMDATA <HLQ>. ICLI: The first time you start PREPARE. Database version: DB2 Version 6. DB2 for OS/390 Make sure that you meet the following requirements before you start PREPARE for the first time: 1. A PTF Check Tool is available for all source releases. 6. For more information. stored procedures are used for DB2 for OS/390. All strategies are supported (A_switch. 54 April 2001 . Upgrade the system with your choice of upgrade strategy. The import of the current downward-compatible SAP Kernel is described in SAP Note 102445. 3.5A.8 or higher. The ICLI software is delivered using PTF.3. Operating system of the application server: AIX Version 4.2 or higher.1I.1H. Current downward-compatible SAP Kernel and required transports for source release Make sure that all required transports and the minimum required patch level of the current downward-compatible SAP Kernel for the source release have been imported into your system.6C ICLI server is started for the upgrade tools alongside the ICLI server of the source release.LINKLIB <HLQ> is identical for all three data sets and its default value is SYS1. Operating system of the database server: OS/390 Version 2. The ICLI software must be in the following three data sets after you have installed the PTFs: <HLQ>. a 4.5B 4. Any missing PTFs can lengthen the runtime of the upgrade significantly. 3.0F. 4.1.6A.6B. the transports.SAMPLIB <HLQ>. This tool is described in SAP Note 183311. The prerequisites and preparations are described in the SAP R/3 on DB2 for OS/390 Planning Guide. You must install this before you start PREPARE for the first time. 4. the release and the minimum required patch level of the Kernel are described in one of the following SAP Notes: Source Release SAP Note Number 3. 5.6B 7. 4. 3. 4. Required PTFs and APARs: SAP Note 81737 (APAR list) contains information on the PTFs that you need to import before the upgrade. 2.0B 4. see SAP Notes 81737 and 136806 and the IBM documentation SAP R/3 on DB2 for OS/390: Planning Guide.6C Support Release 2: UNIX SAP AG 3.

The import is described in SAP Note 102445. see SAP Note 326658.6C Support Release 2: UNIX Informix For information on which version of the Informix Dynamic Server you need for this release.1I Kernel.SAP AG Upgrading to 4. A_on and A_off). If you change to HP-UX 11 between executing PREPARE and starting the upgrade.0x/3. upgrade the operating system. instead use the Version 7. Also use the CD SAP KERNEL from the 3.1x: If you have not done so. If necessary. 3. 2. 5. 4.0x/3. upgrade Informix as described in the guide Installing Version 7. 3. see SAP Note 156548. Import the current Kernel patches. This is currently the 3. All strategies are supported (A_switch. You require at least patch level 3 of the 3. Do not import the Informix version that was mentioned in the notes for the 3. import the current downwardcompatible SAP Kernel (DCK).31 as described in the next step.1I Kernel. If you have not done so. Source Release 3. 2. Oracle Version 8. Proceed as follows: 1.31 of the Informix Dynamic Servers: UNIX. This is currently the 3. since older versions contain errors that cause problems in PREPARE.1I upgrade package that has already been sent to you.1I upgrade package that has already been sent to you. upgrade the operating system. If necessary. Upgrade the system with your choice of upgrade strategy. HP-UX Depending on whether you have Version HP-UX 10 or HP-UX 11. exit it.6 is required for Release 4. import the current downwardcompatible SAP Kernel (DCK). Proceed as follows: 1. April 2001 55 .1I DCK. Start PREPARE and analyze the results. then you need to disassemble the SAP Kernel from the CD again. Start PREPARE and analyze the results. The import is described in SAP Note 102445. before you start the upgrade. For more precise information on the combination you use. Source Release 3.1I Kernel. PREPARE disassembles the correct SAP Kernel and copies it to the directory /put/exe.1x: If you have not done so. 6.0. Also use the CD SAP KERNEL from the 3. since older versions contain errors that cause problems in PREPARE. Repeat the PREPARE module General checks to run through the CONFCHK phase once more and if the module ran successfully.6C on Oracle for the majority of operating systems at the time of going to print.

exit it.0. migrate Oracle as described in the guide Migrating/Upgrading to Oracle Version 8. If you have not already done so. A_on and A_off).6C Support Release 2: UNIX SAP AG The exact procedure is described in the section Starting the Upgrade [Page 107]. Repeat the PREPARE module General checks to run through the CONFCHK phase once more and if the module ran successfully. All strategies are supported (A_switch.Upgrading to 4. 5. 6. End of the database-specific explanations 56 April 2001 . End of HP-UX 4. Upgrade the system with your choice of upgrade strategy.6: UNIX.

Start PREPARE as soon as possible before the upgrade so that you can initiate or perform the necessary preparations in time. The information required in the Initialization module [Page 80] is specific to DB2 for OS/390. b. a.x. If you need extra software after starting PREPARE. for example. For information on using the Upgrade Assistant. if the results from its first run make you want to repeat some checks. f. followed by the Upgrade Assistant GUI [Page 68]. You first start PREPARE [Page 66] from the CD. you must check the version of the SAP Kernel and substitute it [Page 63] if necessary. you can execute it directly. a. April 2001 57 . 3. In the Parameter Input module [Page 75]. You use the Upgrade Assistant to start the PREPARE program. 2. you must check the SAP programs [Page 64]. First you start the Upgrade Assistant server [Page 67]. see Using the Upgrade Assistant [Page 241]. You create an upgrade directory [Page 60]. see PREPARE Phase List [Page 214].x. import it now [Page 74]. Perform the user actions needed during PREPARE. You determine a host for the upgrade preparations [Page 59]. b.SAP AG Upgrading to 4. c. b. If you have Source Release 3. if you want to use it for another system.6C Support Release 2: UNIX Upgrade Preparations Purpose You can prepare for the upgrade while the system is operating productively. You can reset PREPARE [Page 73] at any time. For a complete list of all PREPARE modules and phases. c. Process Flow 1. and finally the Upgrade Assistant [Page 69] itself. Careful preparation of the upgrade is the best guarantee that it will run without errors. The PREPARE program supports you here by making most of the necessary checks automatically. If you have Source Release 4. PREPARE requires you to make certain entries for its individual modules so that it can run. You check the database-specific requirements [Page 62]. If you want to restart PREPARE [Page 72]. you need to provide information about the name of the SAP System or the central SAP server. for example. Prerequisites You have completed the planning of the upgrade. You perform the user actions needed before starting PREPARE. d. You make sure that there are 500 MB of freespace in the database for PREPARE. a. e.

you back up the database. b. You perform the user actions needed before starting the upgrade. you read the results [Page 87] in the log file CHECKS. for example. you check the user for the upgrade. Among other things. 4. Result Once you have made all the preparations. You make preparations at the database level [Page 95]. you back up the SAP Kernel. the language CD is mounted and the Support Packages are included in the Read CD module [Page 82]. for example. d. for example. After PREPARE has run. default values appear that you can confirm or change. 58 April 2001 . c. a. You make preparations at the system level [Page 98].LOG. You make preparations at the operating system level [Page 94]. If possible. or you check the requirements for the modification adjustment.6C Support Release 2: UNIX SAP AG c. you can begin the upgrade.Upgrading to 4.

you may later also need or want to use your database host or another host. Depending on your configuration. • Database host You must perform the actions that affect the database on the database host. see Preparations at the Database Level. For a description of these actions.SAP AG Upgrading to 4. April 2001 59 .6C Support Release 2: UNIX Determining the Host for the Upgrade Preparation Use You need to prepare for the upgrade on the host with the central instance. Procedure Decide which hosts you need for the upgrade preparation and the actual upgrade of the SAP System: • Host with the central instance You must execute the upgrade process and PREPARE on the host where the central instance is running. • Other hosts The graphical user interfaces (GUIs) provided by the Upgrade Assistant can run on any hosts that meet the necessary requirements. The Upgrade Assistant server also runs on this host.

and it is divided into the subdirectories data. You also require an additional 300 MB in the upgrade directory for each language other than English or German. depending on your database and source release. exe. This space is required for the upgrade and the logs. you also need to make these directories larger. The upgrade directory is required by the PREPARE program before the actual upgrade. which can be a softlink to another physical directory. log and other subdirectories in the upgrade directory. you can also give it a different name.6C Support Release 2: UNIX SAP AG Creating the Upgrade Directory Use The system is upgraded using the upgrade directory. if systems include extensive own developments or large amounts of individual documentation. 60 April 2001 . however. chgrp sapsys .650 MB In the Repository Switch. there are dynamic percentages in the subdirectories data and log in the upgrade directory. chmod 755 . since it copies data and programs into the directory Prerequisites The upgrade directory must be installed on the host with the central instance. For more information see Using a Different Upgrade Directory [Page 207]. This may vary by up to 25%. These directories can also be softlinks. Ensure that the SAP profile parameter DIR_PUT in the instance profile of the central instance has the value <upgrade directory>. Procedure If the upgrade directory does not yet exist. If you want to include Support Packages and add-ons in the upgrade. We recommend that you create the directory with more space than specified in the table above. The standard path for the upgrade directory is /usr/sap/put. You need free disk space for the upgrade directory on the host with the central instance.Upgrading to 4. The following table shows the sizes of these directories. Disk Space Requirements in the Subdirectories of the Upgrade Directory data 700 MB exe 250 MB log 300 MB Remaining 400 MB Total 1. user root must create it: mkdir <upgrade directory> cd <upgrade directory> chown <sapsid>adm .

To make any deletions.6C Support Release 2: UNIX The owner of the upgrade directory and of all the subdirectories must be the SAP system administrator <sapsid>adm. If softlinks to subdirectories were created. cd <upgrade directory> ls -ld * (for checking purposes) rm -rf * April 2001 61 . To delete these directories as well. log on as user <sapsid>adm. this deletes the links. the new upgrade the directory must exist. Copy any manually created directories before deletion if you want them to be kept. Switch to the upgrade directory and delete all the subdirectories. If it already exists.SAP AG Upgrading to 4. but not the contents of the directories referred to. you must delete the directories one by one and redefine the links. check whether it still contains data from the previous upgrade. Before you start. but be empty.

Informix Make sure that you have at least 200 MB of freespace available in the temporary dbspaces (TMPDBSx).6C Support Release 2: UNIX SAP AG Checking Database-Specific Prerequisites for PREPARE When you run PREPARE for Release 4. End of the database-specific explanations 62 April 2001 . PREPARE and R3up need the Oracle Client Software under a fixed path.Upgrading to 4.0. Install the software as described in Note 303238.5. Oracle If you already use database Version 8. you require at least the database versions released for the year 2000.6C.

PREPARE checks the Kernel version and prompts you to switch the SAP Kernel.LOG. Also read the section Upgrading the Operating System and Database System [Page 53]. since older versions contain errors that cause problems in PREPARE. Prerequisites You can combine a database upgrade with the import of the new Kernel. 2. Unpack the new Kernel. see SAP Note 102445.SAP AG Upgrading to 4.1I Kernel with patch level 3 before you start PREPARE. see the PREPARE log CHECKS. In the KRN_CHK_INI phase of the Initialization module.6C Support Release 2: UNIX Substituting the SAP Kernel (Source Release 3. 4. For more information. Stop all SAP programs.1I Kernel Version. 3. back up the existing kernel directory. Stop the services SAP<SAPSID>_<INSTANCES> and SAPOSCOL. For more information. Procedure Proceed as follows to substitute the SAP Kernel: 1. if necessary. The following PREPARE modules require a 3. Mount the Kernel CD. All files and subdirectories in /usr/sap/<SAPSID>/SYS/exe/run are overwritten when the kernel is switched. April 2001 63 . Before substituting the SAP Kernel.x) Use Make sure that you are using at least the 3.

Required Versions of the SAP Programs for 4.x) Use Make sure that the following programs meet the specified prerequisites in the SAP Kernel directory /usr/sap/<SAPSID>/sys/exe/run of your source release. • Finding out the version of tp in Release 4. The program displays the date and the version number.5B Call tp with the following command: tp -V The last line displays the highest patch level. • Finding out the version of the SAP Kernel Call the program disp+work with the following command: disp+work -V 64 April 2001 .Upgrading to 4.0B Database SAP Kernel tp R3trans DB2 Universal Database DB2 for OS/390 Informix ORACLE SAP DB DB2 Universal Database No special requirements No special requirements At least version from February 4th. 1999 40B_COM Kernel At least patch level 425 40B_COM Kernel No special requirements 40B_COM Kernel No special requirements Required Versions of the SAP Programs for 4. corresponding dbadaslib At least patch level 606 At least patch level 607 Procedure This enables you to find out the versions of the SAP Kernel programs: • Finding out the version of R3trans Call R3trans without options.5B DB2 Universal Database DB2 for OS/390 Informix ORACLE SAP DB No special requirements At least patch level 126 No special requirements At least patch level 573.6C Support Release 2: UNIX SAP AG Checking SAP Programs (Source Release 4.

0B Database Location DB2 Universal Database DB2 for OS/390 Informix ORACLE SAP DB DB2 Universal Database For R3trans: 4.5B All databases For tp: 4. Directory /<CD mount directory>/UNIX/<OS>/40B For the SAP Kernel: sapserv<X> Locations of the Correct Versions of SAP Kernel Programs for 4.6C Support Release 2: UNIX The last line displays the highest patch level.SAP AG Upgrading to 4. You can always find the correct versions of these SAP Kernel programs on the SAP Support Servers sapserv<X>.6C Kernel CD. Directory /<CD mount directory>/UNIX/<OS>/45B April 2001 65 . You can also use the following options to obtain these versions more quickly: Locations of the Correct Versions of SAP Kernel Programs for 4.6C Kernel CD.

We recommend that you use the Upgrade Assistant. see the section Executing PREPARE and R3up in Scroll Mode [Page 201]. Confirm the prompt of the display mode with the default EXIT. Log on to the Upgrade Assistant GUI as the administrator and restart PREPARE [Page 72]. This ends the program PREPARE.Upgrading to 4. Log on to the host on which the central instance is running as user <sapsid>adm. Mount the CD SAP Kernel. 2. Procedure 1. The necessary commands can be found in the specific chapters for the operating system in the manual SAP Software on UNIX . Make sure that the database and the SAP System have been started up. 66 April 2001 .OS Dependencies. Now start the Upgrade Assistant Server [Page 67].6C Support Release 2: UNIX SAP AG Starting PREPARE from the CD Prerequisites • • You have met the requirements for PREPARE. For information on how to activate scroll mode when you restart PREPARE. followed by the Upgrade Assistant GUI [Page 68]. You have made the met the database-specific requirements for PREPARE [Page 62]. enter SCROLL when you are prompted for the display mode. 5. 4. 3. If you want or have to run PREPARE in scroll mode. Enter the following commands: cd <upgrade directory> /<CD mount directory>/UNIX/PREPARE This creates a directory <upgrade directory>/ua into which the Upgrade Assistant is unpacked.

Open a new window at the operating system level as user <sapsid>adm: 2.jar UaServer April 2001 67 . This creates the subdirectory ua in the upgrade directory and disassembles the Upgrade Assistant in this directory. Enter the following command: jre -cp <upgrade_directory>/ua/ua.SAP AG Upgrading to 4. Procedure 1.6C Support Release 2: UNIX Starting the Upgrade Assistant Server Prerequisites You must start the program PREPARE once from the CD.

jar UaGui 68 April 2001 . hw1156.jar from the upgrade directory on this host to a directory <UaGuiDir> or mount it with NFS. Start the GUI as follows: jre -cp <UaGuiDir>/uagui. 2. So that the GUI can also be used on other hosts.6C Support Release 2: UNIX SAP AG Starting the Upgrade Assistant GUI Prerequisites The Upgrade Assistant server must be active [Page 67].sap-ag.jar UaGui Starting the GUI on Other UNIX Hosts 1. you must copy the file uagui. We recommend that you call the GUI from an Internet browser.html Replace <host name> with the name of the host on which the Upgrade Assistant is running.jar UaGui When using the Microsoft Virtual Machine: jview /cp <UaGuiDir>\uagui.jar from the directory <UpgDir>/ua on this host to any directory <UaGuiDir>. copy the file uagui. enter the following URL: http://<host_name>:4239/ua/UaGui. You need to enter the full Internet name. Start the GUI as follows: jre -cp <upgrade_directory>/ua/uagui. Starting the GUI from the Internet Browser To start the GUI from a browser.de. Use the following URL to display the contents of the upgrade directory: http://<host_name>:4239 Starting the GUI on Windows Hosts 1. Open a new window as user <sapsid>adm: 2. 2.wdf. for example.Upgrading to 4.jar UaGui Starting the GUI on UNIX Hosts Starting the GUI on the Host with the Central Instance 1. So that the GUI can also be executed on other hosts. Start the GUI in a command prompt as follows: When using the Java Runtime Environment (JRE): jre -cp <UaGuiDir>\uagui. The procedure depends on the host on which you are starting the GUI of the Upgrade Assistant.

SAP AG Upgrading to 4. 3.33 2.56. You see the following screen: April 2001 69 .202. Example of the format for the host name: hw1156 hw1156.6C Support Release 2: UNIX Starting the Upgrade Assistant Prerequisites The Upgrade Assistant and the Upgrade Assistant GUI are already started.de 155. In the field Host name.wdf. you can leave the field Host name empty. the following connect screen appears: 1. If you want to start the GUI and the server on the same host. Procedure If you did not start the GUI from an Internet browser.sap-ag. Do not change the default value 4241 in the field Port number. enter the name of the host where the central instance is running.

6C Support Release 2: UNIX SAP AG 4. 5.Upgrading to 4. the following window appears with the main menu: 70 April 2001 . In the field Password. In the fields User name / Phone number. enter your personal information. The initial passwords for the two roles are as follows: Role Initial Password admin observer Administrator Observer After logging on. you must enter a password that specifies if the GUI has the role of the administrator or the observer.

6C Support Release 2: UNIX April 2001 71 .SAP AG Upgrading to 4.

3. 72 April 2001 . Log on to the GUI.6C Support Release 2: UNIX SAP AG Restarting PREPARE from the Upgrade Assistant GUI 1. PREPARE must run through all mandatory modules before you start the actual upgrade. Make sure that the Upgrade Assistant server is active.Upgrading to 4. 2. some are optional. 4. Select Administrator → Start PREPARE. Some modules are mandatory. Start a GUI as described under Starting the Upgrade Assistant GUI. A successfully executed module has the status succeeded. You can select which modules you want PREPARE to run through on one of the following screens.

If you reset PREPARE between the phases mentioned above. but do not want to upgrade the system. Enter the following commands as user <sapsid>adm: cd <upgrade_directory>/bin R3up reset prepare 2.6C Support Release 2: UNIX Resetting PREPARE Use If you have already executed PREPARE more than once. If you have already triggered initialization in transaction ICNV. In the following cases.SAP AG Upgrading to 4. April 2001 73 . • Procedure 1. you can only reset PREPARE under certain conditions: • If PREPARE in the Import module is between the phases TOOLIMPD1 and NPREPCRE0. errors occur when you restart PREPARE. the command reset prepare does not reset these initializations. then you have to reset PREPARE. Delete the contents of the upgrade directory so that it has the same status it had the first time PREPARE was started [Page 66]. you must perform the remaining phases up to at least NPREPCRE0 before you reset PREPARE.

Upgrading to 4. Import the required software. Procedure 1. 2. 3. you may need to import software. or add-ons (and add-on updates). Reset PREPARE as described in the section Resetting PREPARE.6C Support Release 2: UNIX SAP AG Importing Software After Starting PREPARE Use After you start PREPARE. such as Support Packages. 74 April 2001 . languages. Start PREPARE again from the CD and repeat the required and optional modules.

You always have this option if the JCL job produces errors. Procedure The following parameters of your system are prompted (INITPUT phase): • • • • • • Name of the SAP System (<SAPSID>) Number of the instance. DB2 subsystem name Enter the name of the DB2 subsystem.SAP AG Upgrading to 4. Data set for LOAD library Enter the name of the data set that contains the LOAD library. The default name is ICLIRUN. 5. Default entries appear where possible. Data set for DSNTIAD library Enter the name of the data set that contains the DSNTIAD library. for example 00 Host name of the central SAP server Path to the SAP start and stop procedure (default is the home directory of user <sapsid>adm) Path to the active SAP Kernel Instance name of the database DB2 for OS/390 You are now prompted to make the following entries: 1. The name of the phase is given in parentheses to help you. JCL Submission Service test Make the following entries as part of the JCL Submission Service test: − − MESSAGECLASS TCP/IP name of the database host April 2001 75 . 3. 2. User who starts the ICLI server Enter the name of the user who starts the 4. These jobs can also run at night. 6. Here you have to decide whether you want the upgrade to stop before the JCL job is executed. Stop before execution of the JCL job Several JCL jobs are executed during PREPARE and the upgrade. see below. For a list of the necessary entries for this PREPARE module.6C ICLI server. Confirm or change the default entry. 4.6C Support Release 2: UNIX Making Entries for the Parameter Input Module Use PREPARE needs certain information from you so that it can run the Parameter Input module. so that you can make corrections to the job. in particular RUNSTATS during the table import.

End of DB2 for OS/390 • • Host name of the database server Mount directories for CDs If you have only one CD drive. saposcol and librfc) to OS/390 while PREPARE is running. 76 April 2001 . 9.6C ICLI server under this port number. in addition to the instance of the source release’s ICLI server. This instance is needed during the upgrade only. You can also use a job to start and stop the ICLI server (without any user action). Port number You are prompted to enter a port number for an instance of the 4. You are asked if you want to use this option. see SAP Note 136806. If you are working in scroll mode use ENTER to skip the prompts for extra mount directories.6C ICLI server you must enter the High Level Qualifier under which the 4. Whenever necessary. Stop and start the ICLI server for each job In the TABUIMP_BAS phase. you must stop the ICLI server of the source release and start the ICLI server of the target release. 8. If you confirm this prompt. If you confirm this option. High level qualifier for 4. R3up prompts you to specify a mount directory or to change the CD. For more information. You can stop it again after the upgrade. You are then prompted to start a 4. You can delete this directory after you complete the upgrade.Upgrading to 4. You can also install this software as described in SAP Note 103135.6C ICLI PTF was installed. you are asked to adjust the corresponding jobs. you do not have to enter any other mount directories. The OS/390 user (step 6) needs write and read authorization for this directory. SAP software components You are asked whether you want to import some SAP software components (rfcoscol. • Temporary upgrade directory on OpenEdition You must create this directory now. The OS/390 user (step 6) needs write and read authorization for this directory.6C Support Release 2: UNIX SAP AG − − OS/390 user Password of the OS/390 user 7. you need to make the following entries: • • Program ID Specifies the TCP/IP connection used by rfcoscol saposcol-/rfcoscol directory Directory in which saposcol and rfcoscol are installed.6C ICLI PTF As part of the installation of the 4. 10. You need at least 15 MB for this.6C ICLI servers.

you now have the chance to update the database statistics for tables and indexes. to import a new version of the database system. • Language key Enter E or D to define whether the help texts displayed by R3up in error situations appear in English or German. enter all the mount directories used. You can skip this step. • Number of parallel import processes The number of parallel processes used by R3trans to import data into the database. DB2 Universal Database • Update database statistics To avoid lock situations and any resulting problems during the upgrade. see the file README on the CD. For more information on using multiple CD drives. Add-Ons The other CDs in the upgrade package are not required by PREPARE or R3up.SAP AG Upgrading to 4.6C Support Release 2: UNIX If you have more than one CD drive or you are able to copy the contents of the CD to disk. PREPARE and R3up require the following CDs as well as the SAP Kernel CD: Additional CDs CD Title Upgrade CD1 Upgrade CD2 Upgrade CD3 Upgrade CD4 Upgrade CD5 Language Disc Optional CDs CD Title Language Disc for your chosen language Add-On CDs Contents Transport requests imported during the upgrade (PREPARE) Transport requests imported during the upgrade (PREPARE) ABAP loads and transport requests imported in the upgrade (PREPARE/R3up) Transport requests imported during the upgrade (R3up) Transport requests imported during the upgrade (R3up) Standard languages English and German (PREPARE/R3up) Contents Languages other than English and German For the exact contents. but by other programs within the upgrade. However. see Drawing Up an Upgrade Schedule [Page 32]. we only advise you to do this if: − − you update the statistics regularly you already generated statistics the last time you ran PREPARE April 2001 77 . We recommend the 3 processes for machines with 512 MB main memory. Up to 4 parallel import processes are possible for multiprocessor hosts with sufficient main memory. You can change your entries each time you run PREPARE or R3up. for example.

Long runtime. see the script startsap for the correct name of the start profile. In this case. If it is not correct. choose MEDIUM.PFL profile The DEFAULT. It meets the following naming conventions: START_<instance name><instance number>_<host name> START_DVEBMGS00_hsi027 Always check that the default value is correct. You can check this with transaction SM51. enter the host name and the name of the relevant application server. the background service may be elsewhere to improve load distribution. Also make sure that the upgrade directory is mounted on the host with the background service. You have the following options: MEDIUM HIGH = tables with cardinality = -1 or with cardinality = 0 (and any corresponding indexes) = all tables (and any corresponding indexes). • Path and name of the profile of the central instance The profile for the central instance is also in the directory /usr/sap/<SAPSID>/SYS/profile and usually uses the following naming convention: <SAPSID>_DVEBMGS<instance number>_<host name> You must check here whether your default value is correct. • Host name of the background server Normally a background service is available on the central instance. Password of user DDIC in the system. you have another opportunity to update the statistics. End of DB2 Universal Database • Name of the SAP start profile The SAP start profile is used in the SAP start procedure and is in the general profile directory /usr/sap/<SAPSID>/SYS/profile.Upgrading to 4. 78 April 2001 . client 000 This password is needed for the RFC connection to the system. If you do not know the state of the database statistics. • Path of the DEFAULT. change it. However. in larger systems. If in doubt.PFL can be found in directory /usr/sap/<SAPSID>/SYS/profile. If in doubt.6C Support Release 2: UNIX SAP AG At the beginning of R3up (actual upgrade). R3up asks you to verify the password by entering it a second time. and that the background server can process background jobs of class C. Check whether the password is correct by logging onto the system. see the start profile for the correct name.

in which users can make unchecked changes. The system logs are recreated the next time the system is started with the new release. For this reason. If you run the system with multiple application servers. Path to the EPS inbox The default value is proposed.SAP AG Upgrading to 4. April 2001 79 .x cannot read the system log of older releases since the format changed as of Release 4. • • Directory for the central system log See Directory for the local system log above. This action cannot be performed automatically. If you installed several instances.6C Support Release 2: UNIX The server you select must be available for background operations round the clock. you must manually rename the local system log of this remote server (see Renaming the Local System Log [Page 150]). • The greatest synchronization time of the buffers of all the application servers Usually. The SAP Kernel of Release 4. the local system log of the central instance and the central system log are renamed in a kernel substitution (KX_SWITCH phase). R3up must wait for this length of time at certain points during the upgrade so that all the instances are synchronized. it is important that the largest value of all the profiles is defined here.x. If the time entered is too short. time intervals might occur. 60 seconds is entered for the bufreftime parameter in the instance profiles of the servers. Check this value and correct it if necessary. • Directory for the local system log This is the local system log for the central instance. Check the active operation modes with transaction SM63 to find out if it satisfies this requirement.

pfl file contains the VSAM catalog ID and the disk ID. see Note 197772.pfl file does not exist when PREPARE starts. the stogroups needed for the database layout of the target release are created with the volumes defined in the file volumes. To do this.5A.6C Support Release 2: UNIX SAP AG Making Entries for the Initialization Module Procedure DB2 for OS/390 Depending on the source release. the disk ID. you have the option of inserting the volumes defined in the file volumes. R3up creates the following sample file volumes. The volumes.pfl into the existing stogroups of the source release database layout. and then adapt it to the local hardware configuration. The Database Administration Guide describes the new database layout for the target release. #-----------------------# FILE: VOLUMES. or extend existing stogroups.0B.smp.pfl in the sub-directory bin of the upgrade directory contains the following disk entries: # volume VOLUME-ID '*' The following is an example of a sample file for the SMS: 80 April 2001 .5B and later.Upgrading to 4.pfl into the existing stogroups of the source release database layout. you are prompted to create this file using the sample file volumes. The volumes. VOLIDs). The following lines contain information on the disks whose IDs are specified behind volume. You also have the option of inserting the volumes from volumes. The first line without comments contains the characters VCAT and the disk catalog ID. the file volumes. • For information on the amount of disk space needed in the database. you may need to create new stogroups in the database. For source releases 4. In the first SPACECHK phase. • For source releases up to and including 4. If the database uses disks managed by the Storage Management System (SMS). The database layout was changed in Release 4.smp in the sub-directory bin of the upgrade directory. you need information about the local hardware configuration (SMS/NON SMS.pfl .pfl to the sub-directory bin of the upgrade directory.SMP #-----------------------# VCAT-ID VCAT DSNOOE # VOLUME-ID volume DB2069 volume DB206A volume DB206B #------------------------ You must copy this volumes.

PFL #----------------------------# VCAT-ID VCAT DSNOOE # VOLUME-ID volume '*' #----------------------------- End of DB2 for OS/390 April 2001 81 .SAP AG Upgrading to 4.6C Support Release 2: UNIX #----------------------------# FILE: VOLUMES.

In principle. you are asked to insert the corresponding CD. you can exclude certain languages from the upgrade. you are prompted to make the relevant changes. Phase PATCH_CHK3 The system tests to see if all the Support Packages (previously known as Hot Packages. • Delete the add-on You can only choose this alternative if your add-on supplier has confirmed that this does not cause any problems.6C Support Release 2: UNIX SAP AG Making Entries for the Read CD Module Procedure Phase LANG_SELECT You are prompted to mount the language CD.0E and R3up is unable to determine a standard setting for the territory of your system. If you have not installed any add-ons. it is possible to install additional languages during the upgrade.Upgrading to 4. If you exclude a language. Phase IS_CHK You are asked if any add-ons are installed that are not automatically recognized. Phase LANG_CHK If you have a source release lower than 3. A password is required for this alternative. The standard languages are always imported. For more information. If you have installed languages other than the standard languages. and any add-ons that may have been added manually. You need to do this even if only the standard languages English and German are installed in your system. Phase IS_READ All add-ons appear that are found in the IS_CHK phase. Legal Change Patches) are confirmed. 82 April 2001 . you cannot work in this language after the upgrade. confirm the prompt with nothing else. The data is copied to the upgrade directory. The following alternatives are offered for each add-on: • Upgrade the component with the CD for the add-ons When you choose this alternative. • Keep the present version of the add-on Only choose this alternative if the vendor of your add-on has confirmed that you can do this without losing data. see Importing Additional Languages [Page 52].

see SAP Note 119738. If the source release contains Support Packages that are more recent than those in the delivered target release. you need a Package Key as of 4. then you need to do this in the next phase BIND_PATCH.LOG file in the log subdirectory of the upgrade directory. April 2001 83 . If you use SAP HR. As of Release 4. This means that your system is completely up-to-date after the upgrade.6.6C Support Release 1. and all released Basis Support Packages. we recommend that you always include all available Support Packages for the target release. For information on this and on other subjects.SAP AG Upgrading to 4. TABIM_46C and XPRAS_46C increases. ACT_46C.6C Support Release 2: UNIX Unconfirmed Support Packages are displayed on the screen and in the PATCHOUT. We recommend that you include all existing R/3 HR Support Packages in phase BIND_PATCH (see the next section) of the upgrade. a warning appears that informs you which Support Packages these are. the Hot Packages and Legal Change Patches are divided into several subpackages: • Hot Packages: − − − Basis Support Packages (software component SAP_BASIS) Cross-Application Support Packages (software component SAP_ABA) R/3 Support Packages (software component SAP_APPL) • Legal Change Packages: − − − − Basis Support Packages (software component SAP_BASIS) Cross-Application Support Packages (software component SAP_ABA) R/3 Support Packages (software component SAP_APPL) R/3 HR Support Packages (software component SAP_HR) In this case. SAP Note 73510 specifies which R/3 HR Support Package in the target release is equivalent to your current state. you must include the HR Support Packages. Reimporting the R/3 HR Support Packages in the target release does not solve this problem. If you upgrade your system without doing this. the overall runtime of the upgrade is reduced. the R/3 HR Support Packages already imported into your SAP System are canceled and data is lost. Confirm these Support Packages with transaction SPAM. If you use an add-on component. All software components appear whose Support Package level is more up-to-date than the status of the software components on the upgrade CD. One disadvantage of including Support Packages in the upgrade is that the runtime of the upgrade phases SHADOW_IMPORT_REP. You can include the Support Packages for multiple software components in this phase. However. If R3up displays a warning that your Support Package level is too up-to-date and you want to include Support Packages in the upgrade. To include Basis Support Packages. you can find information about including the corresponding Add-On Packages or Conflict Resolution Transports in the SAP Note for the Add-On Supplement CD.

Log on as user <sid>adm.SAR SAPCAR -xvf <CD_DRIVE>:\<PATH>\<ARCHIVE>.Upgrading to 4.R/3 Frontend using transaction SPAM. If you choose this method.6C Support Release 2: UNIX SAP AG Phase BIND_PATCH You can include the Support Packages for the target release in this phase.SAR UNIX Windows NT If you want to download the archives from a Support Package Collection CD. You can download the Support Packages in one of the following ways: − − − from SAPNet . Check whether the unpacked Support Packages are in the EPS Inbox of your transport directory: Operating system EPS Inbox of the transport directory /usr/sap/trans/EPS/in <DRIVE>:\usr\sap\trans\EPS\in UNIX Windows NT 84 April 2001 . the following Support Packages are already included in the upgrade: Component Support Package SAP_BASIS SAP_ABA SAP_APPL SAP_HR 1 .15 1 . proceed as follows: 1. When you upgrade to 4.19 If you want to include additional Support Packages. you can find details about the archives and their paths in the readme file on the CD.15 1 . Use the following command to unpack the archive that contains the Support Packages: Operating system Command SAPCAR -xvf /<CD_DIR>/<PATH>/<ARCHIVE>. following its instructions 2. from the SAP Service Marketplace. following the instructions in SAP Note 83458 from a Support Package Collection CD.15 1 .6C Support Release 2. 3. 5. Switch to the following subdirectory in your system: Operating system Subdirectory /usr/sap/trans <DRIVE>:\usr\sap\trans UNIX Windows NT 4. skip points 2 through 4 and proceed from point 5. Download the Support Packages of the target release.

The modification adjustment function ignores this request. Whether you have the option of including Conflict Resolution Transports (CRTs) or Collective Conflict Resolution Transports (CCRTs) in the upgrade depends on what is written in the SAP Note for the particular add-on component. Answer the prompt about searching for new Support Packages with Search. In certain situations. call Transaction ICNV and choose Information. you are prompted to start transaction ICNV. It may take a few minutes to unpack the Support Package data. 8. make sure that these packages are also in the EPS Inbox. For an online description of how to use this transaction. answer Yes to the prompt about including Support Packages in the BIND_PATCH phase.6C Support Release 2: UNIX For Source Release 4. you can use a single change request to avoid losing data. Enter the Support Package level you want for your various software components.SAP AG Upgrading to 4.0B: If you want to include Conflict Resolution Transports as well as Add-On Support Packages for Add-On components. you also have the option of including a single change request. You can skip this step with Skip if you have not downloaded any new Support Packages since the last time you searched. All you need to do is overwrite the default Support Package level. If you want to include (more) Support Packages for your various software components. The Package Keys are in SAP Note 119738. 7. If you want to cancel the selection for a software component completely. Any Support Packages that you cannot include in the upgrade must be imported into the system after the upgrade. You no longer need to reset PREPARE to reduce the number of Support Packages that you want to include. April 2001 85 . When you confirm the confirmation prompt you integrate all Support Packages up to the specified level into the upgrade for the selected components. As well as the software components. 6. 9. You cannot include SPAM Updates in the upgrade. You need a Package Key to include a Basis Support Package in the upgrade. you are prompted to choose a request. Phase ADJUSTPRP If you want to execute PREPARE in a target system and you made preparations for an automatic modification adjustment in the first system. Using the single change request function is risky. Phase ICNVREQ_PRP If PREPARE determined candidates for incremental table conversion (ICNV). Only use this function if the owner of the request can guarantee that it is compatible with the upgrade. or enter NONE if you are using scroll mode. select the appropriate field if you are using the Upgrade Assistant.

have been completed.Upgrading to 4. 86 April 2001 . If you reset PREPARE. in particular the inclusion of Support Packages. Call the steps Initialization and Data Transfer in the ICNV only when all PREPARE actions.6C Support Release 2: UNIX SAP AG If you do not want to use this option. For more information on incremental conversion. see Planning the Upgrade → Incremental Table Conversion. the tables are converted during downtime. this does not cancel any modifications made by initializing the ICNV.

PFL: Value sendon. Add the space that you will need for additional data before you actually upgrade the system. The entries in the file CHECKS.PFL and make sure that the parameter rdisp/bufrefmode is not set in the local instance profile. If you have distributed application servers that do not use NFS to share access to the profile of the central instance. April 2001 87 . The procedure is described in the following database-specific sections. Call transaction ICNV and finish incremental conversion. The parameter rdisp/bufrefmode must have on of the following values in the profile /usr/sap/<SAPSID>/SYS/profile DEFAULT. This file is located in the sub-directory log of the upgrade directory. see the online help for ICNV. information or prompts for user action.LOG. This is followed by the PREPARE results. The incremental conversion is not yet finished from a previous upgrade.SAP AG Upgrading to 4.exeauto sendoff. PREPARE writes its results to the file CHECKS. Procedure Most of the entries are self-explanatory. The extensions required are specified in a table in CHECKS.LOG. Use Transaction ICNV to lock this conversion. • Insufficient freespace in the database as follows: The new release needs more space in the database. enter the value sendon. The data for the new release cannot be imported into the existing space in your database.6C Support Release 2: UNIX Evaluating the Results of PREPARE Use As mentioned in the section PREPARE [Page 212]. You can find information and procedures for the other entries in the following: • Incremental conversion is not completed.exeauto Use if Multiple SAP instances are installed for this system (<SAPSID>) one SAP instance is installed for this system (<SAPSID>) Also make sure that the parameter rdisp/bufrefmode is not set in the instance profile.exeauto in each local DEFAULT.LOG can be error messages. For more information. • The buffers of your R/3 instance are not automatically validated. Each run of PREPARE generates a header entry containing the text Starting new execution of PREPARE modules <modulename> at <time_stamp>.

Corresponding index and data tablespaces should not be on the same disk. You can find more information in the SAP online documentation on database administration for DB2 Universal Database. For an exact description.2 increases the page size of a database page from 4 KB to 8 KB. make sure that they are not located on the same disk: This improves performance. For performance reasons. you must take the following restrictions into consideration when creating the new tablespaces (in the order they are listed): − − − Different containers of a tablespace should be located on different (physical) disks. create a new devspace with the database tools. DB2 Universal Database Extend the listed tablespaces by at least the specified values. You can find information on extending and creating dbspaces in the SAP online documentation on database administration for Informix. Database Release 7. Informix Extend the listed dbspaces by at least the specified values. The space check is made at the dbspace level. PSAPES<Rel>D and PSAPEL<Rel>D must not be on the same disk.Upgrading to 4. see Note 34690. To create or extend tablespaces. If you moved tables with delivery classes other than “L” to your own dbspaces. Create the new tablespaces as required by PREPARE. These are always the following tablespaces for the Repository Switch: PSAPES<Rel>D PSAPES<Rel>I PSAPEL<Rel>D PSAPEL<Rel>I <Rel> stands for the current target release. When you create the dbspaces. These are always the following dbspaces for the Repository Switch: psapes<rel> psapel<rel> <rel> stands for the current target release (lower case). The required freespace is based on the database version you are currently using.LOG). you can use the DB2 administration tools or a DB2 Command Line Processor Template generated by PREPARE (see file CHECKS. you should have roughly the same size freespace 88 April 2001 . Create the new dbspaces as required by PREPARE.6C Support Release 2: UNIX SAP AG SAP DB To extend your database.

You can now create tablespaces with sapdba. April 2001 89 . - We recommend the following combination: Disk 1: PSAPES<Rel>D and PSAPEL<Rel>I Disk 2: PSAPEL<Rel>D and PSAPES<Rel>I To extend and create tablespaces. Note that the parameter fsize is increased by the same amount for the user <sapsid>adm. however. Create the new tablespaces as required by PREPARE.6C Support Release 2: UNIX available in these dbspaces as in the original dbspaces of the tables. Where necessary. A typical example is moving the ATAB from the dbspace psappool. Otherwise <sapsid>adm is unable to start up the database after large tablespaces have been created. use the program <upgrade_directory>/exe/sapdba as user ora<sapsid>. You can overwrite these values. AIX If the AIX user parameter fsize (=maximum filesize) is set to the default value of 1 GB for the user ora<sapsid>. Oracle Extend the listed tablespaces by at least the specified values. End of AIX sapdba suggests other values for the extension than those specified in the list. increase the value of fsize. error messages are issued if tablespaces greater than 1 GB are created. Avoid fragmenting the database too strongly. you must meet the minimum requirements of the list. and must not be in the same sapdata directory PSAPES<Rel>D and PSAPEL<Rel>D must not be on the same disk. You can find further information in the SAP online documentation on the program sapdba. you must take the following restrictions into consideration when creating the new tablespaces: - index tablespaces and data tablespaces that belong together must not be on the same disk. For performance reasons. Be generous when you extend existing tablespaces. Reboot your AIX System to activate the new values.SAP AG Upgrading to 4. Choose a low degree of fragmentation when you create tablespaces. These are always the following tablespaces for the Repository Switch: PSAPES<Rel>D PSAPES<Rel>I PSAPEL<Rel>D PSAPEL<Rel>I <Rel> stands for the current target release.

see Releasing Open Repairs and Requests [Page 208]. If you have to create a tablespace in more than two fragments.6C Support Release 2: UNIX SAP AG For the tablespace PSAPES<Rel>D. Change the write authorization with: chmod ug+w <executable> If the program does not belong to the group sapsys. For information on this. End of the database-specific explanations • In Release <rel> you applied the following unconfirmed patches to your system. Correct this by changing the authorizations or the owner. since the objects contained in them are locked. for security reasons. BW Support Packages. Their numbers are listed. If open repairs that do not belong to this system are displayed. you must either change the group or add the user <sapsid>adm to the group temporarily. such as R/3 Support Packages. Note 62519 gives you possible solutions to this problem. There are unconfirmed Support Packages in your system. Also check the extent structure of the tables. We do not recommend that you give write authorization to others.2) * 100 MB to the total size of the tablespace. Use the Transaction SPAM to confirm these Support Packages before the upgrade. 90 April 2001 . Before you begin upgrading. R/3 HR Support Packages. otherwise the import of the substitution set will terminate. These open repairs cannot be released in the normal manner. you must release and confirm all the open repairs and requests listed by PREPARE. • Release these open transport requests and repairs: Modifications can be lost if open repairs are ignored There are locked SAP objects in open repairs and/or requests in your system. create at least one data file with 2 GB. The programs that are affected are listed in the lines ERROR> No write permission for file <executable>. • no write permission on <file name>: The specified file in the directory of user <sapsid>adm cannot be overwritten because the authorizations were not correctly set or the owner of the file is not <sapsid>adm. • Change the permission of these executables: You must be able to overwrite the programs of the old SAP Kernel to be able to copy the new SAP kernel to the directory /usr/sap/<SAPSID>/SYS/exe/run during the upgrade. add (n . then this system was created by a database copy. For more information.Upgrading to 4. APO Support Packages and so on. see the Online Documentation under Help → SAP Library → Basis Components → Change and Transport System → Language Transport. where n is the number of fragments.

<SAPSID> where <YY> is the year (2 digits) and <WW> is the calendar week (2 digits).. Entries found in this table by R3up may be the remains of a terminated or running import or export. Your system contains outstanding conversions and restart logs of terminated conversions.Basis Components → Change and Transport System → BC .Transport Tools → Transport Control Program tp • The following indexes <number> were read: Indexes whose names are identical up to the 14th character were found in a table belonging to the substitution set.6C Support Release 2: UNIX You must log on to the system under the name of the relevant owner to release and confirm the open repairs. The 14th character is an 'X' in one of the two names and is empty in the other..SAP AG Upgrading to 4. First try to process the TRBAT entries from /usr/sap/trans/bin with the following command: tp getprots <SAPSID> Running imports or exports are not affected.. .x: Help → SAP Library → BC . TRBAT entry indicates that a batch job has finished.. The list in CHECKS. This is an inconsistency and would result in an error during the import of the substitution set. • Unresolved request found in TRBAT.LOG contains these names. Use Transaction SM31 to delete any entries in TRBAT that cannot be processed and that are no longer needed. • Restart logs of DB conversions found. ... Clean these up as described under Cleaning Up Terminated Conversions in the DB Conversion Phases [Page 179]. TRBAT entry indicates that a batch job is running... You can find more information about the transport control program tp in the SAP Library: Choose in Release 3. You can monitor the tp monitor file with the following command: tail -f /usr/sap/trans/log/SLOG<YY><WW>.Basis →=System Administration → Transport Control → Transport Control Program tp in Release 4. The transport control program tp uses the table TRBAT to communicate with the SAP System..x: Help → R/3-Library → BC . Do not delete entries for running imports or exports during production operation... Corrupted TRBAT entry found. ... Determine and clean up entries for terminated imports or exports during the upgrade preparations.. Outstanding DB conversions found. tp informs you in this file about any problems during processing. April 2001 91 .....

These must be cleaned up before you start the upgrade. 3.. • Update records still exist . To determine the terminated or outstanding updates.6C Support Release 2: UNIX SAP AG The index with the 'X' at the 14th position can only have occurred in a Repository Switch or have been created outside the SAP System. The views will be created in this upgrade. you must first make a backup. Use the SAP DB tool xcontrol to give MAXLOCKS the correct value. The changed parameter only becomes active after you have stopped and started the database. 2. Consult a Basis consultant. proceed as follows: 1. Therefore . since otherwise table or index modifications could terminate. You must delete these tables. Start Transaction SM13. • The following database tables have names that are identical to names of Basis views. user and time. To do this. Choose all the update requests.. 2. Repeat this check when the system stops operating productively (see Isolating the Central Instance [Page 202]). SAP DB • Insufficient DB parameter MAXLOCKS. Log on to the system as user DDIC and start Transaction SE14. If you are still in the preparation phase (PREPARE) and therefore in production operation.Upgrading to 4. Terminated or outstanding updates have to be followed up or deleted in all clients. Delivered views may have names identical to the names of customer tables in the SAP namespace.please process Make sure that you have cleaned up all outstanding updates by the phase JOB_RSVBCHCK3 (during downtime) at the latest. you only have to delete the terminated updates.<TABNAME> drop primary key" 3. Enter the following command: db2 "alter table sapr3. DB2 Universal Database • DATABASE ERROR: There is an inconsistent index in your database: Index SQL<nnnnnnnnnnnnnnn> on table <TABNAME> The information about the primary index names was lost and was replaced with a name generated by the database system because the IBM export/import tool was used. Log on as user <sapsid>adm. 92 April 2001 . Reconstruct the primary index (index ID 0) on the database. Delete the default values for the client. If you need the table data later. proceed as follows: 1.

2.SAP AG Upgrading to 4. To do so. shut down the database with stopsap db and start it up again with startsap db. Increase <param> with the following command: update db cfg for <sapsid> using <param> <new value> 3. Set the parameter(s) to the required value. Certain database parameters are set too low for the upgrade. ---> Set the parameter to <new value>.6C Support Release 2: UNIX • DATABASE ERROR: The value <old value> of <param> database configuration parameter is too low. Proceed as follows: 1. End of the database-specific explanations April 2001 93 . The parameters do not become effective until the database is restarted. Log on as db2<sapsid> and start up CLP with db2.

the SAP Kernel programs are replaced under /usr/sap/<SAPSID>/SYS/exe/run. see the SAP Notes 39473 and 39475. the scripts for starting and stopping the SAP System are substituted so that they correspond to the new release. Backing Up the Scripts for Starting and Stopping the SAP System During the upgrade. Making Operating System-Specific Preparations ReliantUNIX You must change the instance profiles of all the SAP instances. you must back up the scripts before you upgrade.6C Support Release 2: UNIX SAP AG Making Preparations at the Operating System Level Backing Up the SAP Kernel During the upgrade. /install/os_version/Relia=SINIX 2. Depending on the operating system setting displayed with the command uname. These profiles are in the directory /usr/sap/<SAPSID>/SYS/profile and usually stick to the following naming convention: <SAPSID>_<instance name><instance number>_<host name> Insert the following parameters: 1. also insert one of the following parameters: /install/os_version/ReliantUNIX-Y=SINIX (or (or /install/os_version/ReliantUNIX-M=SINIX) /install/os_version/ReliantUNIX-N=SINIX) For more information. Make sure that you can recover the old Kernel if this becomes necessary. /install/os_version/ReliantUNIX=SINIX 3.Upgrading to 4. End of ReliantUNIX 94 April 2001 . If you have modified the standard scripts. so that you can repeat the modifications after the upgrade. Make a backup copy of these programs to guarantee this.

0B: Make sure that the statistics are up-to-date for all tables. Out-ofdate statistics can increase the runtime of the upgrade significantly. The changed parameter only becomes active when the database is stopped and started. Log on as user <sapsid>adm at the operating system level. You must back up the log when you isolate the central instance. The procedure is described in Note 113008. End of Oracle Making Database-Specific Preparations SAP DB For the upgrade.6C Support Release 2: UNIX Making Preparations at the Database Level Backing Up the Database Make sure that you can reset the database to the state it had before the upgrade by using an existing database backup. Oracle 1. DB2 Universal Database User sapr3 needs additional authorizations for updating the statistic values.ora. April 2001 95 . Change MAXUSERTASKS for the upgrade so that it is at least 3 larger than the number of started disp+work processes.SAP AG Upgrading to 4. 2. SAP DB We recommend that you make a complete backup of the database before upgrading.indexes to user sapr3 DB2 for OS/390 We recommend that you update the statistics before the upgrade. If the value is lower than 50 MB. Proceed as described in the section Oracle: Actions → Updating Statistics. Enter the following commands: grant update on table sysstat. change the database parameter MAXUSERTASKS. Determine the number of started disp+work processes with Transaction SM50. For a description of the upgrade strategies that you can choose from. Oracle You can find detailed information about making backups as well as about the programs brbackup and brarchive in the SAP online documentation on database administration for Oracle. As of Source Release 4. increase it to at least 50 MB and restart the database.tables to user sapr3 grant update on table sysstat.columns to user sapr3 grant update on table sysstat. see the section Planning the Upgrade Strategy [Page 20]. Check the value of the parameter shared_pool_size in the file $ORACLE_HOME/dbs/init<SID>.

4.. Start brarchive as user ora<sapsid> from the temporary directory: /tmp/brarchive -f . If your database version is already higher than the minimum version for the new release.Upgrading to 4. enter the SQLPLUS command: grant unlimited tablespace to sapr3. Note 201874 contains the tables and the required minimum values. This procedure avoids upgrade errors caused by overwriting the executables during the upgrade. If you are not sure. Make sure that these quotas are unlimited. Log on to the database as the Oracle user system with sqlplus (default password is manager). they may overflow during the upgrade.0x/3.1x Only: Make sure that the parameter OPTIMIZER_MODE has the following setting in the Oracle profile $ORACLE_HOME/dbs/init<SAPSID>.). 5. If this entry does not exist.privilege='UNLIMITED TABLESPACE'. Check the value of the storage parameter MAXEXTENTS for the tablespace PSAPTEMP. you can also determine these names with sapdba. Note 11777 describes how to change the parameters NEXT and MAXEXTENTS.. 96 April 2001 . For Upgrade Strategy A_on Only: If you want to leave brarchive running during the upgrade to avoid Archiver Stuck situations (brarchive -f . 10. we recommend that you switch the DBA tools (such as sapdba) for the upgrade. Source Releases 3. delete the copy of brarchive. c. Otherwise. Check the resource quotas of the database user SAPR3: Oracle error 1536 can occur during the upgrade if the resource quotas of the database user SAPR3 are limited. The index names are not constant. Make sure that the storage parameters MAXEXTENTS and NEXT have the correct values for certain tables and indexes. enter the following SQLPLUS command: select * from dba_sys_privs where grantee = 'SAPR3'. execute the script psaptemp.6C Support Release 2: UNIX SAP AG 3. This script sets the value of MAXEXTENTS for the tablespace PSAPTEMP to UNLIMITED. 9. You can display the current settings with sapdba..privilege='UNLIMITED TABLESPACE'.. 7. Log off the database with the command quit. After the upgrade.adm='NO' To do this.sql as the database administrator. Check whether table DBA_SYS_PRIVS contains one of the following entries: grantee='SAPR3'.adm='YES' grantee='SAPR3'.sql is located in the bin subdirectory of the upgrade directory.ora: OPTIMIZER_MODE=RULE 8. Make a temporary copy of brarchive: cp /usr/sap/<SAPSID>/SYS/exe/run/brarchive /tmp b. The script psaptemp. However. 6. proceed as follows: a.

End of the database-specific explanations April 2001 97 .6C Support Release 2: UNIX The RDBMS CD for the database contains the up-to-date tools that you unpacked on the current Kernel when you migrated the database. After you execute PREPARE.SAP AG Upgrading to 4. unpack this archive again into the subdirectory exe of the upgrade directory. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version.

1x) [Page 105] 98 April 2001 .1x) [Page 102] Converting the Translation Proposal Pool (Source Releases 3.6C Support Release 2: UNIX SAP AG Making Preparations at the SAP System Level As well as the preparations at the operating system level and the database level.0x/3.1x) [Page 102] Backing Up Wage Types in HR (T512W) (HR Customers) [Page 103] Printing the Default Values for Document Type and Posting Key (FI Customers) [Page 104] Processing Direct Input Error Data (Source Releases 3.Upgrading to 4.0x/3.0x/3. you also need to make preparations at the SAP System level: • • • • • • • • Checking the User for the Upgrade [Page 99] Checking Requirements for the Modification Adjustment [Page 100] Setting the Operation Mode for the Upgrade [Page 101] Processing Batch Input Sessions (Source Release 3.

Procedure To make sure that the authorization has been assigned. because the system is undefined. User DDIC needs to have the authorization SAP_ALL to be able to perform all the actions required during the upgrade. you must log on in the correct client as the user who performs the modification adjustment using transaction SPDD. To perform the modification adjustment.SAP AG Upgrading to 4. This must be a user other than DDIC. Remove this assignment after the upgrade. This means that you cannot create new users. If your system contains the SAP_NEW profile. make sure that the following users are assigned this profile in addition to their existing profiles: • • • DDIC SAP* The user who performs the modification adjustment with transaction SPDD If the SAP_NEW profile is not available in your system. Choose Tools → Administration → Maintain users → Users.6C Support Release 2: UNIX Checking the User for the Upgrade Prerequisites You must be able to log on to the system in client 000 as user DDIC. The initial password for DDIC is 19920706 in a newly installed system. April 2001 99 . or call transaction SU01. You cannot use transaction SU01 at this point. go to user maintenance. You must perform the modification adjustment during the upgrade in the ACT_<rel> phase. we recommend temporarily assigning the SAP_ALL profile to the user who performs the modification adjustment with transaction SPDD. DDIC cannot perform the modification adjustment.

6C Support Release 2: UNIX SAP AG Checking Requirements for the Modification Adjustment If you modified SAP objects in your SAP System. In particular.Basis Components → ABAP Workbench → BC .Upgrading to 4. you might also risk losing the data for ABAP Dictionary objects. make sure that changes to the Repository are allowed in the client in which you want to perform the modification adjustment. we cannot guarantee complete support during adjustment. In addition. If you do not make sure that you have met the requirements for the modification adjustment. To check this. use Transaction SCC4. For more information on the requirements for the modification adjustment.Changing the SAP Standard → The Modification Assistant. 100 April 2001 . see the documentation CD for the target release under SAP Library → BC . make sure that you meet the requirements for the modification adjustment.

If the SAP instance on which you want to upgrade the system is not entered in an operation mode. Call Transaction RZ04. April 2001 101 . for example. background processing. and so on). the server name may be entered as <host_name>_<SAPSID>. Also check the operation mode DUMMY. b. Enter a short description and then save the operation mode. Enter a name for the operation mode. Before starting the upgrade. use Transaction RZ04 to check the definition of your operation modes. Upgrade. f. Choose Operation mode → Create. but not set to status active (in theory. a check is made to see whether the SAP instance that you want to run them on is defined in an operation mode. in particular. d. spool.SAP AG Upgrading to 4. Procedure 1. 3. Select Normal operation (24 hours). Make sure that the instance required for the upgrade has been started up. this affects all jobs scheduled to start on a specific server triggered by an event). All instances and their current configuration appear. g. Position the cursor on the new operation mode and choose Operation mode → Maintain instances → Operation mode view.6C Support Release 2: UNIX Setting the Operation Mode for the Upgrade Use Various background jobs are started during the upgrade. If operation modes contain names of servers other than those belonging to the system. The operation mode specifies which services are offered by the work processes (dialog. When you schedule time-dependent jobs. Choose Save. c. update. enqueue. Prerequisites No operation modes must contain servers that do not belong to the current system. create the operation mode for the upgrade as follows: a. In the case of operation mode DUMMY. e. problems may arise in the background interface in some phases. The jobs may be released. 2. Delete the invalid operation modes. Change this entry to <host_name>_<SAPSID>_<instance_number>. Enter the operation mode you have defined as an active operation mode for 24 hours using Transaction SM63. Choose Settings → Based on current status → New instances →=Generate.

For more information.1x) Use Due to a change in the data structure. 102 April 2001 .0x/3.0x or 3.0x/3. Procedure Make sure that you have finished processing all your batch input sessions before the upgrade. Prerequisites Your source release is 3.0x or 3. If you fail to do so. see the documentation on the report in the system.6C Support Release 2: UNIX SAP AG Processing Batch Input Sessions (Source Releases 3. Converting the Translation Proposal Pool (Source Releases 3.1x. Prerequisites Your source release is 3. Source release 3.1x Only) Use If you have a production system for translation in your SAP System. you must convert the existing proposal pool before upgrading to Release 4.1H: Proceed as described in Note 98752. old sessions cannot be processed after the upgrade.Upgrading to 4.1x. Procedure • • Source release lower than 3.1H: Use report RSTRMINI for the conversion.x. the existing proposal pool will be lost.

Procedure 1. However. use report RPU12W0S.SAP AG Upgrading to 4. and so on). Prerequisites You use the SAP application component HR (Human Resources). check table TRESC by entering T512W as the table name and TABU as the object. in the following cases. You are using SAP model wage types. Table T512W is client-specific.6C Support Release 2: UNIX Backing Up Wage Types in HR (T512W) (HR Customers) Use We generally recommend backing up wage types table T512W before upgrading. This method is particularly suitable if you have exact documentation about the wage types you have modified. Before the upgrade. The documentation on the report includes instructions on how to proceed. you must back up table T512W: • • • You have modified 'technical' wage types. that is wage types beginning with a letter. and you have modified these. RPU12W0S restores the entire backup or a generically selected area of the table. To do this. 2. evaluation class. You can restore your backup copy after the upgrade. you can use the following reports: − − RPU12W0C restores selected parts of table T512W. You have defined wage types that are not within the customer name range. back up table T512W or selected areas of this table. that is wage types beginning with '/' (adjustment of processing class. April 2001 103 . To do this. To find out if this applies. Make sure you back up the data in the correct client.

Back up the data before the upgrade by printing out the contents of the table. are lost during the upgrade.Upgrading to 4. use Transaction SE16. 104 April 2001 . To do this. use report RFTSTCP0. Enter TSTCP as the table name and then choose Enter. 2. Reenter the data manually after the upgrade. Prerequisites You use the SAP application component FI (Financial Accounting).6C Support Release 2: UNIX SAP AG Printing the Default Values for Document Type and Posting Key (FI Customers) Use The default values for document type and posting key. Procedure 1. This affects data in the table TSTCP. In the field TCODE. enter F-01 to F-99. stored for posting transactions with transaction codes between F-01 and F-99 (such as F-52 Post Incoming Payments). To do this.

As a result. Procedure 1. program RMDATINF) to process any error data remaining from a direct input run performed with a 3. If jobs of this type exist. April 2001 105 .0 there are changes to the way error data that occurs during the transfer of data by direct input (material master (industry)) is stored.0x/3.x.6C Support Release 2: UNIX Processing Direct Input Error Data (Source Releases 3. These changes are primarily intended to ensure upward compatibility in the future.1x. Before upgrading to Release 4.x using program RMDATINF_3X.1x) Use In Release 4. recover the errors and run the jobs again.0x or 3.x release. Prerequisites Your source release is 3. check if there are any direct input jobs that have terminated abnormally or that have been completed with logical errors.SAP AG Upgrading to 4. you can no longer use standard functions (direct input administration. 2. You can display the messages of previous direct input runs after the upgrade to 4.

If an error occurs. R3up is located on the application server of the central instance. 106 April 2001 . Once you have repeated the phase successfully. for example). If you have multiple CD drives. You can use the alert function [Page 199] to gather information if the upgrade has stopped. User actions are generally required if problems arise (subdirectories are missing. the log files and an alert function to monitor the upgrade. the abbreviation <rel> is used as a synonym for 46C. Prerequisites • • • You must meet the hardware and software requirements. see R3up Phase List [Page 225].Upgrading to 4. For a complete list of all phases. The Upgrade Monitor [Page 242] lets you monitor the upgrade. The upgrade procedure is divided up into a number of different phases with the successful completion of a phase being in each case a precondition for the success of all subsequent phases. right up until the system starts operating productively again. remove the cause of the error and repeat the phase [Page 109] in which it occurred. or none at all. as well as all structural requirements. If your central instance and database are running on different hosts. you can enter multiple CD mount points in the phase INITPUT. You can use the Upgrade Monitor. R3up logs all actions in the log files [Page 171]. which you can use as the basis of any troubleshooting. During the upgrade. An upgrade with R3up requires the following CDs: • • • Upgrade CD3 (new Repository) Upgrade CD4 (new Repository) Upgrade CD5 (new Repository) To avoid having to change CDs. We recommend that you perform the upgrade with the Upgrade Assistant. you must perform the actions that affect the database on the database host. as well as any particularly critical areas. and helps you recognize any processes that have exceeded their runtime. The program PREPARE has run successfully. You have made all manual preparations. you can ignore the information on changing CDs. you are prompted to insert a CD when necessary. The program R3up controls the complete upgrade from checking that the requirements for the upgrade are met. This documentation assumes that you only have one CD drive. Process Flow You use the program R3up to upgrade the system. you can continue the upgrade.6C Support Release 2: UNIX SAP AG The Upgrade Purpose The upgrade procedure updates your SAP System from a source release to a target release. In the following. This section describes all the required user entries and actions. Some phases of the upgrade require you to make few user entries.

the SAPSID and the database you use. the target release. Procedure: 1. confirm this screen with CONTINUE.SAP AG Upgrading to 4. You have made the preparations that are not supported by PREPARE. start R3up as described in the section Executing PREPARE and R3up in Scroll Mode [Page 201]. Start an Upgrade Assistant GUI [Page 68] and log on as administrator. • • • • • You are logged on to the central instance as user <sapsid>adm. before you start the upgrade. April 2001 107 . The deletion of these files could lead to unpredictable inconsistencies. Mount the CD SAP Kernel. The server of the Upgrade Assistant is active on the host on which the central instance is running. In the main menu. R3up displays the initial screen of the upgrade procedure. If the entries are correct. It displays the R3up version. You have completed the mandatory PREPARE modules. 2. Disassemble the SAP Kernel for HP-UX 11 with: R3up readCD cdpath=<CD mount directory> End of Oracle on HP-UX Procedure 1. 2. If you have changed to HP-UX 11 between executing PREPARE and starting the upgrade. PREPARE disassembles the correct SAP Kernel and copies it to the directory put/exe. Oracle on HP-UX Depending on whether you have Version HP-UX 10 or HP-UX 11. then you need to disassemble the SAP Kernel from the CD again. choose Administrator → Start R3up. Enter the following command as user <sapsid>adm to switch the directory: cd <upgrade_directory>/bin 3. This screen will appear in each future restart. 3. No files must have been deleted in the upgrade directory.6C Support Release 2: UNIX Starting the Upgrade Prerequisites • This description assumes that you are using the Upgrade Assistant. If you want or need to use scroll mode.

You can also enter the following command in a second window at the operating system level: R3up stop Stopping the Upgrade at the Start of a Phase Enter the following command in a second window at the operating system level: R3up stop <phase name> R3up stop XPRAS_<rel> 108 April 2001 .Upgrading to 4. you need to do this if a Note tells you to correct a program before you execute it.6C Support Release 2: UNIX SAP AG Stopping the Upgrade Use You can stop R3up at the beginning of a specific phase or at the end of a current phase. For example. Stopping the Upgrade at the End of the Current Phase • • In the main menu of the Upgrade Assistant choose Administrator → Stop R3up after current phase.

Prerequisites • If you restart the upgrade due to an error or a termination during the upgrade. Other START modes can cause errors. it has to be restarted manually once if reset is selected. For help on analyzing errors. Alternatively you can also correct entries with R3up set stdpar or R3up set DDICpwd (see description of phase INITPUT). Before using a password. If a phase terminates. A password is generally necessary if you want to ignore an error. A large number of cases are known where ignoring an error resulted in serious inconsistencies. If you are unsure how to proceed. contact SAP Local Support. You can use the following START modes: • repeat When restarting R3up. R3up stops and suggests repeating the phase by letting you choose repeat. the cause of the error must be clear and the error must be corrected. the phase in which the upgrade was interrupted is repeated from the beginning. If the system is already in downtime. The START mode repeat leads to the upgrade being continued exactly where it was terminated. This mode returns the upgrade to the phase INITPUT. • init If you choose START mode init. SAP must approve their use in each case. If you have exited R3up by choosing exit. at worst resulting in a database • April 2001 109 . R3up runs through the phase and checks where it needs to restart. provided no other procedure is specified in this guide. you should have carried out a thorough problem analysis and discussed the problems with SAP.6C Support Release 2: UNIX Restarting the Upgrade Use Normally. Otherwise it is impossible to ensure that all upgrade phases will be completed correctly. Only in very rare cases does it make sense to bypass a phase with ignore by entering a password. After this you can restart the upgrade only by resetting the database. Support cannot be guaranteed if you do not consult SAP. other START modes are offered. or jump to a phase other than the one currently being executed. This is only possible up to phase SUBSTNT_INS. • reset START mode reset enables you to start the upgrade from the beginning again. always use START mode repeat. see Problems and Solutions During the Upgrade.SAP AG Upgrading to 4. you only need to restart the upgrade if errors occurred or an upgrade phase has terminated. The repeat mode does not necessarily mean that phases are repeated from the beginning.

choose exit to leave R3up and correct the error. If an error occurred. 2.6C Support Release 2: UNIX SAP AG recovery. 110 April 2001 . 2. After a phase terminates. You can ignore errors with repair severe errors in some exceptional cases. and the help offered in Problems and Solutions During the Upgrade to determine the cause of the error and to correct it. Choose the START mode repeat. Use the Help key in R3up. Procedure if You Have Exited R3up After a Termination 1. The system checks if an error can be reproduced. Start the upgrade as described in the section Starting the Upgrade. such as in the phases ACT_<rel> and XPRAS_<rel>. choose the option repeat. Otherwise the error must be repeated. If it cannot be reproduced. R3up continues the phase at the point at which it terminated. the upgrade continues after the phase is completed. R3up repeats the terminate phase and continues the upgrade. When you choose repeat.Upgrading to 4. Procedure if You Have Left R3up by Choosing exit 1.

confirm with ENTER. for example. You can modify the entries you made in PREPARE in the INITPUT phase. If you skip this phase and realize in the following phases that you made an incorrect entry. If the default values are correct. April 2001 111 . • • If you confirm this. paths and passwords.6C Support Release 2: UNIX Phase INITPUT Use In the Parameter Input PREPARE module you are prompted to enter values for certain systemspecific parameters needed by the upgrade.SAP AG Upgrading to 4. Activities At the start of this phase R3up asks you whether you want to change any parameters. you are prompted for all the parameters. names. correct it as described under Correcting Entries from the INITPUT and INITSUBST Phases [Page 185].

Activities If the error message No information received from the database appears. To access this documentation. 2. To see the documentation. Choose Configuring the Workbench Organizer with Transaction SE06.x – 4. 112 April 2001 . Release 3. SE06 is described online. which logs on to the database and reads the necessary information from there. Go to the initial screen of Transaction SE06. Choose Install. If this is the case. Then exit the transaction.Upgrading to 4. choose New installation as the system status and select the correct System configuration.6x: Use Transaction STMS (Transport Management System) to initialize the Change and Transport System. call Transaction SE06 in the SAP System as user DDIC.6C Support Release 2: UNIX SAP AG Phase DBCHK Use This phase determines the version of the database and the release of the SAP System. see the TMS online documentation. R3up calls the transport control program tp. Any problems in this phase are normally due to the database connection being broken. check the file SLOG46C in the subdirectory log of the upgrade directory. select Help → Application help in Transaction SE06. Release 4.Transport Management System. Confirm any other dialog boxes with Yes or Continue until the system settings have been completed. This takes you to the documentation Setting up the Workbench Organizer and the Transport System. For more information. choose Information in Transaction STMS or go to the menu and choose Help → SAP Library → BC Basis Components → Change and Transport System → BC .5B: 1. A frequent source of problems with tp is an incorrectly configured Change and Transport System.

the RFC connection to your SAP System is tested. start R3up again using the following command: R3up set stdpar April 2001 113 .6C Support Release 2: UNIX Phase RFCCHK Use In this phase. if you receive an error message.SAP AG Upgrading to 4. Your SAP System cannot be reached on the gateway you have specified. it may be due to the following reasons: • • Your SAP System has not been started. Activities To correct your entries.

ii. If errors occur. To display the list. To do this. If the job is successfully. The value of the SAP profile parameter DIR_PUT must match the current upgrade directory. Choose repeat to repeat the phase.Upgrading to 4. − If no background job can be started. proceed as described in Correcting Entries from the INITPUT and INITSUBST Phases [Page 185]. you either have to change the network configuration or change the entries made in the INITPUT phase. this is generally due to a problem with the name of the background server. however R3up cannot find the log. use transaction SM21 to check the system log of the SAP System.6C Support Release 2: UNIX SAP AG Phase BATCHCHK Use This phase tests whether the background server can access the upgrade directory To do this. Check whether the host specified in INITPUT is also in the list with a running background service. ii. call transaction SM37 to check whether the background job has run. To change the entries. make sure of the following i. i. the background job RDDIT008 is started on the specified background server. 114 April 2001 . This job writes a test log in the tmp subdirectory of the upgrade directory. Procedure 1. 2. perform a test call of the function module TH_SERVER_LIST in transaction SE37. The file system of the upgrade directory must be mounted on the background server. − − If the job terminates. double-click the table parameter LIST after executing the function module. Depending on the problem.

− − and you have already included Support Packages in the BIND_PATCH phase of PREPARE. you will lose data if you continue with the upgrade. repeat PREPARE. and you have not included any Support Packages in the BIND_PATCH phase of PREPARE. If you still have to confirm Support Packages for the source release. April 2001 115 . 2. and include the necessary Support Packages. call transaction SPAM and confirm the Support Packages that are proposed there.SAP AG Upgrading to 4. you must reset the upgrade. For more information about this. Activities 1. If a warning appears that the Support Package version of your source release is too high. see the description of the phase PATCH_CHK3 under Making Entries for the Read CD Module. you can ignore the warning.LOG file in the log subdirectory of the upgrade directory. Whether the source release contains Support Packages that are more recent than those in the delivered target release • The phase PATCH_CHK3 in PREPARE has already made these checks. In this case.6C Support Release 2: UNIX Phase PATCH_CHK Use This phase tests: • Whether all Support Packages (such as Basis Support Packages) have been confirmed for the source release Unconfirmed Support Packages are displayed on the screen and in the PATCHOUT.

If you use SAP add-on components in your system (such as IS components). Phase KEY_CHK Use This phase prompts you for the keyword specified in the current Upgrade Note. see Notes for the Upgrade [Page 40]. Activate these objects with Transaction SE11.6C Support Release 2: UNIX SAP AG Phases INTCHK and INTCHK_SW Use This phase checks if the inactive nametab is empty An error is returned if it is not empty.LOG. you will also be prompted for other keywords. Activities If you have not already done so. 2. SAP Systems which have other software components (add-ons) installed must wait until the upgrade has been released by the relevant add-on software vendor. To determine the objects that are affected. Call R3up again using repeat. Activities 1. The inactive nametab is then empty. 3. The Notes are continually being updated. display the log file DDXTTCHK.Upgrading to 4. request the most recent Notes now. 116 April 2001 . For a list of the Notes you require for the upgrade.

you can resume production from the PRODCHK_<rel> phase once the SAP System has been stopped (see also Planning the Upgrade). see SAP Note 46430. Oracle This prompt does not appear in Oracle and MS SQL Server. • If you decide to use A_on or A_switch. Informix The number of parallel R3load processes you choose depends on your upgrade strategy and hardware. DB2 for OS/390 Note that DB2 logging is always activated. DB2 for OS/390 We recommend ten parallel R3load processes.6C Support Release 2: UNIX Phase INITSUBST Use You must specify the following in this phase: • • • • The upgrade strategy The number of parallel processes available to import the substitution set The number of parallel background processes The number of parallel tp processes during the PCON_<rel> phase (DB2 for OS390) Activities • Upgrade strategy Choose one of the strategies described under Planning the Upgrade Strategy: A_switch. If you answer the prompt define upgrade stop with yes. Your upgrade strategy does not influence logging. SAP DB The number of parallel R3load processes you choose depends on a number of factors. see Planning the Upgrade Strategy. you are also asked to specify the time at which you want to restart production operation of your system. or A_off. We recommend between two and five parallel processes. At the earliest. For the most up-to-date recommendations. April 2001 117 .SAP AG Upgrading to 4. A_on. Enter a realistic value here. you are asked for the number of parallel processes for importing the substitution set. End of DB2 for OS/390 • If you decide to use A_off. For information on how to choose the runtime. DB2 Universal Database We recommend three parallel R3load processes. the system now prompts you to enter your runtime for the total import of the substitution set.

End of DB2 for OS/390 If you realize in the following phases that you made an incorrect entry. for hosts with up to 256 MB choose three background processes. We recommend ten tp processes. The central instance profile is modified temporarily. 118 April 2001 . These deadlocks appear in the ICLI error log and in the MVS system log. otherwise you will not improve the runtime. We recommend six parallel tp processes. Note that deadlocks may occur if you use multiple tp processes.6C Support Release 2: UNIX SAP AG End of the database-specific explanations • The number of parallel background processes During downtime. This function reduces the runtime in the PCON_<rel> phase. For hosts with up to 128 MB choose two background processes. • Creating indexes with the DEFER YES option In the PCON_REL phase you can create indexes with the DEFER YES option. and for hosts with more than 256 MB. If you want to create indexes with the DEFER YES option. • The number of parallel tp processes during the PCON_<Rel> phase You are asked if you want to use multiple parallel tp processes in the PCON_<rel> phase. The upgrade tool sets up the indexes again in the STOPR3_IREL phase. however the upgrade process deals with them by repeating a follow-up process. correct it as described under Correcting Entries from the INITPUT and INITSUBST Phases [Page 185]. you are prompted to enter the table size from which you want to use this option. DB2 for OS/390 • Number of parallel tp processes in the NEWTAB_CRE phase You have the option of specifying the number of tp processes in the NEWTAB_CRE phase.Upgrading to 4. Only use this option for indexes on large tables. choose four background processes. the SAP System is started with a modified number of background processes so that operations can be processed in parallel.

LOG file. Activities If the system determines that the operating system must be upgraded to a new version. You must. Phase VIEWCHK1 Use This phase displays conflicts between customer tables in the SAP namespace and views that are newly delivered. First save any data that you need in these tables. you can interrupt R3up at this point. It also writes this information to the VIEWCHK1. however.SAP AG Upgrading to 4. Activities You can ignore the messages at this point. rename or delete the tables in the VIEWCHK2 phase at the latest. April 2001 119 . Do not make any changes in the upgrade directory. This phase checks that the operating system and database versions installed on your computer satisfy the requirements for the upgrade.6C Support Release 2: UNIX Phase CONFCHK_X Use This target release is released for certain combinations of operating system and database versions only.

see Evaluating the Results of PREPARE. and writes them to the file REPACHK1. Activities You can ignore the messages at this point. However. These objects must be released and the repairs confirmed at the latest by phase REPACHK2. For more information. Activities If errors occur in this phase and you have not yet resumed production operation. we recommend checking for outstanding updates and cleaning them up.LOG. The PREPARE message is: Update records still exist . you can bypass these errors with ignore without entering a password.Please process 120 April 2001 .Upgrading to 4.6C Support Release 2: UNIX SAP AG Phase REPACHK1 Use This phase displays all repairs and requests containing objects locked by SAP. Phase JOB_RSVBCHCK2 Use The upgrade stops in this phase with an error message if there are any outstanding or incomplete updates.

Please process 3. Clear the outstanding updates as described in Analyzing Results from PREPARE. April 2001 121 . The PREPARE message is: Update records still exist . Repeat this phase. (See Isolating the Central Instance. the upgrade stops in this phase.SAP AG Upgrading to 4.6C Support Release 2: UNIX Phase JOB_RSVBCHCK3 Use If there are any outstanding or incomplete updates. Proceed as follows: 1.) 2. Make sure that the release for all background jobs was canceled. Activities In this phase you must clear or complete any outstanding updates. except for RDDIMPDP.

this is shown on screen and in the file DBFPLUSD. the SAP System cannot be started without the minimum setting of MAXLOCKS. The changed parameters only become active when the database has been stopped and started. DB2 for OS/390 The required actions for the SPACECHK phases are described in the section Making Entries for the Initialization Module. since PREPARE already made these checks earlier. The corresponding PREPARE message in CHECKS. End of the database-specific explanations 122 April 2001 .6C Support Release 2: UNIX SAP AG Phase SPACECHK_ALL Use This release requires more space in the database than the previous releases. As of Release 3. You can change these database parameters with the SAP DB tool xcontrol.Upgrading to 4. This phase compares the freespace currently available in the database with the minimum requirements for the total amount of data to be imported. The connect information ISOLEVEL and TIMEOUT is checked for the value 0.0D. ISOLEVEL and TIMEOUT.LOG. If more space is required in the database.LOG is as follows: Insufficient freespace in the database as follows SAP DB • • • The database parameter MAXLOCKS is checked for the minimum SAP operational requirements. You can change the connect information with the SAP DB tool xuser. Activities The section Evaluating the Results of PREPARE contains a description of the procedure.

see the PREPARE log CHECKS.6C Support Release 2: UNIX Phase FREECHK_X Use This phase checks to see if there is enough free space in the upgrade directory for the logs written during the upgrade.LOG. All files and subdirectories in /usr/sap/<SAPSID>/SYS/exe/run are overwritten during the upgrade when the kernel is switched. the SAP Kernel is switched in the Kernel directory /usr/sap/<SAPSID>/SYS/exe/run. For more information. This phase also compares the free disk space in the Kernel directory with the space requirements of the new SAP Kernel. Activities At this point. April 2001 123 . During downtime. if this becomes necessary.SAP AG Upgrading to 4. You must have enough free space in the log directory so that the upgrade can run without errors. make sure that you are able to restore the old Kernel.

and so on) from being changed during the upgrade. This lock is needed to prevent development objects (for example. This increases the time in which R3up does not need user input after the last change of CD (EU_IMPORT5 phase). you must confirm that the ABAP Workbench can be locked. If you confirm the lock now: • R3up does not stop in phase REPACHK2 to allow you to confirm the lock on the Workbench. table definitions. Activities If you have chosen strategy A_switch or A_on.Upgrading to 4. R3up asks you in this phase if you want the ABAP Workbench to be locked on all SAP instances now or in the phase REPACHK2. 124 April 2001 .6C Support Release 2: UNIX SAP AG Phase LOCKEU_PRE Use If you have chosen the upgrade strategy A_switch or A_on. you can continue to use your SAP System productively. If you want to do this. R3up waits after input until the time entered in the INITPUT phase as the maximum synchronization time for all the instances has expired (see Phase INITPUT). • • You may not perform any more transports into or out of the SAP System. ABAP reports. since such modifications would be lost.

Activities If you have chosen upgrade strategy A_off. call transaction ICNV. April 2001 125 . R3up checks whether you have already converted the recommended percentage of the selected data (see Incremental Table Conversion [Page 30]). If you ignore the information from R3up. If you called transaction ICNV when you prepared the upgrade.SAP AG Upgrading to 4. Then confirm that you want to continue with the upgrade. See also Changing the Database Recovery Mode. the rest of the data is converted in the conventional manner during downtime. Verify that you can recover the database to its current state at this point. For details on the status of the incremental conversion. Disable the ability of the database to continually recover data. For a description of this. the upgrade control program R3up stops and waits for user input.6C Support Release 2: UNIX Phase EU_IMPORT0 Use At the start of this phase. R3up informs you if you have not. you are prompted at the beginning of this phase to do the following: • • • Isolate the central instance. see Isolating the Central Instance.

126 April 2001 . your time schedule could be seriously disrupted. you are prompted to change the CD. EU_IMPORT3 and EU_IMPORT4. If you miss this prompt. The majority of the substitution set is imported directly from CD-ROM into the database during this phase. SAP DB and DB2 Universal Database The statistics for newly imported tables are updated automatically. less the time taken up by EU_IMPORT2.Upgrading to 4.6C Support Release 2: UNIX SAP AG Phase EU_IMPORT4 Use The runtime for this phase is approximately 30 minutes to an hour for upgrade strategy A_off. End of the database-specific explanations The runtime of this phase is approximately 3 to 4 hours for upgrade strategy A_off. the expected runtime is computed from the total time you specified for the import less the time computed in EU_IMPORT2. For strategies A_on and A_switch. For strategies A_on and A_switch. Phase EU_IMPORT5 Use At the beginning of the this phase. the expected runtime is made up of the total time you specified for the import.

all the repairs which are still in open transport requests are displayed. you have to release and confirm all the open repairs. Any modifications made to SAP objects in your repairs might be overwritten during the upgrade. For information on modifications are copied to the new SAP standard during the upgrade. Activities • Before you continue with the upgrade. you must do so now. under: SAP Library →=Basis Components → =ABAP Workbench → Changing the SAP Standard →The Modification Assistant.LOG. see the documentation CD for the target release. all the repairs and corrections that are not released are displayed on the screen and written in file REPACHK2. April 2001 127 . otherwise the objects contained in the repairs are locked. see Releasing and Confirming Open Repairs and Requests [Page 208]. otherwise the objects in them are locked. To be able to continue. R3up waits until the time entered in phase INITPUT as the maximum synchronization time for all instances has expired (see phase INITPUT). you have to release these transport requests. Once you have released and confirmed all the open repairs. After you have made your entry. • Upgrade strategies A_switch or A_on: If you did not confirm locking of the ABAP Workbench in the phase LOCKEU_PRE.LOG. In this phase.6C Support Release 2: UNIX Phase REPACHK2 Use In this phase. For a description of this procedure. no further transports can enter or leave the SAP System.SAP AG Upgrading to 4. They are also written in the file REPACHK2. After confirming locking of the ABAP Workbench. you could lose modifications. If you ignore open repairs. you must repeat phase REPACHK2.

Upgrading to 4.6C Support Release 2: UNIX SAP AG Phase CNV_CHK_XT Use This phase checks if the following still exist: • • Conversion requests that have not yet been processed Restart logs Activities If you encounter errors. 128 April 2001 . proceed as described under Cleaning Up Terminated Conversions in the DB Conversion Phases [Page 179].

TRBAT entry indicates that a batch job is running... they could be the remains of an import or export that either terminated abnormally or is still running. TRBAT entry indicates that a batch job has finished. Corrupted TRBAT entry found.6C Support Release 2: UNIX Phase TRBATCHK_XT Use The tp program uses table TRBAT to communicate with the SAP System. The PREPARE messages are: Unresolved request found in TRBAT. Activities For information on cleaning up the table TRBAT..... PREPARE already made this check.. see Analyzing Results from PREPARE. .. . . If this table contains entries. . April 2001 129 .SAP AG Upgrading to 4.

at least temporarily. 130 April 2001 . and your own developments. skip the error message with ignore. 2.6C Support Release 2: UNIX SAP AG Phase RUN_RDDIT006 Use This phase determines the set of objects that needs to be copied to the new Repository tables. These modifications cannot be retained during the upgrade. If the modifications are retained. You cannot adjust modifications at this stage of the upgrade. If the tables are database tables. − − If the tables are structures. modified objects that are not delivered. This resets the modifications to the standard SAP version. You can only skip the error message by choosing ignore. Back up any contents of the table. the SAP System might be unable to run with the target release. If you have any questions. Procedure 1. contact SAP Local Support. you can adjust and retain the modifications later in transaction SPDD. Use transaction SE11 to check which table types are affected. For more information. Prerequisites The RUN_RDDIT006 phase ends with an error message stating that the central Basis tables have been modified. This mainly includes generated objects. since the structure of these tables must be adjusted to the target release before the SAP System can be started with the target release for the first time. If necessary. data might be lost if the table structures were modified.Upgrading to 4. and continue with the upgrade. no data is lost. see SAP Note 33888.

It also makes an entry in the file VIEWCHK2. R3up does not stop before the activation of the ABAP Dictionary objects. Pooled or cluster tables must be deleted manually in the SAP System. the modifications it contains are now compared with the modifications in the system.6C Support Release 2: UNIX Phase ADJUSTCHK Use If you chose to copy a request in the ADJUSTPRP phase. If you still need the data in these tables. at the latest.SAP AG Upgrading to 4. you have to save it first. Activities You have to delete these customer tables now. Phase VIEWCHK2 Use This phase displays conflicts between customer tables in the SAP name range and views delivered for the first time. you can still specify that you want R3up to stop in this phase.LOG. you can use R3up for this. The result of this comparison appears. April 2001 131 . If this request contains all the modifications found in the system. Activities You are prompted to confirm the copying of the request. However. If the tables are transparent.

If you do not do this. For details on the status of the incremental conversion. the changes made by the upgrade are reset. the rest of the data is converted in the conventional manner during downtime. Activities If you chose upgrade strategy A_on or A_switch: • Make sure of the following − − − All production work in the SAP System is stopped and no users are logged on to the SAP System. so that you can reset the upgrade to this state at a later point. 132 April 2001 . All changes to the profile are written to the ALPXPOOL. start by reimporting the current version of the profile into your system.6C Support Release 2: UNIX SAP AG Phase MODPROF_TRANS Use The R3up program stops the SAP System in this phase and modifies the instance profile for the duration of the upgrade. • DB2 for OS/390 If you use DB2 for OS/390. All upgrade strategies: Back up the upgrade directory now. Result Once you have completed and confirmed all the activities. If you want to use transaction RZ10 to adjust the instance profile during the upgrade. call transaction ICNV. R3up checks whether you have already converted the recommended percentage of the selected data (see Incremental Table Conversion [Page 30]).Upgrading to 4. If you ignore the information from R3up. All secondary application servers are shut down. End of DB2 for OS/390 So that you can recover your SAP System after errors. you are not prompted to do this. • If you called transaction ICNV when you prepared the upgrade. R3up prompts you to perform several activities. R3up informs you if you have not. also make sure that you have switched off the capability of the database to continually restore data. If you chose the upgrade strategy A_switch. depending on your database and the upgrade strategy you have chosen. Isolate the central instance as described under Isolating the Central Instance. R3up automatically shuts down the central instance and modifies the instance profile in directory /usr/sap/<SID>/SYS/profile (UNIX) or \usr\sap\<SAPSID>\SYS\profile (Windows NT) for the duration of the upgrade. perform the following actions: Strategy A_switch: Make sure that you can recover the database to its current state. which can cause the upgrade to stop running.LOG file.

April 2001 133 .sh startsap_<host name>_<instance number> stopsap_<host name>_<instance number> Activities If you made changes to the environment of the user <sapsid>adm they are no longer active after the upgrade.sh . If other application servers exist. If you replace the profiles of this user you also prevent an obsolete user environment from causing problems during the upgrade.csh . and the change you have made to the environment of user <sapsid>adm to these servers. copy the files listed above. 1. 2.SAP AG Upgrading to 4.dbenv_<host name>. Make the changes again if this is the case. This can lead to incorrect settings being made.csh .6C Support Release 2: UNIX Phase ENVCHK Use This phase tests the environment of the user <sapsid>adm.dbenv_<host name>. The following files are changed: .sapenv_<host name>.sapenv_<host name>. The environment files previously used are copied to <upgrade directory>/exe/INSTALL before being overwritten. Do not copy back the environment files that were saved to <upgrade directory>/exe/INSTALL.

You still need the authorization for creating users. If errors are reported when you activate your own developments after executing this phase. If you want to create a user for the adjustment at this point. data will be lost. This user is valid for a week.Upgrading to 4. see the documentation CD under Help → SAP Library → Basis Components → ABAP Workbench → BC . confirm that you want to temporarily revoke the lock on logging on to the SAP System to allow a normal user logon for the purposes of modification adjustment. use the report program UPGADDUSR. Otherwise. you can correct these here. 1. This leads to the loss of data in customer fields. 2. However. For more information on this transaction. you have to activate these objects after the upgrade. 134 April 2001 . You cannot create any new users in Transaction SU01 at this point. UPGADDUSER creates the adjustment user upg_tmp_user with the password init in the client where you run the report. You do not need a password to do this. otherwise data may be lost. Activities Do not attempt to import adjustment transport requests into the system manually in this phase. since R3up stops when errors occur. If you chose ignore here. this means that the activation has been terminated and you must not continue with the next phase.Changing the SAP Standard → The Modification Assistant → Upgrade Procedure/R/3 Support Packages → Adjusting ABAP Dictionary Objects.6C Support Release 2: UNIX SAP AG Phase ACT_<rel> Use Depending on the results of the phase ADJUSTCHK. because the system is undefined. You first have to remove the cause of the termination. Any requests for automatic adjustment from previous upgrades can be included in this upgrade in the PREPARE phase ADJUSTPRP only. You must make adjustments at this point if you have made structural changes to tables. you may be asked at the beginning of this phase to adjust your modifications to SAP objects so that they correspond to the new SAP standard version of the objects. If you are prompted for a password anyway. you also have the option of choosing ignore to temporarily ignore these errors. Use Transaction SPDD to determine the ABAP Dictionary objects that need to be adjusted. In R3up.

and this time would be exceeded if you executed the next phase. and this time would be exceeded if you executed the next phase.6C Support Release 2: UNIX Continuing the Upgrade After Phase PRODCHK_<rel> Use Up to the PRODCHK_<rel> phase. If you decided to start production operation again now. If you did not specify a time. If you did not specify a time. the procedure described above occurs in the phases MODPROFP_<rel>. Procedure Strategy A_on R3up stops the upgrade if you entered the latest time at which you want to start production. see Phase CHK_POSTUP [Page 136]. Now you can either enter a new time at which you want R3up to stop again. It prompts you to switch the database back to recovery mode. It recreates the status of the system profiles before the upgrade. or you can start a database backup immediately so that you can switch to production operation again afterwards. the way the upgrade proceeds depends on the strategy you have chosen. the procedure described above occurs in the phases MODPROFP_<rel>. You can then use your SAP System for production again or begin the post-upgrade activities. After the PRODCHK_<rel> phase. You then have to start the secondary application servers. R3up does the following: • • • • • It displays the P errors.SAP AG Upgrading to 4. R3up displays the P errors (see Phase CHK_POSTUP [Page 136]). April 2001 135 . It prompts you to start the secondary application servers. In the second case. STARTR3_P<rel> and CHK_POSTUP. For more information on P errors. or you can switch over to production immediately. You are prompted to switch the database back to recovery mode and to create a complete backup of your database. stops the system for the last time and recreates the status of the system profiles before the upgrade. Now you can either enter a new time at which you want R3up to stop again. It starts up the SAP System for the last time. Strategies A_switch and A_off R3up stops the upgrade if you entered the latest time at which you want to start production. R3up does not expect any further user entries unless an error occurs. You can then use your system for production again or begin the post-upgrade activities. STARTR3_P<rel> and CHK_POSTUP.

136 April 2001 .6C Support Release 2: UNIX SAP AG Phase CHK_POSTUP Use You can remove some of the problems that occur during an upgrade after you complete the upgrade.ELG logs. This type of problem is indicated by a P in the second column of the . R3up displays a complete list of these P-messages in this phase. Some of the secondary indexes may not have been created because they were not unique. Any messages that you do not handle immediately need to be handled at the next possible opportunity. Activities To remove errors. Use the ABAP Dictionary tools (Transaction SE14) to create these indexes in the database.Upgrading to 4. You must usually remove the cause of these problems before you start using SAP applications again. proceed as described in the long text of the message.

such as subsequent processing of table clusters (for Source Releases 3.sh. Depending on the actions.6C Support Release 2: UNIX Post-Upgrade Activities Purpose This section tells you how to complete and check the upgrade. The System Administration Assistant is a program in the SAP System that. April 2001 137 . You can use the System Administration Assistant to help you with the postupgrade activities. Then in the initial screen of the System Administration Assistant choose System Administration Assistant → Display. Process Flow You must perform some of the actions before you start operating the system productively again [Page 138]. click the help button (? icon) for help on the System Administration Assistant. Prerequisites You have reached at least the PRODCHK_<Rel> phase of the upgrade. For certain actions.0x and 3.1x). it only displays documentation. You can get more information online in the system. We recommend completing the actions in the order given. Some actions can wait until you have started operating the system productively [Page 152]. you can start transactions directly from the System Administration Assistant. In the following screen. among other things. such as executing the script saproot. or until the next upgrade. lists the post-upgrade activities for each platform. The prerequisite for this is that you have the current online documentation installed.SAP AG Upgrading to 4. You start the System Administration Assistant by executing Transaction SSAA.

R3up then executes the last phases and completes the upgrade. Then perform the following actions: • • • • • • • • • Executing the Script saproot. At the same time you can perform the post-upgrade activities specified by R3up.6C Support Release 2: UNIX SAP AG Actions Before Starting Production Operation R3up stops at the latest in the phase MODPROFP_<rel> so that you can begin early with the post-upgrade activities. 138 April 2001 .Upgrading to 4.sh [Page 139] SAP DB: Backing Up the Database [Page 141] DB2 Universal Database [Page 142] DB2 for OS/390: Preparations [Page 145] Informix: Preparations [Page 146] Oracle: Preparations [Page 147] Distributing SAP Programs [Page 149] Renaming the Local System Log (For Source Releases 3.0x/3.1x Only) [Page 150] Checking the Profile Parameters with Transaction RZ10 [Page 151] You can start operating the system again productively after these actions.

Execute the following command: April 2001 139 . You need the authorizations of the user root to do this.6C Support Release 2: UNIX Executing the Script saproot. 2. Procedure DB2 for OS/390. Informix. The old groups sysadm and sysctrl must be replaced by the new groups db<sapsid>adm and db<sapsid>ctl.sh <SAPSID> exit 2. Oracle./saproot. you need to make a number of adjustments. Start up the system with stopsap and startsap. Execute the following commands: su . DB2 Universal Database For source releases lower than 4. and change the assignments of the following users as follows: New User Group Concept Old User db2<sapsid> <sapsid>adm db2as New Primary Group sysadm sapsys db2asgrp Secondary Group Primary Group db<sapsid>ad m Secondary Group sysadm db<sapsid>ctl db<sapsid>admgroups for all sapsids on the database host sysctrl sysadm sapsys db2asgrp Change the group access authorizations as follows: 1. SAP DB 1. Log on to the database server and all application servers as user root. create the two new groups db<sapsid>adm and db<sapsid>ctl before you execute the script saproot.root cd <upgrade_directory>/exe .6A only: A new user group concept has been introduced in Release 4.6A that makes it easier to separate user authorizations when you operate multiple SAP Systems on a single host.sh.SAP AG Upgrading to 4.sh Use After the upgrade. To do this.

End of the database-specific explanations 140 April 2001 .sh <SAPSID> exit 4. Start up the system with stopsap and startsap. The script requires the environment variables of user <sapsid>adm. Execute the following commands: cd <upgrade_directory>/exe .Upgrading to 4. Log on as user <sapsid>adm. it adapts the database manager configuration to the new groups). For all source releases: The script saproot. Proceed as follows: 1. 2.6C Support Release 2: UNIX SAP AG find /db2/<SAPSID> \! -type l -group sysadm -print | xargs chgrp db<sapsid>adm 3. Execute the following command: su root (not su .sh performs additional database-specific actions (for example./saproot.root) 3.sh on the database server afterwards. since it needs the new groups. Execute the script saproot.

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

SAP DB: Backing Up the Database
SAP DB

Prerequisites
You have not started to operate the system productively.

Procedure
1. Stop the SAP System as user <sapsid>adm with:
stopsap r3

Note that you have to stop and restart the database. 2. Give the database parameter the value it had before the upgrade. 3. This step depends on the chosen upgrade strategy: a. Strategies A_off and A_switch: Since the log mode is reset to the original value after the upgrade, you must back up the database completely (in operating mode COLD) before you can start the system again productively. b. Strategy A_on: We recommend making a complete backup so that you do not have to upgrade all the logs again in case of a recovery. Instead of a complete backup, you can perform an incremental online backup (save updated pages). This type of backup has the advantage that a recovery is significantly faster. 4. Start the SAP System as user <sapsid>adm with:
startsap r3 End of SAP DB

April 2001

141

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

DB2 Universal Database
DB2 Universal Database

Prerequisites
You have not started to operate the system productively.

Installing and Updating the DB2 Administration Tools
You can install the administration tools in the following steps:

Installation of the administration frontend Install the new administration frontend as described in the BC R/3 Database Guide: DB2 Universal Database. You can install the frontend either during or after the upgrade. These functions are available only after you execute the script saproot.sh.

Creation/update of the administration database To store administration data (for example for log file handling), data is stored on the database server under the SAP database instance in the SAP database and in an additional administration database. The administration database has the name ADM<SAPSID> and is needed to store data while the SAP database is not available (for example during a backup). Log on as user <sapsid>adm and change to the user root with su root (not su root). Execute the following command (depending on your source release): Source Releases 3.0x/3.1x:
sddb6ins -s <SAPSID> -u 31I 46C -

Source Release >= 4.0B:
sddb6ins -s <SAPSID> -u <Start-Release> 46C

This creates the database ADM<SAPSID> with standard contents, if it does not yet exist. Otherwise, the database objects are adjusted to the new release in this database.
sddb6ins exchanges the program userexit that is responsible for saving log files in the log archive directory. The program userexit logs its actions in the database ADM<SAPSID>.

As of Release 4.0A, administration tools such as brarchive, brrestore and userexit do not log their actions at the file system level anymore. Instead, they log the actions in the database ADM<SAPSID>. This means that after the program userexit is substituted, you must use the old program brarchive to manually back up all the log files that have been created up to this point (for source releases smaller than 4.0A). You can find the old program brarchive on the CD SAP KERNEL under the following name:
<CD mount directory>/UNIX/AIX_32/BRARCH31

Activating Log Archiving

142

April 2001

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

If you did not reactivate log archiving for the database with R3up, you must convert the database parameters LOGRETAIN and USEREXIT. To do this, enter the following commands in the DB2 command line:
db2 update db cfg using LOGRETAIN ON db2 update db cfg using USEREXIT ON

You must then perform a complete database backup before DB2 permits new database connections.

Backing Up the Database
Now back up the database completely.

Deleting Substitution Tablespaces
After the upgrade, a number of tablespaces are no longer used and you can delete them. These are always the following tablespaces for a Repository switch: PSAPES<source release>D PSAPES<source release>I PSAPEL<source release>D PSAPEL<source release>I where <source release> is the source release for the current upgrade. To delete a tablespace, enter the following command in the operating system:
db2 drop tablespace <Tablespace_name>

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

Perform an Update Statistics
Proceed as follows: 1. Log on to the SAP System. You require the authorizations for database administration and background jobs. 2. Start Transaction DB13 (planning calendar) or choose
Tools → CCMS → DB Administration → DBA scheduling

3. Open the dialog box with the actions which you can schedule by double-clicking on the current day. 4. Select the action Upd. Statistics + Reorgcheck all tables 5. Choose Start immediately. Confirm the following dialog boxes to start the job in the background.
Runstat_all has been scheduled for the current day and started immediately.

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

April 2001

143

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

6. Check the status of the job with the Job logs option for the current day.

Scheduling Update Statistics Jobs
To schedule update statistics jobs: 1. Log on to the SAP System. You require the authorizations for database administration and background jobs. 2. Start Transaction DB13 or choose:
Tools → CCMS → DB Administration → DBA scheduling

3. In the menu, choose Planning → Planning pattern. Several defined database actions are shown here. 4. Choose the following action:
Check Step, Upd.Statistics + Reorg. check on DBSTATC (daily)

Enter a start time (if possible, when the system is available but the system load is low) and confirm the subsequent steps. 5. Choose the following action:
Upd. Statistics & Reorgcheck all tables (Sun.weekly)

Enter a start time and confirm the subsequent steps.
End of DB2 Universal Database

144

April 2001

SELECT DBNAME.SAP AG Upgrading to 4. Otherwise reorganize the database according to the usual cycle. Backing Up the Database Perform a complete backup of the database. TSNAME. CARD. (NEARINDREF + FARINDREF) * 100 / CARD. CARD. SELECT IXNAME. For information on how to update the statistics. see SAP Note 113008.6C Support Release 2: UNIX DB2 for OS/390: Preparations DB2 for OS/390 Prerequisites You have not started to operate the system productively. The first query checks for overflow conditions or space being filled by dropped tables. IXCREATOR FROM SYSIBM. Switching the ICLI Server At the start of production operation (at the latest in the MODPROFP_<Rel> phase) you are prompted to stop the ICLI server of the source release. and replace it with a target release ICLI server.SYSINDEXPART WHERE (CARD > 0 AND (NEAROFFPOS + FAROFFPOS) * 100 / CARD > 10) The following query specifies indexes that might need to be reorganized. The following two queries specify which tablespaces might need to be reorganized.SYSTABLEPART WHERE ((CARD > 0 AND (NEARINDREF + FARINDREF) * 100 / CARD > 10) OR PERCDROP > 10) SELECT IXNAME. which uses the port indicated by the service entry sapdb2<SAPSID>. (NEAROFFPOS + FAROFFPOS) * 100 / CARD FROM SYSIBM. We strongly recommend that you perform RUNSTATS on all tablespaces. IXCREATOR. These pages cannot benefit from sequential prefetch. PERCDROP FROM SYSIBM. End of DB2 for OS/390 April 2001 145 .SYSINDEXPART WHERE LEAFDIST > 200. SAP recommends that you reorganize any tablespaces and indexes that you find with the following SQL statements. Reorganizing the Database Reorganizing the database at this point in time is optional. The second query checks for rows that are out of sequence. Performing an Update Statistics (RUNSTATS) The system does not update statistics automatically. It searches for leaf pages that are not close together. Only reorganize now if you have enough time.

Backup: Database Was Operated with Backup Mode Deactivated Reactivate the backup mode. 3. Execute this command for both of the dbspaces that you want to delete. start dbaccess as user informix and enter the following SQL command: select count(*) from systables where dbinfo('DBSPACE'. and then create a complete backup of the database.Upgrading to 4. You must make this backup offline.6C Support Release 2: UNIX SAP AG Informix: Preparations Informix Prerequisites You have not started to operate the system productively. End of Informix 146 April 2001 . Otherwise restoring the database may be very time-consuming.partnum) = '<dbspace-name>' and partnum != 0. To delete the dbspaces use the database tool onspaces as follows: onspaces -d <dbspace-name> Before you can use the space freed by deleting the dbspaces. 2. To do this. Backing Up the Database There are two different procedures when you back up the database. Proceed as follows: 1. count(*) = 0 should be the result. Backup: Database Was Operated with Backup Mode Activated Since the amount of logical log files increased during the upgrade. you must make a level 0 database backup. First check that the dbspaces really are empty. Deleting dbspaces The dbspaces psapes<sourcerel> and psapel<sourcerel> (<sourcerel> stands for the source release for this upgrade) are empty after the upgrade. make another complete offline or online backup of the database immediately. depending on whether you have operated the database during the upgrade with the backup mode activated or deactivated. This means that you can delete them.

check whether all the environment variables have been set correctly for sapdba at the UNIX level: SAP Library → Basis Components → Database Interface/Database Platforms → Database Administration (Oracle) with SAPDBA →=Using SAPDBA → Configuring SAPDBA → Environment Variables (UNIX). you must use an editor to enter these parameters in the profile $ORACLE_HOME/dbs/init<DBSID>.sql again. Start the SQL script with: cd $ORACLE_HOME/dbs cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.SQL as SYSTEM.x: UNIX). if it appears: Error accessing PRODUCT_USER_PROFILE Warning: Product user profile information not loaded! You may need to run PUBLD. only the user ora<sapsid> can have DBA authorization in Release 4. If you make backups to a remote tape device (backup_dev_type = pipe pipe_auto pipe_box).5 for creating backups with brbackup. brarchive and brrestore. replace the parameter read_fifo_cmd (no longer supported as of Release 4. You have already performed most of the required manual changes when you migrated Oracle to Version 8.sap.sap (For Source Releases Lower than 4.5A) New parameters are used for in Release 4.x. Log on as user ora<sapsid> at the UNIX level. Proceed as follows: 1.0 (see the guide Migration/Upgrade to Oracle Version 8.sql sapdba_role.6C Support Release 2: UNIX Oracle: Preparations Oracle Prerequisites You have not started to operate the system productively.sql sqlplus internal @sapdba_role <SAPSID> UNIX You can ignore the following error message.5A) with the following parameters: remote_host = <remote_host_name> remote_user = <remote_user_name> April 2001 147 .SAP AG Upgrading to 4. 2. Creating and Updating the SAPDBA Role To ensure the security of your system. This means that you must execute the SQL script sapdba_role.0. If you want to use the new functions of these programs. The upgrade imports additional objects which have to be adjusted. Checking the Environment Variables for the Program sapdba Using the following information on the documentation CD. Adding New Parameters to the Profile init<DBSID>.

5A) So that you can use the Oracle Recovery Manager (RMAN) with brbackup. make a complete offline or online backup of the database as quickly as possible.ora: control_file_record_keep_time = 30 Backing Up the Database The procedure for backing up the database depends on the mode with which you operated the database during the upgrade. 3. you can start up your SAP System again as <sapsid>adm with startsap r3 and continue working.ora (For Source Releases Lower than 4. You can find more information about offline backups and brbackup in the SAP online documentation on database administration for Oracle. Stop your SAP System as user <sapsid>adm with: stopsap r3 2. Proceed as follows: 1. This stops and starts up the database again. add the following new parameter to the profile init<DBSID>. End of Oracle 148 April 2001 . Start the offline backup of the database with the program brbackup. When you have made the backup. Backup: Database Was Operated in NOARCHIVELOG Mode Activate ARCHIVELOG mode again and create a complete backup of the database. This must be done as an offline backup. Activate ARCHIVELOG mode again with sapdba. Backup: Database Was Operated in ARCHIVELOG Mode Since a large number of archives were produced during the upgrade. BRARCHIVE and BRRESTORE. 4.Upgrading to 4. Adding a New Parameter to the Profile init<DBSID>.5 → BRBACKUP. Otherwise restoring the database may be very time-consuming.6C Support Release 2: UNIX SAP AG For detailed information. You can find instructions on doing this under Changing the Database Recovery Mode [Page 205]. see the documentation CD for the target release under SAP Library →=Basis Components → Database Interface/Database Platforms → Database Administration (Oracle) with SAPDBA →==New Features in SAP R/3 Release 4.

Start R3up directly from CD with: /<CD mount directory>/UNIX/<OS>/R3UP readkernel Replace <CD mount directory> with the mount directory of the CD and <OS> with one of the following: AIX_32. HP11_64. HP10_32. April 2001 149 . AIX_64. RLX_64. 3.6C Support Release 2: UNIX Distributing SAP Programs Use If your SAP System has multiple application servers and you do not use NFS to share the kernel directory of the central instance. we recommend that you use NFS to share programs in /usr/sap/<SAPSID>/SYS/exe/run. To keep the network load low. RLX_32.Basis Components →=Client Server Technology → System Services → Setting Up Local Executables on UNIX R/3 Instances. Procedure 1. You can copy the programs directly from the CD SAP Kernel to the target directory of the application server with R3up.SAP AG Upgrading to 4. Shut down the application server. For more information on using sapcpe see Help → SAP Library → BC . DEC_64. Mount the CD. SUNOS_32 or LINUX_32. If you use distributed servers. you can also save the programs locally on the servers and update them automatically with the program sapcpe. HP11_32. you have to distribute the programs in directory /usr/sap/<SAPSID>/SYS/exe/run to all servers. This avoids inconsistent programs and having to distribute them manually. 2.

for example. Prerequisites You had Release 3.x for the first time. This means that you must have an empty system log when you start the system with Release 4. as SLOG<instance_number>. a new one is created when you start the system. On the host with the central instance.Upgrading to 4. 150 April 2001 .0.6C Support Release 2: UNIX SAP AG Renaming the Local System Log (For Source Releases 3. You can achieve this easily by renaming the old system log.1x Only) Use The format of the system log was changed for Release 4. Procedure Rename the file SLOG<instance_number> in the directory /usr/sap/<SAPSID>/<instance_name>/log.0x or 3.0x/3.old. The SAP Kernel cannot correctly interpret entries in the old format. If a log does not exist. R3up has already renamed the central and local system logs.1x before the upgrade. This is not done automatically on the remote application servers. If you use the SAP System with multiple application servers then you have to rename the local system log on these remote servers.

6. 5. Alternatively. Transaction RZ10 checks the profiles of all servers. check the settings in your system profiles with Transaction RZ10. Choose Utilities → Import profiles → Of active servers.6C Support Release 2: UNIX Checking the Profile Parameters with Transaction RZ10 Use After the upgrade.SAP AG Upgrading to 4. 2. choose Goto → Profile values → Of a server. Choose Utilities →Check all profiles → Of active servers. if you want to read the documentation offline from the documentation CD for the target release. choose SAP Library → Basis Components → Computing Center Management System → Computing Center Management System → Profiles. double-click the name of the server you want to display. To display the values. Whenever possible. a. You can display the parameters with their current settings and the default value using Transaction RZ10. you receive a warning. Ensure that all active servers (SAP instances) are started. 4. b. Call Transaction RZ10. For more information about changing the profile parameters. Check the parameters whose values differ from the default. return the parameter values to the default values. Procedure 1. 3. choose Help → Application Help from within Transaction RZ10. If parameters are set incorrectly. Ensure that you have authorization S_RZL_ADM in the SAP System. April 2001 151 . On the initial screen of RZ10.

1x) [Page 155] Adjusting Repository Objects [Page 156] Reimporting Additional Programs [Page 156] Migrating Matchcodes to Search Help Objects (Source Releases 3.0x/3.1x) [Page 167] Installing More Dialog Instances [Page 168] Evaluating the Upgrade Runtime [Page 169] 152 April 2001 .1x) [Page 157] Performing Post-Upgrade Activities for the Language Transport [Page 158] SAP DB: Updating Optimizer Statistics [Page 159] DB2 for OS/390: Actions [Page 159] Informix: Performing an Update Statistics [Page 160] Oracle: Actions [Page 160] Generating ABAP Loads [Page 163] Converting Batch Input Logs [Page 163] Actions for the SAP Online Documentation [Page 164] Performing Post-Upgrade Activities in the Authorization Area [Page 164] Performing Post-Upgrade Activities for the Application [Page 166] Processing Table Clusters After the Upgrade (Source Releases 3.0x/3.0x/3.6C Support Release 2: UNIX SAP AG Actions During Production Operation You can perform the following actions while the system is operating productively: • • • • • • • • • • • • • • • • • • • • Importing SAP Support Packages After the Upgrade [Page 153] Transport Management System: Distributing the Configuration [Page 153] Rescheduling Background Jobs [Page 154] Rescheduling Jobs with Transaction DB13 (Source Releases 3.Upgrading to 4.

Always start with the newest SPAM update. Log on to the system that is configured as the domain controller.6C Support Release 2: UNIX Importing Support Packages After the Upgrade Use To avoid problems with your SAP software. such as the SPAM updates. Call Transaction STMS and choose Overview → Systems. Select the system that has been upgraded and choose SAP System → Update configuration. This applies to Support Packages that cannot be included. This is how you avoid potential problems in your system before they occur. This is also applies after the upgrade. Choose Extras → Distribute TMS configuration. Procedure Import the newest Support Packages. If have not included all the necessary Support Packages during the upgrade. If you want to install additional languages in your SAP System. see Help → SAP Library → Basis Components → Change and Transport → Language Transport. For information on importing a language. Procedure 1. Add-On Support Packages and CRTs. 3. The Support Packages always contain the current language version for text-relevant objects. you can also import them after the upgrade. Transport Management System: Distributing the Configuration Use After an upgrade. April 2001 153 . perform the language import before you import the Support Packages.SAP AG Upgrading to 4. you have to distribute the information about the new release to all systems in the transport domain. 2. 4. we recommend that you import new Support Packages into your system as soon as they become available.

Call Transaction SM37. To release the jobs. If this is the case. Log on as user DDIC in client 000. 154 April 2001 .5: 1. since the report variants will no longer be correct. 4. Result The jobs are released. choose Job → Schedule → Release. you have to reschedule the job. 3.6C Support Release 2: UNIX SAP AG Rescheduling Background Jobs Use Use this procedure to release all background jobs that were locked when you isolated the central instance. As of Source Release 4. 2.0B only: 1.Upgrading to 4. 2. Log on as user DDIC in client 000. Execute the report BTCTRNS2. Find all the relevant jobs. Errors may occur if a background report was changed by the upgrade. Procedure For Source Releases up to and including 4.

0x or 3. Prerequisites • • Your source release is 3. ready. Enter Transaction SM37 in the SAP System. April 2001 155 .1x) Use You deleted all scheduled jobs at the start of downtime.SAP AG Upgrading to 4. released. Procedure 1.0x/3. 4. Select the following jobs: Job name User name Start date from Start date to Only jobs with status DBA* * No entry No entry scheduled. You have already checked that all old DB13 jobs were deleted properly.6C Support Release 2: UNIX Rescheduling Jobs with Transaction DB13 (Source Releases 3. Enter Transaction DB13 and reschedule your jobs. active 3. Delete all the jobs displayed. You can now schedule them again with Transaction DB13 (see also Isolating the Central R/3 Instance). 2.1x.

RLX_64. the contents of directory /usr/sap/<SAPSID>/SYS/exe/run are completely deleted before the new SAP kernel is imported.SAR Replace <CD directory> with the mount directory of the CD and <OS> with one of the following: AIX_32.Changing the SAP Standard → The Modification Assistant → Upgrade Procedure/R/3 Support Packages → Adjusting R/3 Repository Objects.6C Support Release 2: UNIX SAP AG Adjusting Repository Objects Use If you have made modifications to programs. HP11_32. in this directory. Procedure 1. 156 April 2001 . RLX_32. you must adjust these with Transaction SPAU. Reimporting Additional Programs Use During the upgrade. Procedure For more information on modification adjustment. If you installed additional programs such as the RFC library or the CPIC library. DEC_64. SUNOS_32 or LINUX_32.Upgrading to 4. you have to install them again from the CD Presentation. Log on as user <sapsid>adm. After you have completed the upgrade you have a maximum of 14 days to execute Transaction SPAU without a key check (SAP Software Change Registration) for the objects that you changed. 2. screens or interfaces (GUIs). Enter the following commands: cd /usr/sap/<SAPSID>/SYS/exe/run /<CD dir>/SDK/UNIX/<OS>/SAPCAR -xvf \ /<CD dir>/SDK/UNIX/<OS>/<additional package>. see the documentation CD for the target release under Help → SAP Library → Basis Components → ABAP Workbench → BC . AIX_64. HP10_32. HP11_64.

SAP AG Upgrading to 4. April 2001 157 . Conversion Program.6C Support Release 2: UNIX Migrating Matchcodes to Search Help Objects (Source Releases 3.1x.0x/3. Procedure Use Release Note Migration of Matchcodes to Search Helps to check if manual post-upgrade activities are necessary. in the SAP System choose Help → Release Notes → Complete list from Rel.0 → 40A → Basis Components → ABAP Workbench → ABAP Dictionary → Activation Program. DB Utility. During the upgrade.1x) Use As of Release 4. Prerequisites Your source release is 3. SPDD → Migration of Matchcodes in Search Helps.0x or 3. These exceptions are listed in the Release Note DDIC40_MC_MIGR Migration of Matchcodes to Search Helps. Only in exceptional cases do you need to perform postupgrade activities manually. If you have already installed the current online documentation. MC.0 the ABAP Dictionary objects help views and matchcodes are replaced by the new ABAP Dictionary object search help. You can find this Release Note offline on the documentation CD. 4. the matchcodes are migrated largely automatically to search helps.

use the following procedure to copy the data from the container tables to the database tables. so execute it in the background.6C Support Release 2: UNIX SAP AG Performing Post-Upgrade Activities for the Language Transport Use To reduce downtime during the upgrade. This report may take a long time to execute. Procedure Use the report RSTLAN_AFTER_UPGRADE to copy the data. some data from the language CDs was only imported into container tables. Prerequisites You have imported a language during the upgrade. This data includes glossary and terminology data. There are no input parameters. 158 April 2001 . If you want to use a glossary or terminology in your system. depending on the number of languages you have imported. You are using a glossary or terminology in your system.Upgrading to 4. The contents of the container tables are then deleted. and not yet imported into the actual database tables of the system. The report unpacks the contents of the container tables and copies the data to the corresponding database tables.

Do this with the report program RSDB2CLN. End of SAP DB DB2 for OS/390: Actions DB2 for OS/390 Removing Any Superfluous Database Objects Check if there are any empty database objects such as tablespaces. Log on to the SAP System. 4. 3. Select Create new optimizer/space statistics. End of DB2 for OS/390 April 2001 159 . The menu for scheduling database actions appears. Select a day in the Planning Calendar by double-clicking. Procedure 1. In the role SAP_BC_DB_ADMIN_SAPDB. databases and stogroups. Plan this action as soon as possible.SAP AG Upgrading to 4. to avoid a drop in your system performance. delete them.6C Support Release 2: UNIX SAP DB: Updating Optimizer Statistics SAP DB Use To improve the response of the database after the upgrade. If there are. you must update the optimizer statistics. 2. call Transaction DB13.

Use the sapdba program to delete the tablespaces. the space is actually released You may be asked whether you want to wait until Oracle releases the files.6C Support Release 2: UNIX SAP AG Informix: Performing an Update Statistics Informix Use To improve the response of the database after the upgrade. 160 April 2001 . Procedure Enter the following commands as user informix: su . some tablespaces are empty and are no longer used. the tablespace is empty 2. This applies to the following tablespaces in a Repository Switch upgrade: PSAPES<source release>D PSAPES<source release>I PSAPEL<source release>D PSAPEL<source release>I where <source release> is the source release for the current upgrade. you must execute an Update Statistics as user informix. You can delete these tablespaces.informix /usr/sap/<SAPSID>/SYS/exe/run/ sapdba -updstat End of Informix Oracle: Actions Oracle Deleting Tablespaces After the upgrade.Upgrading to 4. The program sapdba checks whether: 1.

The runtime depends strongly on the size of your database and can take several hours. When you run the database in rule-based mode you significantly reduce the performance of the system. If the user system does not have the default password manager you need to append the following command options to the end of the sapdba calls: -u system/<password> Call the sapdba program with the following command: sapdba -analyze DBSTATCO You can do this during production operation. Proceed as follows: 1.1x) You must switch the database optimizer to cost-based mode after the upgrade. sapdba executes the Drop command on the database and deletes the data files at the operating system level.0x/3.x.6C Support Release 2: UNIX Delete the tablespaces as follows: 1. see the following documentation on the documentation CD for the target release under: • SAP Library → BC . For background information on this subject. 4. System performance is reduced considerably during this time.SAP AG Upgrading to 4. You can make this switch during production operation.Basis Components → Database Interface/Database Platforms → Database Administration (Oracle) with SAPDBA → Using SAPDBA Read about the following topics there: − − • Support for the Cost-Based Optimizer SAPDBA Command Options SAP Library → Basis Components → Computing Center Management System → Database Administration in CCMS → SAP/Oracle DBA in CCMS → CCMS Support for the Cost-Based Optimizer: Oracle Switching the Optimizer Mode (For Source Releases 3. Enter the name of the tablespaces you want to delete. SAP no longer supports the parameter setting optimizer_mode = rule after the upgrade to 4. Choose Drop tablespace. Actions for Cost-Based Optimizer Mode The following text only describes the actions for the database optimizer that you need to perform directly after the upgrade. The cost-based optimizer requires table statistics to be created. 3. Check the success of the action with one of the following options: April 2001 161 . Choose Tablespace administration. 2. Start sapdba at the operating system level as user ora<sapsid>. If the tablespace is empty.

The Optimizer must be set to cost-based mode. you can analyze the cause by double-clicking the log line and pushbutton SAPDBA Detail Log in the menu above. Scheduling Periodic Statistics Updates (For All Source Releases) Make sure that the statistics are updated at regular intervals.ora: optimizer_mode = choose db_file_multiblock_read_count = 8 3. send a problem message and the log file to SAP. Restart the database to activate the parameters. see the online documentation under Help → Application help. Make sure that the following parameters are set in the file $ORACLE_HOME/dbs/init<SAPSID>. your database is already running in cost-based optimizer mode. End of Oracle 162 April 2001 .x before the upgrade. If you cannot solve the problem yourself. Correctly created optimizer statistics are essential for the performance of your system.opt If there are errors. Updating the Statistics (For Source Release 4.6C Support Release 2: UNIX SAP AG − − In the SAP System. Friday/Saturday night): sapdba -checkopt PSAP% (for example. make sure that the return code is either 0 or 1 by choosing: Tools → CCMS → DB Administration → Operations Monitor Check the logs in the file system if necessary. After the upgrade you only need to update the statistics. System performance is reduced considerably during this time. $ORACLE_HOME/sapcheck/*.aly or *.Upgrading to 4. 2. For more information on DB13. Schedule the following two phases periodically once the database has been in operation for one day following the upgrade: Phase I Phase II (for example.x) If you had Release 4. If the user system does not have the default password manager you need to append the following command options to the end of the sapdba calls: -u system/<password> Call the sapdba program with the following command: sapdba -analyze DBSTATCO You can do this during production operation. Saturday/Sunday night): sapdba -analyze DBSTATCO You can schedule these actions with transaction DB13.

However. Selection of software components to restrict the amount of objects being generated (SAP_ABA. Transaction SGEN offers the following functions: • • • • Selection of predefined generation tasks. Prerequisites Your source release is lower than 4. however.6C only supports the new batch input log procedure. Converting Batch Input Logs Use Release 4. Choose Regenerate after an SAP System upgrade.SAP AG Upgrading to 4. This may.6B. reduce production system performance. you can use transaction SGEN to generate the missing loads. or in the Job Monitor by choosing Job Monitor. there are not yet any generated ABAP loads for all the transactions from the different SAP application areas.6C Support Release 2: UNIX Generating ABAP Loads Use The most important ABAP loads for the Basis system are upgraded with the new release. April 2001 163 .6A. Procedure For an exact procedure and other information.6A or 4. To avoid this. see SAP Note 186066. For a detailed description of the features. a load is automatically generated. SAP_BASIS and so on) Generating in the background Job Monitor for checking the progress of the generation in the background Procedure If possible. generate the loads directly after the upgrade. see the online documentation in transaction SGEN by choosing Information on the SAP Load Generator. otherwise the system will no longer be able to read them. For more information on the free space requirements in the load tables. see Note 175596 in SAPNet – R/3 Frontend. or you have not yet converted your logs in Releases 4. if it does not already exist. When you call a program. The old log files are deleted after a successful conversion. All old batch input logs must be converted with the program RSBDCLCH in all clients.

1G. You can use it to: • • Deactivate checks within a transaction Define proposals for the profile generator for activated checks Both the check flags and the proposed values are based on SAP default values.1G: To copy the latest SAP default values while retaining your own modifications. For source releases as of 3. use Transaction SU25 (steps 2 and 3). You can change these values with Transaction SU24. see the guide Installing the SAP Library. Only for help type PlainHtmlHttp: Set up the Web server 3. use Transaction SU25 (step 1). Maintain the settings variants for the Online Help in the IMG 4. 164 April 2001 . This transaction • • displays the differences between your own check flags or authorization proposals and the new SAP default values for all the changes by SAP defines all the roles which will have to be generated later on using the profile generator in order to generate authorizations for all the current checks For more detailed information. see the online documentation for Transaction SU25.6C Support Release 2: UNIX SAP AG Actions for the SAP Online Documentation Process Flow Certain actions are necessary before you can display the online documentation (SAP Library) in your SAP System: 1.Upgrading to 4. Installation of a Web browser/viewer For instructions. For source releases before 3.1G: To copy the SAP default values. Performing Post-Upgrade Activities in the Authorizations Area Procedure Adjusting the Assignments Between Check Flags and Transactions Transaction SU24 was introduced in Release 3. Installation of the online documentation 2.

Release 3. For Source Release 3. April 2001 165 . Composite profile SAP_NEW contains all the individual SAP_NEW_<Rel> profiles since Release 2. It contains the authorizations only for new checks in functions that were already delivered. This is how the composite profile is also given the overall authorization for the check S_TCODE (exists since Release 3. Choose User names → Change.CPIC and save. Assign user SAPCPIC (in the clients in which it exists) profile S_A.0D Only: New Authorization Check when Starting all Transactions For security reasons. If this is not the case.1C. The profile SAP_NEW does not contain the authorizations for functions delivered in the upgrade. In a later phase you can begin to assign special profiles with exactly the transactions to be executed by the users.6C Support Release 2: UNIX For Source Release 3. Enter the authorization profile S_A. To do this. where <rel> is the release for which the new authorization check was delivered. remove the single profile SAP_NEW_<rel> from the composite profile SAP_NEW. This defines which users can continue to carry out the corresponding actions. Before this. To do this.6A. into which customer profile the authorizations should be copied.CPIC . The composite profile SAP_NEW contains all single profiles SAP_NEW_<Rel> (as of Release 4. you can temporarily enter the profile SAP_NEW for all users with Transaction SU01. Upwards Compatibility for Authorization Checks There are functions that are protected in more detail by new authorization objects in the new release.0E contains a new authorization check against authorization object S_TCODE when starting all transactions.1E).0D Only: User SAPCPIC Must Be Assigned the Profile S_A. Keep the single profiles SAP_NEW_<rel>. so that you can find out later which authorization appeared in which release. than was previously the case. go to Transaction SU01 and enter the user SAPCPIC. The authorizations for these new objects are in the single profiles SAP_NEW_<rel> . which they were able to carry out previously without an authorization check.SAP AG Upgrading to 4. This has made it necessary to assign new authorizations (see Release Note BC_30E_AUTHORITY). This guarantees that users can continue to carry out those functions after an upgrade. Ensure that all the users have authorization profile SAP_NEW so that they can still start transactions.CPIC New authorization checks were introduced in the interface from the SAP System to the operating system. Empty and activate the profile SAP_NEW after finishing the analysis and maintenance. To do this. the naming convention S_NEW_<rel><number> is valid). which is used for internal purposes and which in the past did not need any authorizations. Every user should have the profile SAP_NEW in his or her master record. delete all the individual profiles from SAP_NEW that refer to releases that are lower than the source release for the upgrade. This also has an effect on user SAPCPIC. After the upgrade the user administrator should go through the profile SAP_NEW and decide for each authorization object. choose Environment → Mass changes.

the predefined buffer size might not be large enough for the newly delivered profiles. see Note 10187.6C Support Release 2: UNIX SAP AG Handling Problems with User Buffers If the user master records were already very large before the upgrade. If you encounter authorization problems after the upgrade where authorizations are missing for users although these are contained in the master record. Performing Post-Upgrade Activities for the Application Use Some applications require specific post-upgrade activities without which the application cannot execute. HR Customers Only: Restoring Table T512W (Wage Types in HR) If you saved table T512W before the upgrade. For SAP Retail Customers Only: Replacing Short Texts You are advised to replace short texts for some languages. You can create a release-specific view of a Customizing project by choosing the activities for delta or upgrade Customizing. You can make the necessary Customizing settings in the release-specific Customizing project by calling Transaction SPRO. Procedure These actions are described in the Release Notes for the particular application. see the Online Documentation under Help → SAP Library → Logistics → SAP Retail → Basic Principles → Retail Terminology. The precise procedure is described in the section Backing Up Wage Types in HR (T512W) [Page 103]. reload it now.Upgrading to 4. Also check to see if you have to adapt your Customizing. For more information. To do this call Transaction SPRO_ADMIN or choose Tools → AcceleratedSAP →Customizing →Project Administration. 166 April 2001 .

choose the function button F1.0x/3. If they do not. the estimated time for the remaining data transfer appears automatically. choose Control → Data transfer → Start. Procedure 1. Read the online documentation. You now have the option of selecting tables and starting the process in the background.6C Support Release 2: UNIX Processing Table Clusters After the Upgrade (Source Release 3. As soon as the tables have the status Done. Prerequisites Your source release is 3. Since there is often a large amount of data to handle. To start the data transfer. You will not be able to start the upgrade. If you have not. switch to the new tables. the table clusters EDIDOC and CDCLS are converted from Release 3. the tables EDIDOC and CDCLS must have the status Conversion. choose Control → Switch (STRG+F2). To do this.x. 4. April 2001 167 . After a while.0x or 3. The time when you process the table clusters is not critical. choose Control → Delete entry. you can delete them from the list. For more information on the individual fields.1x) Use After the upgrade. you can use transaction ICNV to convert the table clusters during production operation of the system.SAP AG Upgrading to 4.x to Release 4. You can then select the tables you want to delete and remove them from the list. PREPARE warns you about any outstanding conversions. 5. Any data that has not yet been transferred is included in the process. Directly after the upgrade.1x. Call transaction ICNV. To do this. Monitor the progress of the action. 3. You must complete step 5 before you start the next upgrade. This considerably reduces the downtime during the upgrade. but it must be done before you begin the next upgrade. 2. End the conversion. create a problem message under the component BC-UPG-TLS. When at least 95% of the data has been converted.

Procedure Proceed as described in Note 137478 Installing a Dialog Instance/Gateway .Upgrading to 4.4. 168 April 2001 .5B.6C Support Release 2: UNIX SAP AG Installing More Dialog Instances Use You can use the SAP tool R3SETUP to install more dialog instances in an SAP System.

Check if the SAPNet . Choose Program → Execute and print. only those phases which have a significant effect on the runtime are displayed. Result The report writes data into a log file and generates a list approximately two pages long.R/3 Frontend. choose Display data. If you have a connection to the SAPNet . If you keep the default settings. The procedure is very simple: 1. If you do not yet have a link to the SAPNet . 2. The data was formatted previously using RSUPGSUM.R/3 Frontend connection exists. To display the data to be transferred. you can fax the RSUPGSUM list to us at: SAP AG Software Logistics department Fax number + 49 6227/7 46495 April 2001 169 . Prerequisites You are logged on to the SAP System. 2. Procedure 1. Send the results of the report to SAP for further analysis. for example. 3. Choose Transfer data.SAP AG Upgrading to 4. you can send this data electronically. 3. 4. Choose Customizing and select that at least the option Run time results of completed upgrades and return to the previous screen. Execute the program RSUPGSUM using Transaction SE38.RTS in the subdirectory log of the upgrade directory which R3up automatically creates after the upgrade. Call Transaction SCUI.6C Support Release 2: UNIX Evaluating the Upgrade Runtime Use You can use the report RSUPGSUM to display the upgrade runtime.R/3 Frontend. Enter the relevant information. 4. The times are displayed in the file R3up. Enter the time required for modification adjustments. database size.

170 April 2001 . Request the Notes [Page 40] that are relevant to this upgrade.R/3 Frontend Notes.6C Support Release 2: UNIX SAP AG Troubleshooting • Logs − − Upgrade Logs [Page 171] Analyzing the ELG Log Files [Page 173] • Correcting Errors After Phases − − − − − − − − Correcting Errors in the ACT Phase [Page 175] Correcting Errors in the ADOIM Phase [Page 176] Correcting Errors in the XPRAS Phase [Page 177] Cleaning Up Terminated Conversions in the DB Conversion Phases [Page 179] Correcting Lost Fields Problems in the PCON Phase [Page 182] Correcting Conversion Errors in the PCON Phase [Page 183] Correcting Errors in the Job Phases [Page 184] Correcting Entries from the INITPUT and INITSUBST Phases [Page 185] • General Problems − − − − − − − − Preparing the Restart of the Upgrade After a System Failure [Page 186] Resetting the Upgrade [Page 187] Scroll Mode: Restart [Page 191] Correcting Problems when Processing ABAP Steps [Page 192] Correcting Problems when Starting the SAP System [Page 193] Correcting Problems when Copying SAP Programs [Page 194] Correcting Administrator Profile Problems on Application Servers [Page 195] Providing SAP Local Support with Information [Page 196] As well as the problems listed here. also read the SAPNet .Upgrading to 4.

Functions R3up records all actions in the log file R3up.6C Support Release 2: UNIX Upgrade Logs Use R3up logs all actions in log files. To do this. open another terminal window and execute the following command: tail -f <upgrade directory>/log/SLOG46C Each tp-driven phase is divided up into a number of different steps whose start and end times are noted in the SLOG log. where you can also monitor them with tail -f. The start and end of a phase are indicated by the lines START put and STOP put. You can use these log files to monitor your upgrade. If you encounter any errors you can analyze them to help you find a solution. The section in the SLOG relating to phase ACT_46C looks like this: START START STOP START STOP START STOP START START STOP STOP START STOP START STOP START STOP START STOP STOP put tpsetstopm tpsetstopm tplock_eu tplock_eu tpsapstart tpsapstart DD ACTIVAT tp_getprot tp_getprot DD ACTIVAT locksysX locksysX tpsapstart tpsapstart locksys locksys tpdequeue tpdequeue put Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A Q1A ( ( 3 3 A A { { 3 3 | | 0000 19940905200903 19940905200903 19940905200903 19940905200903 19940905200904 19940905200904 19940905200935 19940905200936 19940905200936 19940905202559 19940905202559 19940905202559 19940905202559 19940905202600 19940905202631 19940905202631 19940905202631 19940905202631 19940905202632 19940905202632 q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm q1aadm hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 hs0102 Additional detailed logs are also written for most steps.SAP AG Upgrading to 4. These are in the tmp subdirectory of the upgrade directory. After the various steps of the April 2001 171 . A simple method of monitoring the progress of all tp-driven phases is to observe the SLOG log using tail.log in the subdirectory log of the upgrade directory. Additional detailed logs are usually written for these tp steps. The tp steps are also listed in the file SLOG46C in the subdirectory log of the upgrade directory.

it displays all the logs for a specific transport request. you only need to check these summaries. a description of the error is displayed. their log names.<SAPSID> SAPD??????. If no errors occurred. After completing each tp-driven phase. R3up creates a summary of all individual logs in this phase. You can do this by executing program RDDPROTT with Transaction SE38.ELG (for example.<SAPSID> PL<DATE>.<SAPSID> DS<DATE>. The logs are broken down into several levels.<SAPSID> PD<DATE>. 172 April 2001 . A brief overview of all the logs existing for this transport request is displayed. When you double click an error line.6C Support Release 2: UNIX SAP AG phase have been completed.<SAPSID> PA<DATE>. At level 1 only the return code for the step is displayed. which means. any errors which occurred and the return codes.ELG).<SAPSID> N<DATE>.<SAPSID> Program executing the step R3trans R3trans SHADOW_IMPORT DD IMPORT (H) DD ACTIVATION (A) DISTRIBUTION OF DD OBJECTS (S) TBATG CONVERSION OF DD OBJECTS (N) tpmvntabs ABAP program (RDDMASGL) ABAP program (RDDDIS0L) ABAP program (RDDGEN0L) tp MAIN IMPORT (I) tpmvkernel (C) TBATG CONVERSION OF MC OBJECTS (N) IMPORT OF SELFDEFINED OBJECTS (D) VERSION UPDATE (V) EXECUTION OF REPORTS AFTER PUT (R) R3trans tp ABAP program (RDDGEN0L) ABAP program (RDDDIC1L) ABAP program (RDDVERSL) ABAP program (RDDEXECL) Once the logs are located in the subdirectory log of the upgrade directory. enter the name of the transport request (for example.<SAPSID> SAPH??????. you branch to the log display for the step in question.<SAPSID> SAPV??????. SAPK46CD01) and then choose Execute. The names of the summaries usually comprise the phase name (without the underscore) and the extension . tp moves the individual logs to the subdirectory log of the upgrade directory. The summary contains the names of the individual logs.<SAPSID> C<DATE>.<SAPSID> SAPI??????.Upgrading to 4. DDIC46C. In the field Transport request. The table below contains the most important steps.<SAPSID> P<DATE>. you can also display them in the SAP System.<SAPSID> SAPR??????.<SAPSID> SAPA??????. RDDPROTT works based on transport requests. and specifies which programs carried out the steps: Step Log name SAPK??????.<SAPSID> N<DATE>. If you double click one of the lines. You should check at least level 2 to display any error messages this level may contain.

If a return code is greater than or equal to 12.ELG log to find out why the phase terminated: No errors have occurred if a return code less than 8 appears in the log at the end of a step. Enter the following commands to lock the SAP System again: cd /usr/sap/put/bin . If tp or R3trans have terminated. The job overview normally displays one canceled job and one background job that completed normally. Make sure that the date in the SM37 input screen is correct and that an asterisk (*) appears in the Start after event field. 2. you must analyze the job log in the SAP System to determine the cause of the error. Log on as user DDIC and call transaction SM37.ELG log files are summary log files that contain a list of all the errors that occurred during a specific phase of the upgrade. for example).SAP AG Upgrading to 4. Double-click the canceled job to display the log. Procedure 1. you can call up detailed log files that contain more information. For a chronological list of the files in both log directories. The name of this log is listed in the header of each phase step. From these files. the SAP System may block the logon.. Determine when the program terminated from the last two lines of the SLOG log.exe/tp locksys <SAPSID> April 2001 173 . If you use a user ID other than DDIC to log on to the SAP system and correct the error.6C Support Release 2: UNIX Analyzing the ELG Log Files Use The <PHASE>. Errors have occurred if the return code is equal to 8 and preceded by error messages or if the return code is higher than 8. and no error messages appear for that step. using the detailed log file if necessary.. 4. Enter the job name as the name of the report that usually processes the terminated step (RDDMASGL for DD ACTIVATION. Analyze the errors. R3up displays an appropriate message and prompts you to repeat that phase. When errors are detected during a phase. then tp or a program called by tp has terminated. Double-click the error line to display the long text for the error. In this case.exe/tp unlock_eu <SAPSID> Log on to the SAP system and correct the error. proceed as follows: Enter the following commands to unlock the SAP system: cd /usr/sap/put/bin .exe/tp unlocksys <SAPSID> . analyze the last log that was written.. enter the following commands: ls -ltr <upgrade directory>/log ls -ltr <upgrade directory>/tmp 3. If a background step in the SAP System terminates. First check the <PHASE>.

R3up does not require a password. In this case. When you choose ignore. Remove all errors to avoid the risk of follow-on errors.Upgrading to 4. contact SAP Local Support. R3up prompts you to enter a password if the errors are serious. SAP Local Support also gives you the password that you need to correct the error. since the transport control program tp automatically starts from the point at which it terminated. repeat the phase by selecting repeat in R3up. otherwise the phase is complete. you must always remove the cause of the error. Generally. Once you have found and corrected the error.. A return code of 8 indicates that some individual objects have not been processed or not been processed completely. A return code of 8 indicates that some errors have occurred./exe/tp lock_eu <SAPSID> 5. Result In some exceptional cases.6C Support Release 2: UNIX SAP AG . In this case. The repeated phase is usually completed quickly. you can choose ignore in R3up to continue with the upgrade and avoid repeating the failed phase. 174 April 2001 . you must get approval to ignore the error from SAP Local Support. If you are not sure how to proceed.

. all error messages with return code 8 are ignored. 5. Choose Release 3. April 2001 175 . This procedure tells you how to remove these errors. Log off the SAP System. If you choose ignore severe errors. 3. Enter the following command: cd <upgrade directory>/bin . 2. as described under Prerequisites.SAP AG Upgrading to 4. Prerequisites Before you can correct ABAP Dictionary objects that cannot be activated. Make the required corrections.. you can proceed with the upgrade where it terminated in the ACT_<rel> phases by selecting repeat in R3up.exe/tp unlocksys <SAPSID> Procedure 1.for setting the system → Set System Change Option → All objects (w. 6. lock it again with the following command. → Modifiable 4.. 7. 8. Return the system change option to its previous value. error messages with return code 8 might occur during the ACT_<Rel> phase.x: Administration → Set System Change Option → Global setting. If you had to unlock the SAP System. Proceed as follows: 1. Log on as user <sapsid>adm. Call Transaction SE03..x: Expert tools → .exe/tp locksys <SAPSID> Result When you have manually corrected all the error situations displayed for the objects. Log on as a user other than DDIC. The user DDIC cannot make any changes to the SAP System. 2. cd <upgrade_directory>/bin. you might need to unlock the SAP System.. Workbench Organizer) Release 4. Log on to the SAP System as user DDIC..6C Support Release 2: UNIX Correcting Errors in the ACT Phase Use If your SAP System has been modified.

R3up gives you two options for continuing the upgrade: • • repair severe errors ignore all errors Procedure Choose repair severe errors. Result • If you choose repair severe errors. you must have approval from SAP Local Support. • 176 April 2001 . The errors must be removed after the upgrade. You require a password for ignore all errors.6C Support Release 2: UNIX SAP AG Correcting Errors in the ADOIM Phase Use If your SAP System has been modified.Upgrading to 4. R3up goes to the next phase without dealing with the rest of the objects. If you choose ignore. The objects with errors are not imported into the SAP System. If you choose ignore all errors. R3up repeats the phase and ignores all error messages with return value 8 (eight). Before you can choose ignore. error messages with return code 8 may occur during the ADOIM_<rel> phase.

In the log XPRAS<Rel>. Procedure Finding Help Texts for Error Messages 1. 5. The help text helps you correct the error. You can display a detailed help text for each of these error messages in the SAP System. 2. 2. 4. This file contains error messages with the following header: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ XPRA ERRORS and RETURN CODE in <file name> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If this header is followed by lines other than the return code. Log on to the SAP System. repeat the upgrade phase with R3up. To navigate to the log display for this step. The error messages will generally be visible as of the second level. When you have corrected all the errors. 3. To display the individual transport logs. 6. double-click the line Exec after put. a separate line indicates the names of the reports that generated the preceding error messages. The name of the relevant transport request can be derived from the two names.ELG log. Call transaction SE09.SAP AG Upgrading to 4. You can expand the log to view it in more detail. Choose Request/task → Display individually and enter the name of the transport request. In addition to the actual error lines. see the documentation on the report.6C Support Release 2: UNIX Correcting Errors in the XPRAS Phase Use If errors occur during the execution of XPRA reports in the XPRAS_<rel> phase.ELG look for the file name <file name> displayed in the heading. 3.ELG file is important for finding help. To access this information. choose Goto → Transport logs. If you need more information.<SAPSID> where <ID> can be any string of six characters. log April 2001 177 . position the cursor on the error message and choose Long text. The file name always has the following format: SAPR<ID>. R3up stops and informs you that all errors which occurred have been recorded in the XPRAS_<rel>. Correcting Errors 1. Replace the ‘R’ with a ‘K’ and delete the period and all characters that follow it. then errors have occurred while the reports were being executed. You now have SAPK<ID> as the name of the transport request. These texts usually contain all the information you need to correct the error. Follow the instructions in the help text precisely. or if the report still results in errors after repeating the XPRAS_<rel> phase. The file name <file_name> given in the heading of the XPRAS_<rel>. To display a help text.

R3up repeats the phase and ignores all error messages with return code 8.6C Support Release 2: UNIX SAP AG on to the SAP System. This documentation is always available in English and German. If you cannot execute an XPRA later and still want to skip it. You require a password for ignore all errors. you must suppress the execution of the corresponding report before you repeat the upgrade phase. 4. The errors must be removed after the upgrade.Upgrading to 4. for example. To do this. you must have approval from SAP Local Support. see SAP Note 122597. R3up gives you two options for continuing the upgrade: • • repair severe errors ignore all errors Choose repair severe errors. you can correct some errors that occur during the execution of XPRA reports after you have completed the upgrade. The objects with errors are not imported into the SAP System. If you choose ignore. After the upgrade. However. R3up then continues with the next phase. For technical instructions on skipping an XPRA. when special measures in the SAP application areas are necessary to correct the errors. Before you can choose ignore. Call transaction SE38 and display the documentation for the report that is named in the error log. correct the error and run the report manually using transaction SE38. Correcting Errors After the Upgrade We recommend correcting errors as soon as they are detected. without executing the following XPRAs. if an SAP Note tells you that this is allowed). Only skip an XPRA report program if you are sure you can execute it later (for example. 178 April 2001 . This option makes sense. contact SAP. and the corresponding specialists are not available right now.

If both messages appear. Check the meaning and status of the table. Sometimes there are test tables which are no longer needed. Also check if the table contains the data you expect. CNV_CHK_XT and CNV_CHK_SW. This prevents the conversion being continued automatically. for example. b. Ask the last person who changed a table or to the table owner to find out its status.5A) is harmless in this case. choose Object log. You can see the detailed display for a particular table by double-clicking. 3. Contact your Basis consultant or SAP Local Support for assistance with saving this data. but ends abruptly. A list of the terminated conversions appears. Any data which is still in the temporary table is lost during the next conversion. In some cases. You could encounter the following problems here: a. If the data does not exist. it could still be in the temporary table. Continue with step 4 (Continuing the conversion to the end). Find out if the table is still needed. 2. choose the function Cancel adjustment in the detailed display (Unlock table as of Release 4. The function Cancel adjustment (Unlock table as of Release 4. The table itself does not return to a consistent status. process the message Restart logs of DB conversions found first. You can determine the status of the table with the function Check → Database object and Check → Runtime object. however. This shows that the conversion process was stopped by an external event.5A). If you find out that the table is still needed. CNV_CHK_IMP.SAP AG Upgrading to 4. If the table is no longer needed. The log does not contain an error message. You can do this with Transaction SE16. You cannot find a log because it was deleted at some time in the past. Look for error messages that explain the cause of the termination. proceed as follows: 1. You can now use Transaction April 2001 179 . Procedure for Restart Logs of DB Conversions Found To clean up terminated conversions indicated by the message Restart logs of DB conversions found. Determine the cause of the error. the table was already corrected without the reset log being deleted.6C Support Release 2: UNIX Cleaning Up Terminated Conversions in the DB Conversion Phases Use These errors are indicated by the following PREPARE and R3up error messages: • • Restart logs of DB conversions found Outstanding DB conversions found These errors can occur in the phases CNV_CHK_GEN. Start up the database utility (Transaction SE14) and choose DB requests → Terminated.

if the log clearly gives a reason for the error. You now have two possibilities: a. 4. b. Check the meaning and status of the requests. you must correct it. b. Ask the last person who changed the object if the request should still be processed. A log now exists. views and matchcode objects.6C Support Release 2: UNIX SAP AG SM21 to read the system log to find out the approximate time of termination. proceed as follows. The objects are thus removed from the work list of the conversion program. If. However. Continue the conversion to the end. Since you do not know how long this will take. proceed as follows: Process this message after you have processed the message Restart logs of DB conversions found. In contrast to the procedure for the message Restart logs of DB conversions found. select the request and choose the function Delete selected. but has not yet been processed. Repeat the analysis from step 3 (Determining the cause of the error). and there is a success message in the object log. choose the processing type Background. In the detailed display. Determine the objects that are affected. If the user does not want this. They might not even have been started. The conversion terminates again. contact a Basis consultant or SAP Local Support. 2. Do not remove requests from the last upgrade. 3. and to look for the cause of the error. after several attempts. Process the outstanding requests. a. c. Procedure for Outstanding DB conversions found To clean up terminated conversions indicated by the message Outstanding DB conversions found. You can see this because the error message disappears. the Check function does not display any further problems. you still cannot complete the conversion. The conversion finished successfully. this procedure can also include requests for indexes. a. The requests which are found do not always have to be terminated. b. execute the function Continue adjustment. Choose the function All requests. 1. Choose DB requests → Created with import.Upgrading to 4. 180 April 2001 . This displays the worklist that was not processed correctly during the last upgrade. You now see the worklist of the conversion program. Start up the database utility (Transaction SE14) and choose DB requests → Mass processing. This worklist was generated by developments or modifications in your SAP System.

Schedule the request. or continue it. a.6C Support Release 2: UNIX You can select the requests from the list of mass processing requests and schedule a job for execution with the function Schedule selections. Since you do not know how long this will take. b.SAP AG Upgrading to 4. April 2001 181 . choose the processing type Background. Go to the detailed display of the object by double-clicking it in the list of requests created by the import.

Also read Note 73999. If you do not want to keep the fields name in the log. The log therefore might contain the following message: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lost fields. you must insert them in the ABAP Dictionary. Normally. For this reason. If table BSEG is specified. do not choose suppress. since conversion is only possible on database systems that allow a table to contain more than 254 fields.. a further check is made in phase PCON_<rel>. a. conversions could take a very long time.6C Support Release 2: UNIX SAP AG Correcting Lost Field Problems in the PCON Phase Use Transaction SPDD cannot find all the modifications to the standard and make the relevant decisions.. b.<SID>. customer extensions to the standard are lost and indexes or views can become inconsistent. continue the upgrade with do not repeat check. Procedure 1.Upgrading to 4. Then activate the corresponding table. Read the information in Note 73999. Also read Note 24864. 182 April 2001 . If you want to keep the fields named in the log. 2. table BSEG is so large that you should avoid converting it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2WETG450 Table <name> is losing customer fields.. In addition. tables that cannot be converted and RETURN CODE in FDSAVPRT. Recommendation: Insert the lost fields in the identical positions before continuing. Analyze the log FDSAVPRT. although it did not appear in SPDD In this case. The transaction does not recognize any modifications that were already made without the correction system.

To do this. 2. is incorrect since the relevant table field is missing. you decided to return to the standard definition of the table (using Transaction SPDD) and this additional field was removed. there will be errors when the objects are created. If necessary. however. you can use Transaction SE11. you could. 3. see Note 177680. are already detected by the system before a command can be given to the database. b.SAP AG Upgrading to 4. In phase ACT_<rel>. A field was added to an SAP table. In the above example. This type of error frequently occurs if you decide to revert to the SAP standard during Transaction SPDD (ACT_<rel> phase). for example. April 2001 183 .6C Support Release 2: UNIX Correcting Conversion Problems in the PCON Phase Use This procedure enables you to correct problems that occur in phase PCON_<rel>. The errors can roughly be divided into two classes: • Technical problems on the database You can recognize these in the SysLog (Transaction SM21) since they are marked with SQLERROR followed by an abbreviation with an error number. tablespaces or dbspaces. extend.ELG. however. The index or view definition. remove the deleted field from the index or view definition or re-insert the deleted field into the table. Analyze the log PCON_<rel>. Remove the cause of the error. Procedure 1. • Logical errors in the object definition These could also appear in the form of SQL errors. a. This field was also used in an index or view. Some of them. Technical problems on the database Read the documentation in the database system about how to correct the error. and the ACT_<REL> phase was completed with ignore. For more information on alternative procedures. Logical errors in the object definition Correct the objects. Repeat phase PCON_<rel>. however. Also check whether the objects which are not contained in the standard and which are now incorrect can be deleted completely. Often it concerns insufficient disk space. If the index definition is not corrected. for example.

• The job was terminated normally. In this case. Check if the error can be reproduced by selecting repeat in R3up. Enter Transaction SM37 and narrow down the start time and start date as far as possible.Upgrading to 4. If the error occurs again. If you are unsure how to proceed. but with error messages. In this case R3up does not require a password if you choose ignore. 2. These error messages can sometimes be ignored. The naming convention for the job phases is JOB_<Name>. proceed as described in Providing SAP Local Support with Information. there are two possible cases: • The job was abnormally terminated. If no background job was started. contact SAP Local Support.6C Support Release 2: UNIX SAP AG Correcting Errors in the Job Phases Use A job phase starts a background job in the SAP System and waits for it to end. Procedure To analyze problems with a job phase. Log on to the SAP System as user DDIC. If the background job was started. contact SAP Local Support. call SAP Local Support. Proceed as follows: 1. this is generally due to a syntax error in the calling program. start by checking if a background job was started at all. If there is no Note explaining this error. 184 April 2001 . where <Name> is the name of the job or report.

If you need to correct entries made in INITSUBST . Choose exit to exit R3up and then restart the upgrade as described under Restarting the Upgrade [Page 109]. use the start mode init. enter the following command: set stdpar To change the password of the user DDIC. enter the following command: R3up set stdpar To change the password of the user DDIC. To start the current phase. choose Administrator → Start R3up with option. the password of user DDIC is changed during the upgrade.6C Support Release 2: UNIX Correcting Entries from the INITPUT and INITSUBST Phases Use If in later phases you find that entries you made in the INITPUT and INITSUBST phases were incorrect. enter the following command: R3up set DDICpwd 2. If you are using scroll mode: 1. use the start mode init. In the main menu of the Upgrade Assistant. April 2001 185 . you have the option of only changing the password of the DDIC user. enter the following command: set DDICpwd 3. Frequently. This is the reason why background jobs could not be started in the JOB_<name> phases. To do this. enter the following command: R3up set rswpar 3. 2. Restart R3up.SAP AG Upgrading to 4. If you need to correct entries made in INITPUT. you can correct them. If you need to correct entries made in INITSUBST . enter the following command: set rswpar 4. If you need to correct entries made in INITPUT. So that you do not have to reconfirm all the entries you made in the INITPUT phase. Procedure If you are using the Upgrade Assistant: 1.

and then delete these jobs using Transaction SM37. This ensures that if there are identical names. Before restarting the upgrade after a system failure. Using Transaction SM37. tp. 3. Move all the logs contained in the subdirectory tmp of the upgrade directory into the subdirectory log of the upgrade directory. 186 April 2001 . 2. delete all the released background jobs related to the processing of a phase with the exception of RDDIMPDP. you must ensure that a number of requirements for successful restarting of the upgrade are met: Procedure 1.Upgrading to 4. Restart the upgrade as described under Restarting the Upgrade [Page 109]. for example) R3up. run the report RSBTCRPR. 6.6C Support Release 2: UNIX SAP AG Preparing the Restart of the Upgrade After a System Failure Use If the system fails (due to power failure. and R3trans are no longer able to perform certain debugging operations. Use the following commands to copy a log to a new location.. 4. Cancel any background jobs that have already been restarted using Transaction SM50. the logs from the subdirectory tmp of the upgrade directory are added to the logs in the subdirectory log and no logs are overwritten. cd <upgrade directory>/tmp cat <log name> >> ./log/<log name> rm <log name> 7. 5. To change the status of all the current or active background jobs to 'terminated'. Start the SAP System. Log on to the SAP System as user DDIC and delete all the entries from table TRBAT using Transaction SM31.

6C Support Release 2: UNIX Resetting the Upgrade Use You need to take different measures to reset the upgrade (because of hardware problems. Procedure After Database Failure Depending on the upgrade strategy you have chosen and the stage of the upgrade reached. For information on the progress of the upgrade. Delete the upgrade directory. Some of the actions are listed in italics. depending on what stage the upgrade has reached. see SAP Note 158358. see the vendor’s specifications. for example). It could be necessary to downgrade these software components after upgrading the operating system and/or database system in order to restart the production system. see the log file R3up. including the operating system. Also perform one or more of the following actions. April 2001 187 . For downgrading options. For additional information on resetting an upgrade. If you have any questions. you need to perform various actions. 4. see the end of this section under Detailed Description of the Individual Actions. To perform these actions. The safest method is to reload a complete backup of the whole system. depending on the progress of the upgrade: If the phase MODPROF_TRANS ENVCHK KX_SWITCH has already been completed Reset the SAP profiles Reset the user profiles Reset the SAP Kernel 3. You need to distinguish between two cases: • • Database failure without loss of the upgrade directory Loss of the upgrade directory The actions you need to take are listed in the following section depending on the selected upgrade strategy and the progress of the upgrade. contact SAP Local Support. Reset the database to the state it had before the SAP upgrade. In addition to resetting the database. Upgrade Strategy A_off 1. 2.SAP AG Upgrading to 4. you might also have to reset the SAP Kernel and the SAP profiles. Restart the upgrade with PREPARE. These actions are listed in the tables below: The actions are explained in more detail later.log.

perform a point-in-timerecovery to the last state of the database. 188 April 2001 . Also perform one or more of the following actions. reset the database to the state it had when the central instance was isolated. proceed exactly as described in the Database Failure section above. skip the phase by entering a password (which you can get from SAP Local Support). In this case. Restart the upgrade at the point at which it was interrupted. restart where it terminated. • • If the MODPROF_TRANS phase has not yet been completed. Upgrade Strategies A_switch and A_on This procedure depends on whether the system is operating productively. depending on the progress of the upgrade: If the phase MODPROF_TRANS ENVCHK KX_SWITCH has already been completed Reset the upgrade directory Reset the user profiles Reset the SAP Kernel 3. proceed as follows: 1. Before you delete the upgrade directory. Upgrade Strategy A_off If the upgrade directory has been destroyed. 2. 2. Upgrade Strategy A_on 1. Reset the database. it is irrelevant whether the database. Recover the database up to the point at which the upgrade was interrupted. Since the database and the upgrade directory match only at the beginning of the upgrade. or whether it is in downtime. If the MODPROF_TRANS phase has already been completed. you must also recover it. If the MODPROF_TRANS phase has already been completed.6C Support Release 2: UNIX SAP AG Upgrade Strategy A_switch 1. Procedure After Loss of the Upgrade Directory If the upgrade directory is affected by the hardware problem.Upgrading to 4. Recover the last state of the database (if the database is affected). If the substitution tables have already been created on the database. R3up deletes these substitution tables at the start of the EU_IMPORT phases before re-importing the data. 2. back up all data from this directory that can be recovered. Restart the upgrade. the upgrade directory or both are destroyed. restart in MODPROF_TRANS. the SPACECHK phases tell you that there is not enough free space. • • If the MODPROF_TRANS phase has not yet been completed. Downtime begins at the MODPROF_TRANS phase. so that it corresponds to the state of the database. There is then enough space. Delete the upgrade directory and restart the upgrade with PREPARE. If the MODPROF_TRANS phase has not yet been completed.

For strategy A_on. Reset the user profiles The new user profiles are normally also valid for the old SAP System version. we recommend that you delete the tables manually. Try to start. Recover the upgrade directory as described in Reset the upgrade directory.cshrc . Reset the database to the state it had when the central instance was isolated. 3. you must retrieve these two files from the sapnames subdirectory of the upgrade directory.kshrc April 2001 189 . Only recover the old user profile if problems occur when you do this. PSAPES<target release>I. The following files are affected here: . the fragmentation of the free space segments leads to an increase in required space of up to 10% of the entire of the tablespace. The instance profile is saved in PROFX.BCK. the default profile in DEFPROF.SAP AG Upgrading to 4. see Isolating the Central Instance [Page 202]). the instance profile and the default profile of the SAP System are changed by R3up. contact SAP for help with choosing the jump option. If you let R3up delete the tables. If you cannot recover the upgrade directory. Delete all the tables in the tablespaces PSAPES<target release>D. depending on the progress of the upgrade: If the phase ENVCHK KX_SWITCH has already been completed Reset the user profiles Reset the SAP Kernel 4. proceed as follows: 1.BCK. Also perform one or more of the following actions. If the MODPROF_TRANS phase has already been completed.login . a point-in-time recovery is necessary. before you restart the upgrade. (which means that you have already isolated the central instance. This is the only way to restore consistency with the upgrade directory. Do this even if the database has not been corrupted. stop and log on to the system as user <sapsid>adm.6C Support Release 2: UNIX Oracle For Oracle. PSAPEL<target release>D and PSAPEL<target release>I and then join the free space segments together with the following SQL command (available as of Oracle version 7. Restart the upgrade in the MODPROF_TRANS phase. Detailed Description of the Individual Actions Reset the SAP profiles After phase MODPROF_TRANS (or EU_IMPORT0 for upgrade strategy A_off). If this phase has been completed.3): alter tablespace <name> coalesce. 2.

SAR and SAPEXEDB. 190 April 2001 .SAR from the CD. You can exclude the data directory if you have space problems. You must reimport the old Kernel when you make the recovery. The old files are in <upgrade directory>/exe/INSTALL.Upgrading to 4. Delete the upgrade directory We recommend that you archive all the subdirectories before you delete the contents of the upgrade directory. Reset the upgrade directory You must recover the whole upgrade directory with all its subdirectories.csh . You must unpack the packages SAPEXE.6C Support Release 2: UNIX SAP AG .sh All the files are in the home directory of user <sapsid>adm. Then delete the contents of the upgrade directory. Reset the SAP Kernel The new Kernel is active after the KX_SWITCH phase.dbenv_<host name>. You can recover the Kernel directory from a backup created before the upgrade or from the Kernel CD of the source release.dbenv_<host name>. You must have backed up the upgrade directory when you isolated the central instance if you want to do this (see Isolating the Central Instance [Page 202]). These profiles have the latest state after the ENVCHK phase.profile startsap_<host name>_<instance number> stopsap_<host name>_<instance number> .

Check whether a tp process still exists. note the process number. If it is. it keeps running independently of the upgrade. You must prevent R3up from starting two processes of the same type. If so. Restart the upgrade as described under Restarting the Upgrade [Page 109]. both in the SAP System. Check whether R3up is running in the background on the host. Procedure 1. If so. R3up does not need to wait if the processes found are of a different type. When you restart R3up. If the transport control program was active when R3up terminated. and at the operating system level. R3up logs any processes it has started.SAP AG Upgrading to 4. 3. R3up must wait until these processes have ended. a check is made to see if any of the processes you noted are still running. 2. use the command kill to stop R3up. April 2001 191 .6C Support Release 2: UNIX Scroll Mode: Restart Prerequisites You are upgrading the system in scroll mode from a PC or X Terminal and the terminal connection has broken.

Use Transactions SM37 and SM50 to check if RDDIMPDP has already started the actual background job for editing the ABAP step. proceed as follows: 1. see the documentation Transport Control Program tp. To trigger an ABAP step. table TRBAT may contain only one HEADER entry. During distribution of the Dictionary objects (S) and table conversion (N). These are: • • • • • • • Dictionary activation (A) Distributing Dictionary objects (S) Table conversion (N) Matchcode activation (M) Importing application objects (D) Updating version management (U) Executing XPRAs (R) The interface between the transport control program tp and the SAP System is formed by table TRBAT. To access this documentation: In Release 3. Log on as user DDIC in client 000. so that event-driven jobs are also displayed. The table must have one HEADER entry and should contain one entry for each transport request. 3. Check when RDDIMPDP last ran and if it ran without errors.x: Choose Help → R/3 Library → BC Basis → System Administration → Transport Control → Transport Control Program tp. In Release 4. Result For more information on the transport control program and on communication between tp and the SAP System. 192 April 2001 . as these steps are not carried out by transport request. 4. 2.Upgrading to 4. In phase JOB_RDDNEWPP the background job RDDIMPDP is scheduled to run when certain events occur to process the entries in table TRBAT. Check if the control information in table TRBAT has been entered correctly.6C Support Release 2: UNIX SAP AG Correcting Problems when Processing ABAP Steps Use Some of the ABAP steps are performed in the SAP System. Enter an asterisk (*) in the field or after event. tp writes control information into this table.x: Choose Help → SAP Library → Basis Components → Change and Transport System → BC Transport Tools → Transport Control Program tp. Check that the SAP System was started correctly. Procedure If you encounter problems when editing the ABAP steps. Enter Transaction SM37 and check if background job RDDIMPDP has been scheduled.

In both cases. check whether the SAP System is supposed to be started up or shut down at this point. try to run the SAP System with fewer dialog processes April 2001 193 . increased demands on computer resources may have caused the problems. If the SAP System is not successfully started up and the next step requires processing to take place within the SAP System (table conversion.6C Support Release 2: UNIX Correcting Problems when Starting the SAP System Use In the course of the various phases. If this is the case. tp waits without success for this step to end. Try to start up the SAP System with the command: startsap r3 If you cannot start up the system manually. for example). shut down any SAP processes that may be running with the command: stopsap r3 3. Starting at the end of the log. MODPROF_BAS and MODPROFP_<rel> or by SAP programs being exchanged in the KX_SWITCH phase. 4. the SAP System should have been started up. Check whether all processes of the SAP System were actually stopped. according to SLOG. You can do this with the command: ps –fu <sapsid>adm The output should consist only of database processes.SAP AG Upgrading to 4. R3up. transport control program tp restarts the SAP System automatically several times. 2. tp. If. search upwards for the latest entry marked tpsapstop or tpsapstart. Procedure 1. and some shells. Using the SLOG log (SLOG46C). but you are unable to log on as user DDIC. this is probably caused by changes to the SAP profile made in the phases MODPROF_TRANS.

Analyze the log of the copy process. Do not start the SAP System during this period.<SAPSID>. Repeat the phase or copy the program manually from subdirectory exe of the upgrade directory to directory /usr/sap/<SAPSID>/SYS/exe/run. It is located in the subdirectory log of the upgrade directory and is called C<DATE>.6C Support Release 2: UNIX SAP AG Correcting Problems when Copying SAP Programs Use In the phase KX_SWITCH. it cannot overwrite the old files. Procedure 1. 194 April 2001 .Upgrading to 4. 2. the SAP programs in the directory /usr/sap/<SAPSID>/SYS/exe/run are replaced. otherwise.

are automatically adjusted on the host with the central instance. Log on to the application server. The profiles on the secondary application servers only need to be adjusted if the <sapsid>adm users do not have the same home directory. Enter the following commands as user <sapsid>adm: cd /<new directory name> . The templates for the new profiles are in the subdirectory exe/INSTALL of the upgrade directory. R3up replaces the placeholders in the templates and writes the result to the home directory of <sapsid>adm. if necessary you can use R3up to update these profiles as well. 4. 2. Confirm the update for the relevant profiles. Procedure 1. the UNIX user profiles. April 2001 195 . Mount the upgrade directory from the host with the central instance: mount <host_name>:<upgrade_directory> /<new directory name> 3. and also the scripts for starting and stopping the system.6C Support Release 2: UNIX Correcting Administrator Profile Problems on Application Servers Use During the upgrade. However./R3up update_user R3up displays every <sapsid>adm profile and asks you whether you want to replace it.SAP AG Upgrading to 4.

Procedure If you encounter problems that are specific to the upgrade.log file located in the upgrade directory.R/3 Frontend customer message: 1. see SAP Note 40024. follow the procedure given here.ELG or the last file written with the .R/3 Frontend. if one exists (use transaction ST22 to find this out). Which release are you upgrading from? Which release are you upgrading to? 3. To enable us to help you as quickly and effectively as possible. Which operating system version are you using? 4.6C Support Release 2: UNIX SAP AG Providing SAP Local Support with Information Use If none of the measures described in Problems and Solutions During the Upgrade solves your problem. For which SAP component do you want to perform the upgrade? 2. If you are certain that the problem is not an upgrade-specific one but a product-specific one. For more information about using the SAP support server to transfer files. assign your error message to the appropriate product-specific component. 6. we also require − − − Last job log of user DDIC written in client 000 (use transaction SM37 to find it) Last lines written in the system log of the SAP System (use transaction SM21 to find them) Last short dump written to the system log at the time in question. create an error message in the SAPNet – R/3 Frontend and assign it to the component BC-UPG. In which R3up phase does the error occur? This information is listed at the end of the of the R3up.Upgrading to 4. • For transport phases we also require SLOG46D. 196 April 2001 . contact your SAP Local Support. Answer the following questions and put these answers in your SAPNet .ELG suffix and the detailed log file that contains the error message For the phases JOB_<name> or RUN_<name>. The following table gives you information on the different components to which you can assign your message in SAPNet .log <name of the phase with errors>. Did you have problems with the SAP System before upgrading? Also provide us with the following logs (if they exist in the upgrade directory) using ftp on the SAP support server that is closest to you (sapserv<x>) or by fax: • • • R3up. What was the original release of your SAP System? 5.

Mobile Client .CRM Server .6C Support Release 2: UNIX SAP Product Component in SAPNet – R/3 Frontend Index Management Server OLTP R/3 System R/3 Standalone Gateway SAP Add-On SAP Advanced Planner & Optimizer SAP Business Connector SAP Business Information Warehouse SAP Business-to-Business Procurement SAP Customer Relationship Management .SAP AG Upgrading to 4.Internet Pricing and Configurator (IPC) .R/3 SAP DrFuzzy Search Engine SAP Frontend SAP Internet Transaction Server SAP Knowledge Management SAP R/3 Enterprise SAP Strategic Enterprise Management SAP Web Application Server SAP Workplace Server SMART Installation BC-SRV-TRX BC-UPG BC-UPG BC-UPG-ADDON APO-BAS BC-MID-BUS BW-SYS BBP-SAD CRM-MW BC-MID-INT-SRV CRM-MT-IU-SPE CRM-WBT-IU BC-UPG BC-SRV-TRX BC-INS BC-FES-ITS KM-KW BC-UPG BC-UPG-ADDON BC-UPG BC-UPG BC-UPG April 2001 197 .Communication and Development Station .

6C Support Release 2: UNIX SAP AG Upgrade Administration This section contains additional information on the various administrative tasks which are necessary before and during the SAP upgrade. • • • • • • • • • Using the Alert Function [Page 199] Determining the Operating System Version.Upgrading to 4. Database Version and the SAP Release [Page 200] Executing PREPARE and R3up in Scroll Mode [Page 201] Isolating the Central Instance [Page 202] Changing the Database Recovery Mode [Page 205] Deleting Archived Upgrade Logs [Page 206] Using a Different Upgrade Directory [Page 207] Releasing and Confirming Open Repairs and Requests [Page 208] Reducing Upgrade Runtime in Modified Systems [Page 210] 198 April 2001 .

This alert file is deleted when the upgrade is continued. and minimize downtime. • Alert Function of the Upgrade Assistant When you use the Upgrade Assistant for your upgrade. Go to the main menu and choose Help → Introduction. of if the upgrade terminates (for example. instead of analyzing the alert file. for example by telephone. As with the alert file. due to an error). you must also provide the external software for starting a communication service. you can use an alert function. then go to the section ‘Set Alert’ window. Activities To activate the alert functions of the Upgrade Assistant. to indicate that action is necessary. Functions • Alert file An appropriate message appears on the screen if the upgrade stops. You see the following screen: You can get more information online in the Upgrade Assistant. go to the main menu of the Upgrade Assistant and choose Administrator → Set Alert.SAP AG Upgrading to 4. April 2001 199 . An alert file upalert. You can use this to notify the system administrator.log is also created in the sub-directory tmp of the upgrade directory. You can then be informed if the control program R3up waits longer than a predefined period of time for input.6C Support Release 2: UNIX Alert Function Use Use the alert function to inform yourself if the upgrade waits for a long time.

6C Support Release 2: UNIX SAP AG Determining Versions Determining the Operating System Version At the UNIX level enter the following command: uname -a Determining the Database Version SAP DB Execute the following operating system command: x_cons <SAPSID> show version Informix With the database running.Upgrading to 4. The first line of the output contains the Oracle server release. enter the following command as user informix: onstat Oracle Execute the following SQL command: SELECT BANNER FROM V$VERSION. End of the database-specific explanations Determining the SAP Release You can determine the SAP Release by selecting System → Status in the SAP main menu. 200 April 2001 .

respond to the prompt for the display after you start PREPARE with SCROLL. Executing PREPARE in Scroll Mode To execute PREPARE in scroll mode./R3up [gt=SCROLL] When you are prompted for the display mode. You need to do this if there is some reason why you cannot use the Upgrade Assistant. or do not want to. start the program as follows: 1. 2. Log on to the host on which the central instance is running as user <sapsid>adm. 2. April 2001 201 .6C Support Release 2: UNIX Executing PREPARE and R3up in Scroll Mode Use You can execute PREPARE and R3up in scroll mode. To run R3up. When you restart PREPARE you need to proceed as follows: 1. enter SCROLL for the line-oriented mode. Log on to the host on which the central instance is running as user <sapsid>adm. enter the following command: cd <upgrade_directory>/bin . since PREPARE is started from the CD./PREPARE When you are prompted for the display mode. enter SCROLL for the line-oriented mode.SAP AG Upgrading to 4. Executing R3up in Scroll Mode If you want to execute R3up in scroll mode. The commands for starting PREPARE for the first time [Page 66] are the same for display mode Server (Upgrade Assistant) and display mode Scroll. Enter the following commands: cd <upgrade_directory>/bin .

b. You have two options: a. During downtime. all users must be logged off the system. Stop the SAProuter now and restart it after the upgrade. Stop and delete saposcol as user root: cd /usr/sap/<SAPSID>/SYS/exe/run . you can rename it as follows: cd /usr/sap/<SAPSID>/SYS/exe/run mv saprouter saprouter. R3up asks you to isolate the central instance when downtime begins. A list of all the parameters is displayed.busy after you have started up the new SAProuter. This could affect R3up's control of the system. You can use Transaction SM02 to inform the users logged on to the system.Upgrading to 4. 3. Procedure 1./saposcol –d Collector> leave rm saposcol 2. These must have the following values: cpu=-1 fsize=4194302 core=100000 202 April 2001 . If you need the SAProuter during the upgrade. AIX Check the restrictions for cpu. Enter the command lsuser as user root./saposcol –d . See the documentation CD for the target release (SAP Library → Basis Components → Kernel Components → BC SAProuter). Make sure that no CRON job is scheduled that affects the system. backing up the database or similar actions. fsize and core for user <sapsid>adm.busy Delete saprouter. 4.6C Support Release 2: UNIX SAP AG Isolating the Central Instance Use You need to isolate the central instance so that only the upgrade program can work with the system during downtime. The SAProuter in the directory /usr/sap/<SAPSID>/SYS/exe/run must not be active while the new SAP Kernel is being imported. This means that you can use the central instance exclusively for the upgrade. To get more information about the SAProuter : − − Enter saprouter at the operating system level. such as starting and stopping the SAP System.

SAP AG Upgrading to 4. d. Determine the jobs involved. c. b. The To date must be far enough in the future that you can display the background jobs which could become active during the upgrade. For Source Releases 3. change them with the command chuser (Entry: chuser cpu=-1 <sapsid>adm) and correspondingly for fsize and core. you must delete all future schedules. check that the from date is in the past. Since the old job formats can no longer be read by Transaction DB13 after the upgrade. Position the cursor on the job that you want to delete and choose Delete. Choose Execute. 6. As of Release 4. Make sure that no change of operation mode is defined on the central instance during the upgrade. Then start up the SAP System with stopsap and startsap. If this is not the case. Execute b) and c) until all jobs that were not yet executed have been deleted. Clean up all outstanding updates as described in Evaluating Results from PREPARE [Page 87] when the message Update records still exist . The upgrade is not affected if RDDIMPDP is also scheduled in other clients. c. These changes only take effect for user <sapsid>adm when you have logged on again as <sapsid>adm. Fill in the necessary information on the screen Select background jobs as described in the example below. No background job other than RDDIMPDP may be active during the upgrade. 8. f. In the field Start date. you have to cancel the release of all background jobs except RDDIMPDP before the upgrade. 7. Special feature in client 000 The background job RDDIMPDP must be scheduled in client 000. Transaction DB13 uses different internal job formats. If this is the case in normal operation. e. schedule it by executing the report RDDNEWPP (Transaction SE38). April 2001 203 .0B. Double-click on the corresponding day in the header line in order to see the job overview for this day. Cancel the release by choosing: Job → Schedule Job → Cancel. Proceed as follows: a. To do this: a. use Transaction SM63 to either choose a single operation mode for all time spans or delete all the assignments. these jobs are automatically descheduled by R3up .Please process appears. d. b. You must do this in every client. End of AIX 5.1x Only: Delete scheduled actions in Transaction DB13. Call Transaction SM37.5B. Log on as user DDIC in the relevant client. For all other source releases. As of Source Release 4.0x/3.6C Support Release 2: UNIX If this is not the case. Start Transaction DB13.

Back up your upgrade directory now if you chose strategy A_switch or A_on. So that R3up has the correct control information.Upgrading to 4. delete the corresponding tablespace and recreate the table with Transaction SE14. These tables are now empty. you may have to reset the upgrade to its status when the system was isolated. then you must reset the partitioning of these tables now and recreate them in segmented tablespaces. 12. Make sure that you can recover the database to its current state. Otherwise you may lose data. DB2 for OS/390 For Source Releases up to and including 4. This only applies to these three basis tables. If a hardware problem occurs during downtime. To reset the partitioning. For example.6C Support Release 2: UNIX SAP AG 9. by manually importing requests for the automatic adjustment. Make sure that no transport requests are imported into the system during downtime. VBDHR and VBMOD If you want to partition the tables VBDATA. 10. VBDHR and VBMOD as described in Note 122599. you may lose all your modifications to the SAP standard. Application tables remain partitioned. End of DB2 for OS/390 204 April 2001 .B only: Partitioning of tables VBDATA. the upgrade directory must have the same status as at the beginning of the phase MODPROF_TRANS. You can lock the database against remote access. 11. Shut down all application servers. 13. Contact the database administrator. if there are any (secondary SAP instances).0.

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

Changing the Database Recovery Mode
Use
If you use the upgrade strategies A_switch and A_off, you need to change the recovery mode of the database at the beginning and end of downtime.

Procedure
SAP DB

The recovery mode is changed automatically by R3up.
DB2 Universal Database

When you set LOGRETAIN and USEREXIT to OFF, make sure that you can restore the current state of the database. If the last full backup was a long time ago and the number of archives collected up to that point is large, SAP recommends performing a full backup before setting the parameters to OFF.
Informix

Ensure that the current state of the database can be restored when backup mode is deactivated. If the last complete backup was some time ago and a large amount of logical log files has been created since, make a complete backup of the current database state before deactivating the backup mode. Deactivate the backup mode as follows: 1. Stop the database as user informix with:
onmode -yuk

2. Edit the file $INFORMIXDIR/etc/$ONCONFIG as user informix and change the parameter LTAPEDEV to /dev/null. 3. Start the database as user informix with:
oninit Oracle

When you deactivate database archiving, you must make sure that the current state of the database can be recovered. If the last complete backup was some time ago and a large set of archives has since been collected, we recommend a complete backup of the current status of the database before deactivating archiving. Deactivate the archiving as follows: 1. Log on as user ora<sapsid>. 2. Start the program sapdba and use the option Archive Mode → Toggle Database log mode. In the same way as when you deactivate the archiving, you can reactivate it as user ora<sapsid> with the program sapdba.
End of the database-specific explanations

April 2001

205

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Deleting Archived Upgrade Logs
Use
You can make more space by deleting archived logs from earlier upgrades that you no longer need.

Procedure
To do this, delete the subdirectories <target_release> along with their contents:
/usr/sap/trans/upgrade/<SAPSID>/<target_release>

If you no longer need the logs of the upgrades to 3.0D and 3.0F, then you can delete the subdirectories 30D and 30F: /usr/sap/trans/upgrade/P11/30D /usr/sap/trans/upgrade/P11/30F /usr/sap/trans/upgrade/P11/30I ..... /usr/sap/trans/upgrade/T11/30D /usr/sap/trans/upgrade/T11/30F /usr/sap/trans/upgrade/P11/30I .....

206

April 2001

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

Using a Different Upgrade Directory
Use
You can use an upgrade directory other than /usr/sap/put/. This is useful if you have several SAP Systems on a single host and you want to upgrade them all to a new release. The name of the directory must include put, for example /usr/sap/put_C11/ or /free/PRD_put/.

Prerequisites
In the instance profile of the SAP System, you have to set the parameter DIR_PUT to the upgrade directory that you want to use: DIR_PUT = <upgrade_directory>
R3up checks at startup if the entry in the instance profile matches the specified upgrade directory.

Procedure
Call PREPARE or R3up with the following parameter:
PREPARE upgdir=<upgrade_directory> R3up upgdir=<upgrade_directory>

You must specify the parameter upgdir each time you call PREPARE or R3up, otherwise the default value /usr/sap/put is used.

If you want to use another upgrade directory, make sure that no /usr/sap/put/ directory exists on this host.

April 2001

207

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Releasing and Confirming Open Repairs and Requests
Use
Before starting to upgrade, release and confirm all open repairs and requests that conflict with the SAP delivery. PREPARE determines a list of these repairs and requests. If you ignore open repairs, you could lose modifications. To release and confirm open repairs, you must log on to the system as the owner of the repairs. You can find the user names of the owners in CHECKS.LOG.

Procedure in Release 3.x:
1. Log on to the SAP System as the owner of an open repair. 2. Enter Transaction SE01. 3. Choose Find.

You can also release the repairs from the Workbench Organizer (Transaction SE09). 4. Make sure that the field User name contains the correct name. 5. Enter REPA in the field Type. Leave all the other default values unchanged. 6. Choose Execute. A list of all the open repairs for this owner appears. 7. Select the repair that you want to release. 8. Choose Repair → Release repair. 9. If the repair is assigned to a higher-level transport request, this transport request must also be released.

If you are unable to log on with a specific user ID, you can change the owner of the repair in Transaction SE01. 1. In the list of open repairs, position the cursor on the repair. 2. Choose Edit → Change owner. To be able to change an owner in Transaction SE01, you need project authorization for the Workbench Organizer (S_CTS_PROJEC).

208

April 2001

For Request status. 9. If it is not confirmed. Enter Transaction SE09.x: 1. 3. Choose Change owner. A list of all open repairs for the selected user appears. Choose Request/task → Find requests… 4. you need project authorization for the Workbench Organizer (S_CTS_PROJEC). To be able to change an owner in Transaction SE09.6C Support Release 2: UNIX Procedure in Release 4. select everything except Released. Log on as the owner of the open repair. Choose Release. choose Request/task → Confirm repair. 7. 2. Choose as the Request type only the task Repair. 5. 6. April 2001 209 . Release the request to which the repair is assigned. Choose Execute. position the cursor on the repair.SAP AG Upgrading to 4. If you are unable to log on with a specific user ID. 10. 8. you can change the owner of a repair as follows using Transaction SE09: In the list of open repairs. The repair must be confirmed. Position the cursor on the request that you want to release.

You cannot have finished the PREPARE preparation phase.5A. the Repository Switch automatically copies objects from the SAP namespace to the new Repository. there are no conflicts with changes made by SAP. 210 April 2001 . 6. Use the PREPARE module Modification support to check that the amount of objects copied has been restricted. then you can speed up the upgrade. Use Transaction SE95 (Modification Browser) to display all objects that have been modified in your system. Restart PREPARE. Choose Yes to confirm that you want to restrict the objects copied to those displayed in Transaction SE95. Do not use this runtime optimization option if you are not sure whether the list is complete. Only those objects are copied that appear here. This alternative is based on the modification status of the objects. and check whether the list is complete.6C Support Release 2: UNIX SAP AG Reducing Upgrade Runtime in Modified Systems Use Under certain conditions. you need to specify that R3up excludes any objects that no longer count as modified from being copied to the Repository. You created the object as a new object. To do this.5A.Upgrading to 4. Enter the following commands at the operating system level as user <sapsid>adm: R3up set sapmodi 4. Procedure 1. 5. This module writes the object list SAPKCCR<target release>. exit it by choosing exit. If PREPARE is still active. administered by the Modification Assistant as of Release 4. 3. The corresponding log is called CUSTEXP. however. but now are no longer classed as modified. Prerequisites You must have at least Source Release 4. 2. If many objects were at one time modified in your system. • • You modified the object. The change now takes affect.<SAPSID>. The Repository Switch detects these objects using the requests with which they were created or changed.

SAP AG Upgrading to 4.6C Support Release 2: UNIX Upgrade Tools The following tools support you in upgrading the SAP System: • • • • PREPARE R3up Upgrade Assistant Upgrade Monitor April 2001 211 .

you must also check the operating system. The PREPARE modules have the following features: • • • • They can be mandatory or optional. Prerequisites You must meet a number of requirements before you run the PREPARE program. It checks the requirements for the upgrade and provides further information when executing the optional module. For example. They can have predecessors which must first be executed. • • • • You can execute this program while the system is running. PREPARE modules can be executed individually. Integration When the upgrade is started. R3up assumes that the mandatory modules have run through successfully. Afterwards. Functions All the actions performed by PREPARE execute in phases. The following graphic gives an overview of all the PREPARE modules and their predecessors. These phases are combined into PREPARE modules. PREPARE performs the majority of the required checks automatically. database and SAP System manually as well. It copies data and programs to the upgrade directory. the analysis tools must be imported before they can be executed. A complete list of the modules and the phases which execute in these modules can be found in the phase list for PREPARE. These are described in the section User Actions Before Starting PREPARE. since production operation could have created a new situation.Upgrading to 4. 212 April 2001 . R3up then repeats a number of the checks (not all of them).6C Support Release 2: UNIX SAP AG PREPARE Use Use the PREPARE program to prepare your SAP System for the upgrade. Import a number of tools into your database. There are PREPARE modules which you must only execute once and those which you can execute as often as you require.

6C Support Release 2: UNIX Parameter entry Initialization Import CD Read General checks Activation checks Required checks for conversions Optional checks for conversions Modification support Preliminary execution For more information about the contents and features of the PREPARE modules. To be sure that all the requirements are met. such as SAP Support Packages. you can choose certain PREPARE modules more than once. languages. Its contents are saved in file CHECKS. see the online help for PREPARE. see Importing Software after Starting PREPARE. April 2001 213 . it is overwritten each time a module is executed again. After you start PREPARE.SAV. you may need to import software. If the file CHECKS. Results of PREPARE PREPARE writes the results for the modules that you selected for execution to the file CHECKS.SAP AG Upgrading to 4.LOG already exists. Activities • • Start PREPARE as soon as possible before the upgrade so that you can initiate or perform the necessary preparations in time.LOG. or add-ons (and add-on updates). You can find it easily by choosing Help when selecting the modules. Look at this file and carry out the necessary measures based on the information it contains. For more information. This file is in the subdirectory log of the upgrade directory.

Upgrading to 4.6C Support Release 2: UNIX SAP AG PREPARE Phase List PREPARE Module Parameter Input Phase BEGIN_PRE INITPUT_PRE Actions Taken by PREPARE Log User Actions Checks upgrade directory Initialize R3up DB2 Universal Database DB2 Universal Database DB6RUNST.LOG EXECCT. if necessary VALCHK.LOG Upgrade to a valid source release.LOG Enter parameters DB2 Universal Database Update database statistics DB2 for OS/390 Choose MEDIUM or HIGH DB2 for OS/390 Tests JCL submission Test JCL submission Start second ICLI server DBCHK_PRE INIT_CBU_REQ_READ NOTE CHECKGROUP_END Determines DB and SAP version --End of module PREPARE Module Initialization Phase DBCHK_INI RFCCHK_INI VERSCHK_INI Actions Taken by PREPARE Log User Actions Determines DB and SAP version Tests the RFC connection Checks SAP version RFCCHK_INI.LOG Unlock clients for SAP upgrade.LOG VALCHK_INI Tests target system: is it a preliminary version? (Cannot upgrade the system) Checks whether clients are locked for SAP upgrade CLNT_CHK_INI CLNTOUT. if necessary 214 April 2001 .

LST Extend free disk space.LOG EXECPT. if necessary DBPREP_CHK CHECKGROUP_END --End of module PREPARE Module Import Phase REQIMPORT READDATA0 Actions Taken by PREPARE Log User Actions Displays prompt Reads data files for Source Releases 3.1I or 4. 4.0D or 3.6B: Mount Upgrade CD3 READDATA2 CPYFIL0_CBU EXEC_CPYFIL1_CBU INFO_STORE_READ CONFCHK_IMP If necessary.1H.1I or 4.5B.LOG KRN_CHK.5B. 3.0F and data files required for all source releases from Upgrade CD1 Source Releases 3.6A or 4.0B: reads data files from Upgrade CD2 Source Releases 4.SAP AG Upgrading to 4.6C Support Release 2: UNIX PATCH_CHK1 Determines nonconfirmed Support Packages and displays results Check whether the inactive nametab is empty Check free space in DB Checks the version of the SAP Kernel PATCHOUT.6B: reads data files from Upgrade CD3 ------Tests operating system and database Confirm execution of Import module Mount Upgrade CD1 READDATA1 Source Releases 3. if necessary Import current downwardcompatible Kernel.6A or 4.LOG Use transaction SPAM to confirm any unconfirmed Support Packages INTCHK_INI SPACECHK_INI KRN_CHK_INI DBFPREP. 3. upgrade OS or DB April 2001 215 .1H. 4.0B: Mount Upgrade CD2 For Source Releases 4.

LOG ICNVCOUNT.0x and 3.LOG TOOLIMPD.LOG ICNVCHK_IMP Complete incremental conversion with transaction ICNV.x: Avoids critical conversions in tool import Source Release 4. if necessary CLNT_CHK_IMP INTCHK_IMP SPACECHK_IMP PATCH_CHK2 Extend free disk space.LOG PATCHOUT.LOG CNVTST.Upgrading to 4.LOG CLCNVTST.x: Avoids critical conversions in tool import Checks whether table TRBAT is empty Checks whether clients are locked for SAP upgrade Check whether the inactive nametab is empty Check free space in DB Determines nonconfirmed Support Packages and displays results Creates tables for nametab administration so that new tools have access Deletes tables that describe the delivery Source releases 3.LOG ICNVEX.LOG CNVTST.LOG EXECCT.LOG CLCNVTST.LOG SCRIPTCHK.LOG SCRIPTCHK.ELG 216 April 2001 .LOG ALTER_TO TOOLIMPD1 ALTER_TO. if necessary SCRIPT_CHK_TOOL3 SCRIPT_CHK_TOOL4 TRBATCHK_IMP Perform any actions specified by R3up Unlock clients for SAP upgrade. if necessary Use transaction SPAM to confirm any unconfirmed Support Packages NTHISTCRE NTABHIST.LOG CLCNVTAB.LOG Determines outstanding conversions and restart logs of terminated conversions Checks whether incremental conversion from previous upgrade has finished Source Release 3.LOG CLNTOUT.1x: Prepares ABAP Dictionary for DBFPREP. if necessary ICNVCHK.LOG EXECPT.LOG CLCNVTAB.6C Support Release 2: UNIX SAP AG version CNV_CHK_IMP to required version Make conversions (after discussion with Basis consultant).LOG ICNVLIST.

LOG BATCHCHK_IMP.ELG PREPIMP.ELG NPREPCRE1 DDYIMP. prepares ABAP Dictionary for upgrade tools For source release 4.SAP AG Upgrading to 4.ELG RDPUTTB.ELG TOOLIMPI. LOG JOB_RSCVINIT READPUTTB PSCVINIT.LOG JOB_RDDGENRS RUN_RDDITCUG RUN_RSINCGEN_IMP RDDGENRS.LOG PDDITCUG.LOG PSCVINIT.6C Support Release 2: UNIX upgrade tools TOOLIMPD2 For source release 4.ELG MVNTAB_TOOL TOOLIMPI TOOLIMPM NPREPCRE0 MVNTTOOL.ELG TOOLIMPD3 TOOLIMPD.ELG UVERS_INIT UVERS_CHK_IMP BATCHCHK_IMP UVERSINI.ELG PSINCGEN.LOG PSINCGEN.LOG PDDITCUG.LOG UVERSCHK_IMP.LOG MVNTTOOL.ELG TOOLIMPM.5B.ELG PRE_IMPORT0 April 2001 217 .0B. prepares ABAP Dictionary for upgrade tools Activates nametabs for upgrade tools Imports tools for SAP upgrade Imports tools for SAP upgrade Imports tables that describe the delivery from Upgrade CD1 Imports tables that describe the delivery from Upgrade CD1 Writes entry in table UVERS Checks consistency of table UVERS Tests whether background server can access the upgrade directory Initializes table CVERS Reads table PUTTB and store in file system Generates tool reports Generate CUAs Adapts ABAP include RSTABINC to the system --- TOOLIMPD.

0D: enter language area.LOG PATCH_CHK3 Use transaction SPAM to confirm any unconfirmed Support Packages If necessary.LOG EXECPT.0D: determines language area PATCHINT. if necessary. PATCHOUT.LOG Include Support Packages in the upgrade.LOG LANGOUT. if necessary EXECLANG LANG_CHK EXECLG. if necessary 218 April 2001 .LOG Add add-ons manually. or confirm with nothing else Mount add-on CDs.Upgrading to 4.6C Support Release 2: UNIX SAP AG PRE_IMPORT1 CHECKGROUP_END --End of module PREPARE Module Read CD Phase ADDSPAREQ_0 JOB_CBUIFCHK EXECIS IS_CHK Actions Taken by PREPARE Log User Actions Prepare space check on DB --Determines add-ons Displays installed add-ons EXECIS. check using Note 73510 if upgrade can be performed or which Support Packages are equivalent in the target release.LOG Delay upgrade until next release. BIND_PATCH Includes Support Packages for the target release Determines installed languages Checks whether the new release supports the installed languages Source release 3. if necessary IS_READ Copies data for addons to the upgrade directory Determines unconfirmed Support Packages and checks if the source release contains Support Packages that are more recent than the version of the target release.LOG ISOUT. if necessary Source release 3.

ELG JOB_RDDIT021 TR_TRK2HEAP_ADDON PDDIT021.LOG ADDSPAREQ_N ADDSPAREQ_T ADJUSTPRP ADJUSTPRP.ELG TPSHBUF. if necessary.<SID> PCMDIMP.ELG PEVALLAN. TR_CMDIMPORT_ PATCH TR_TODIR_MERGE_ PATCH GETSPAREQ_N DBFINTEQ.ELG If necessary.LOG TR_HYP2HEAP_ICNV TRICVNBUF.LOG INTEG_PATCH INTGPTCH. Confirm language selection.LOG April 2001 219 .LOG LANGSEL.ELG ICNVXRQ.LOG ICNV_CND_IMP ICNVXRQ ICNVCNDI. imports command file marked in another system Imports command files for add-ons Evaluates command files imported in ISC_IMP Merges add-ons with the delivery directory Places add-on upgrade requests in the R3up buffer Selects Support Package integration file and includes the contained requests Writes ICNV add-on candidates to the R3up buffer Imports the ICNV add-on candidates Checks the LANGSEL.ELG Mount language CDs. select command file ISC_IMP IS_MERGE ISC_IMP.SAP AG Upgrading to 4.LOG PDDIT021.LOG PCMDIMP.6C Support Release 2: UNIX LANG_SELECT Copies data for language import to the upgrade directory Imports piece lists for included Support Packages Merges included Support Packages with the delivery directory Determines freespace needed for the language data on the database Prepare space check on DB Prepare space check on DB Prepares adjustment calculation: if necessary.

LOG DDICNV. check write authorizations for SAP Kernel. if necessary If necessary.ELG DDICNV.ELG ICNVCAND. if necessary UVERS_UP_T CHECKGROUP_END PREPARE Module General Checks Phase CONFCHK Actions Taken by PREPARE Log User Actions Tests operating system and database version Check free space in DB Checks disk space for logs and Kernel Checks whether the SAP Kernel can be overwritten.LOG ICNVINIT. initializes ICNV tables with the successful candidates Prompts you to call transaction ICNV after candidates have been written to the ICNV tables Changes status in table UVERS End of module ICNVREQ_PRP ICNVREQP. DBFPLUSD. if necessary Make conversions (after discussion with Basis consultant). REPACHK.LOG Checks the volumes of the candidates.LOG SPACECHK_GEN FREECHK REPACHK Determines SAP objects locked in repairs or requests Determines outstanding conversions and restart logs of terminated conversions Checks whether table TRBAT is empty Release repairs and requests. update OS or DB to required version Extend free disk space.LOG ICNVREQP.LOG If necessary.Upgrading to 4. if necessary Increase disk space.ELG DDICNV. if necessary Perform any actions specified by R3up CNV_CHK_GEN TRBATCHK_GEN 220 April 2001 .LOG Call transaction ICNV.LOG ICNVINIT.6C Support Release 2: UNIX SAP AG prerequisites for ICNV and filters candidates for ICNV ICNVINIT ICNVXRQ.

if necessary JOB_RS_NAMT_CL NTACT_CHK NTCHK. LOG BATCHCHK_GEN.ELG JOB_RSVBCHCK1 Delete any terminated updates CHECKGROUP_END April 2001 221 .LOG Delete tables. if necessary ENVCHK_PRE If necessary assign write authorization to the user profile Upgrade the frontend software. if necessary VIEWCHK VIEWCHK.LOG PSVBCHCK.SAP AG Upgrading to 4.LOG Correct entries with R3up set stdpar.LOG EXECCT.ELG NTCHK.LOG PXPRECHK.LOG Perform any actions specified by R3up INTCHK_GEN SINXCHK Delete indexes.6C Support Release 2: UNIX CLNT_CHK_GEN Checks whether clients are locked for SAP upgrade --Checks the consistency of the nametab entries Check whether the inactive nametab is empty Checks the consistency of the indexes in the substitution tables Checks collisions between customer tables in the SAP namespace and delivered views Checks whether profile of user <sapsid>adm can be modified Displays information about the upgrade of the frontend software Checks consistency of table UVERS Tests whether background server can access the upgrade directory Checks if the profile names specified in INITPUT correspond to the names used by the system Preliminary checks for XPRA RLXPRA40 Checks whether outstanding updates exist End of module CLNTOUT. if necessary UVERSCHK_GEN.LOG Unlock clients for SAP upgrade. if necessary JOB_RXPRECHK_PRE PXPRECHK.LOG FRONTREQ_PRE UVERS_CHK_GEN BATCHCHK_GEN PROFCHK PROFCHK.ELG PSVBCHCK.

6C Support Release 2: UNIX SAP AG PREPARE Module Activation Checks Phase JOB_RADDRCHK Actions Taken by PREPARE Log PADDRCHK.LOG PADDRCHK.ELG User Actions Determines tables that are converted during the upgrade (known to SAP) and writes them to a file for information purposes Totals results of all space checks ADDSPAREQ_AD 222 April 2001 .ELG User Actions Finds tables that can be reduced in size before the upgrade to speed up the conversion Prepares for the address data conversion If necessary reduce size of tables as described in Note 76431 If necessary.ELG CHECKGROUP_END End of module PREPARE Module Optional Checks for Conversions Phase CNV_LIST Actions Taken by PREPARE Log TABCONV.LOG RSUPGTAA.ELG User Actions Prepares for renaming the data elements Checks whether activation errors could occur during the upgrade End of module Correct name conflicts as described in Note 96905 Remove references to SAP data elements and domains ACTREF_CHK RSTODIRX.LOG RSTODIRX.LST RSUPGTAL. start report for preparing the address data conversion as described in Note 82167 JOB_RSCNVADR PSCNVADR.Upgrading to 4.LOG PSCNVADR.ELG CHECKGROUP_END PREPARE Module Necessary Checks for Conversions Phase CNV_AVOID Actions Taken by PREPARE Log RSUPGTAA.LOG RSUPGTAL.

LOG PSWBO230.LOG SPACECHK_OPT CHECKGROUP_END Check free space in DB End of module DBFPLUSD.SAP AG Upgrading to 4. if necessary PREPARE Module Modification Support Phase RUN_RDDIT006_PRE Actions Taken by PREPARE Log DIFFCALC.ELG User Actions Determines collision with central Basis objects Contact SAP to get modifications to central Basis objects.LOG ADJUSTCK. if necessary Use transaction SPDD or SPAU to display modifications ADJUSTCHK_PRE Determines objects to be adjusted (preparation for SPDD and SPAU) End of module ADJUSTCK.ELG User Actions Deletes SAP requests from previous upgrades End of module April 2001 223 .6C Support Release 2: UNIX DYNSPCADD Checks space requirements in the database dynamically: 1.LOG DIFFCALC.ELG ADJUSTMT. Space for new secondary indexes DYNSPC. Space needed temporarily for conversion 2.INF CHECKGROUP_END PREPARE Module Pre-Processing Phase RUN_RSWBO230_ PRE CHECKGROUP_END Actions Taken by PREPARE Log PSWBO230.LOG Extend free disk space.

There you can also find the main log file R3up. to restarting production operation. and helps you recognize frozen processes. The Upgrade Monitor lets you follow the upgrade as it occurs.log. Prerequisites The mandatory PREPARE modules have run successfully. • You can continue the upgrade by restarting R3up. R3up starts various tools. to importing the necessary programs. refer to the following Phase Lists for R3up. 224 April 2001 . At the beginning of its run. This occurs sequentially in phases where one phase must end successfully before the next one can begin. from checking the requirements.6C Support Release 2: UNIX SAP AG R3up Use R3up controls the entire upgrade process for an SAP System. You can stop R3up at the beginning of a specific phase or at the beginning of the next phase. The upgrade strategies are differentiated by the type of backup. R3up repeats all essential checks made by PREPARE. and when production operation stops. R3up stops and gives you several modes for restarting the upgrade. These logs are stored in the log subdirectory of the upgrade directory. Normally. In this case. For a complete list of all phases.Upgrading to 4. For example. the disk space requirements. Activities • • You start R3up. You can find a list of all R3up phases under Phase List for R3up. you can still use the SAP System productively. R3up makes the necessary checks and then starts at the point in the phase where the program terminated. When downtime begins and how long it lasts depends on the strategy you choose. you only need to restart the upgrade if errors occurred or an upgrade phase has terminated. checks the results and creates a series of logs. If you choose the default value repeat. During the checks. you need to do this if a Note tells you to correct a program before you execute it. In the individual phases.

R3up does not require an operator at this point. the runtime depends to a great extent on your own data. The runtime depends on the following criteria: − − − − • 1) Amount of customer data Number of SAP applications used Amount and type of modifications and customer developments Number of clients 2) Log If a phase name has comment . not all the logs can be specified in this column.6C. The following assumptions are made: − − Only one CD drive is used. Some phases are considerably shorter when you upgrade from 4. otherwise R3up requests that you make the entries described. • User Actions If nothing is entered here.6C.x to 4. The percentage duration of these phases can be very different in your upgrade. This is based on the upgrade from 3.x to 4.SAP AG Upgrading to 4. also read the section Logs under Troubleshooting. April 2001 225 . If a phase is marked with comment .6C Support Release 2: UNIX R3up Phase List Explanations of the columns: • Duration (percentage) This phase takes up this percentage of the total runtime of R3up. R3up Upgrade Phases Phase Duration (percent age) Actions Taken by R3up Log User Actions BEGIN INITPUT <1% --DB2 UDB Checks upgrade directory Initialize R3up DB2 Universal Database DB2 Universal Database DB6RUNST. You have not specified a latest time at which you want to go live (query define upgrade stop in the INITSUBST phase).LOG Enter parameters DB2 Universal Database 1% Update database statistics DB2 for OS/390 Choose MEDIUM or HIGH Checks parameters. If you have a problem.

asks for keyword for industry solution PATCH_CHK <1% PATCHOUT.LOG EXECPT. if necessary CLNT_CHK <1% CLNTOUT. upgrade OS or DB to required version VIEWCHK1. if necessary Enter parameters If necessary.6C Support Release 2: UNIX SAP AG ICLI server and JCL submission service DBCHK VERSCHK <1% <1% Determines DB and SAP version Checks SAP version Upgrade to a valid source release.LOG EXECCT.LOG UVERS_CHK BATCHCHK <1% <1% Checks consistency of table UVERS Tests whether background server can access the upgrade directory Determines nonconfirmed Support Packages and displays results Checks whether clients are locked for SAP upgrade Check whether the inactive nametab is empty Queries keyword from Note If necessary.used only for information Determines SAP objects locked in repairs or requests Informs users that they must import a new VIEWCHK1 <1% Delete tables.LOG Use transaction SPAM to confirm any unconfirmed Support Packages Unlock clients for SAP upgrade. if necessary REPACHK1 <1% REPACHK1. if necessary UVERSCHK.LOG BATCHCHK.LOG INITSUBST CONFCHK_X --<1% Initializes for Repository Switch Tests operating system and database version Determines collisions between delivered views and customer tables in the SAP namespace .LOG INTCHK <1% KEY_CHK --- Enter keyword for the upgrade Enter password for industry solution.Upgrading to 4.LOG FRONTREQ --- Confirm 226 April 2001 .

ELG ICNVREQ.LOG BTCTRNS1. if necessary Confirm Enlarge the file system.ELG DBFPLUSD.ELG ICNVCAND.6C Support Release 2: UNIX version of the SAPGUI JOB_RSVBCHCK2 <1% Checks whether outstanding updates exist Deletes SAP requests from previous upgrades As in PREPARE Prompts you to start ICNV if there are candidates for the ICNV.SAP AG Upgrading to 4. but ICNV has not yet been started Deletes incorrect templates for Create Table statements Checks freespace in the database SAP DB PSVBCHCK2.LOG Delete any terminated updates RUN_RSWBO230 <1% JOB_RXPRECHK ICNVREQ <1% <1% Call transaction ICNV.LOG PDDPURI2.ELG For strategy A_off.ELG PXPRECHK.LOG SPACECHK_ALL <1% Extend the database. if necessary JOB_RDDPURI2 <1% PDDPURI2.LOG PSVBCHCK2.LOG PSWBO230.LOG PXPRECHK.LOG EU_IMP0.LOG ICNVREQ. if necessary SAP DB Checks database parameter MAXLOCKS Raise the MAXLOCKS parameter to the minimum value.5B: Deschedules background jobs For strategies A_switch and A_on: Prompts time when ABAP Workbench should be locked LOCKEU_PRE <1% For strategies A_switch and A_on: Respond to prompt for lock time EU_IMPORT0 <1% If necessary.LOG FREECHK_X <1% Checks freespace in file system JOB_BTCTRNS0 <1% As of Source Release 4. stops system. if necessary BTCTRNS1.ELG PSWBO230.ELG LOCKEUPR. isolate the central instance and stop all application servers Mount CD Upgrade CD3 April 2001 227 . Imports information on code page conversion from Upgrade CD3 into shadow area EU_IMP0.

ELG Mount CD Upgrade CD4 EU_IMPORT5 14% EU_IMP5.BUF into the R3up buffer Copies upgrade EU_IMP3.LOG 228 April 2001 .LOG TRB2H.ELG Mount CD Upgrade CD3 EU_IMPORT4 9% EU_IMP4.LOG EU_IMP2. if necessary CNV_CHK_XT <1% TRBATCHK_XT TR_BUF2HEAP_ INSTIMP <1% <1% Perform any actions specified by R3up TPSHBUF.LOG EU_IMP1.6C Support Release 2: UNIX SAP AG EU_IMPORT1 EU_IMPORT2 <1% <1% Creates substitution tables for ABAP loads Creates ABAP tables EU_IMP1.LOG REPACHK2 <1% REPACHK2.LOG TR_BUF2HEAP_ TABULONG <1% TPSHBUF.LOG EU_IMP5.LOG Confirm locks for ABAP Workbench if not yet done in LOCKEU_PRE Make conversions (after discussion with Basis consultant).Upgrading to 4.LOG EU_IMP3.LOG TRB2H.ELG EU_IMP2.LOG EU_IMP4.LOG TR_APPENDBUF_ <1% TRAPPB. if necessary EU_IMPORT3 2% Imports substitution set from Upgrade CD3 into the shadow tables Imports substitution set from Upgrade CD4 into the shadow tables Imports substitution set from Upgrade CD5 into the shadow tables Imports views of shadow tables Starts system if it was stopped during EU_IMPORT0 Determines SAP objects locked in repairs or requests Determines outstanding conversions and restart logs of terminated conversions Checks whether table TRBAT is empty Puts upgrade requests of the buffer INSTIMP.ELG Mount CD Upgrade CD5 EUVIEWIMP STARTR3_IMP <1% <1% ALTER34V.ELG Mount CD Upgrade CD3 Mount CD Upgrade CD3 DB2 for OS/390 Edit RUNSTATS jobs.BUF into the R3up buffer Puts upgrade requests of the buffer TABULONG.

LOG SYSPREP.ELG NTSHDCP.LOG LISTLOAD.LOG JOB_RDDTAXIT SUBSTNT_INS <1% <1% SYSPREP.LOG RUN_RSINCGEN <1% PSINCGEN.INF SHDTSEL.ELG DIFFCALC.LOG TR_CMDIMPORT_ UPG NEWTAB_CHK NEWTAB_CRE LIST_LOAD 2% <1% NEWTABCR.LOG DIFFCALC. if necessary SHADOW_CAND_SEL <1% SHADOW_PUTTB_ FILL SHADOW_NTACT_CP <1% <1% PREPPCON_INIT RUN_RDDNT4MD <1% <1% April 2001 229 .LOG XTTSIZE0.ELG TRCMDUPG.LOG SHDTTABS.LOG NEWTABCK.6C Support Release 2: UNIX UPG requests from the R3up buffer to the hyperbuffer <1% <1% Command file import of upgrade requests Determines which tables are new in this release Creates tables that are new in this release Creates list of programs to generate after upgrade Selects generated objects Creates nametab entries for the new substitution tables Generates include program for access to the substitution tables Determines deviations of the current system from the future SAP standard (objects and modifications that have to be copied) Determines DDIC objects to be adjusted Determines candidates for shadow import Generates entries in PUTTB for shadow import Generates nametabs of the shadow tables in the shadow nametab Prepares parallel DDL processing in PCON Adjusts structural changes to the source release TRCMDUPG.LOG PDDNT4MD.LOG PN*.LOG PSINCGEN.LOG SHDTABU.ELG ADJUSTMT.ELG SHDTABU.ELG NTSHDCP.LOG ADJUSTCK.LOG SHDTTABS.ELG Confirm R3up message.LOG PDDNT4MD.ELG STBNTINS.ELG RUN_RDDIT0061) 1% ADJUSTCHK1) <1% ADJUSTCK.SID PREPCON.SAP AG Upgrading to 4.

6C Support Release 2: UNIX SAP AG RUN_RDDNT4DL <1% Prepares nametabs in the shadow tables for the new tables Export documentation created/modified by the customer Copies objects for add-ons to the shadow tables Copies generated objects to the shadow tables Transfers unsent modified objects to the shadow tables Copies customer developments to the shadow tables Exports inactive DDIC versions Exports customer extensions to documentation on SAP objects Exports the documentation on customer objects Exports modifications to documents Exports local private objects and tests objects in SAP namespace Imports upgrade data and language data into the shadow tables and the new tables Imports Support Package data and add-on data into the shadow tables Copies technical settings in DDIC Copies TADIR entries PDDNT4DL.ELG DIFFEXPO.ELG DIFFEXPC.ELG DIFFEXPA.ELG DIFFEXPD.LOG PSPUSCA4.ELG DIFFEXPR.LOG DIFFEXPG.ELG PSPUSCA4.LOG DIFFEXMO.LOG PDDSAVTE.LOG DIFFEXPD.ELG DIFFEXPT.ELG DIFFEXPMDOC1) DIFFEXPTSAP1) <1% <1% SHADOW_IMPORT_ ALL <5% SHDALLIMP.Upgrading to 4.LOG DIFFEXPG.LOG DIFFEXPC.LOG DIFFEXCO.LOG DIFFEXPT.LOG DIFFEXPO.ELG JOB_RDDSAVTE RUN_RDDCP4TB <1% <1% PDDSAVTE.LOG DIFFEXPR.LOG 230 April 2001 .LOG PDDNT4DL.ELG PDDCP4TB.ELG DIFFEXPA.ELG SHADOW_IMPORT_ REP <5% SHDREPIMP.ELG JOB_RSPUSCAD1) <1% DIFFEXPADD <1% DIFFEXPGEN1) 2% DIFFEXPMOD1) <1% DIFFEXPCUST1) <1% DIFFEXPDDIV DIFFEXPDOCU1) <1% <1% DIFFEXPCDOC1) <1% DIFFEXCO.ELG DIFFEXMO.

5B: Deschedules background jobs Deletes inconsistent values from tables Deletes nametab entries created in SUBSTNT_INS Deletes nametabs of the shadow tables in the shadow nametab Determines conversions that stopped Checks whether table TRBAT is empty Check whether the inactive nametab is BTCTRNS1.LOG STARTR3_TRANS JOB_BTCTRNS1 <1% <1% JOB_RDDPURIF SUBSTNT_DEL <1% <1% SHADOW_NTACT_ DEL CNV_CHK_SW <1% NTSHDDEL.LOG RSTRESNC.ELG PDDPURIF.ELG <1% Deletes entries of objects to be deleted in the TADIR shadow table Copies namespace reservations to the shadow tables Copies nametabs to the shadow tables Determines conflicts between delivered views and customer tables in the SAP name range Stops system and changes profiles PDDDL4TB.ELG STBNTDEL.LOG NTACT_PREMV VIEWCHK2 <1% <1% Delete tables.ELG VIEWCHK2. isolate the central instance and stop all application servers CONFCHK_BAS <1% Tests operating system and database version Starts system As of Source Release 4.6C Support Release 2: UNIX that have not been delivered to the shadow tables RUN_RDDDL4TB PDDCP4TB.LOG PDDPURIF. if necessary MODPROF_TRANS <1% ALPXPOOL.SAP AG Upgrading to 4.LOG PDDDL4TB.LOG ALPXDEF.ELG <1% TRBATCHK_SW INTCHK_SW <1% <1% April 2001 231 .ELG RUN_RSTRESNC <1% RSTRESNC.LOG NTSHDDEL.LOG NTMOVPRE.LOG For strategies A_switch and A_on.LOG BTCTRNS1.ELG NTMOVPRE.

LOG DISTBPRE.LOG INXDEL.LOG DISTBAS.ELG INXPREP.LOG RDCLTAF1.LOG DUMP_CNV.LOG PDDYT2NT.ELG UVERS_UP_B JOB_RSVBCHCK3 <1% <1% PSVBCHCK3.ELG PADISWTC.LOG PSVBCHCK3.LOG INXPREP.ELG BASDDIMP.Upgrading to 4.ELG STOPR3_DIST STARTR3_DIST RUN_PRELDIST <1% <1% <1% DISTBPRE.LOG NTDELFIN.LOG NTMOVFIN.ELG PORT_IMP.ELG NTDELFIN.ELG JOB_RDDGENBB <1% DUMP_CNV 1% 232 April 2001 .LOG PADISWTC.ELG Clear all outstanding updates JOB_RDDINDPR JOB_RDDINDDL <1% <1% JOB_CLTAF1 PORT_IMP2) <1% <1% RDCLTAF1.ELG DISTBAS.ELG INXDEL.ELG DUMP_CNV.ELG NTACT_MV NTACT_DEL BASDDIMPORT2) <1% 1% <1% NTMOVFIN.6C Support Release 2: UNIX SAP AG empty RUN_RDDYT2NT PRUN_RADISWTC CNV_CHK_ICC <1% <1% <1% Prepares conversion of Basis tables Completes incremental conversion Determines halted conversions of the incremental conversion Copies nametabs to the shadow tables Adjusts nametabs of structures Imports DDIC source for tables relevant to Basis Changes status in table UVERS Checks whether outstanding updates exist Determines all secondary indexes Deletes inconsistent secondary index definitions for tables relevant to Basis Deletes table TATAF Imports requests for porting-dependent modifications Stops system Starts system Prepares distribution run for the tables relevant for Basis Distributor run for tables relevant for Basis Writes table contents for external conversion PDDYT2NT.

LOG EXECSMF.LOG ALTERD4V.LOG EUSWITCH.6C Support Release 2: UNIX to file system DEL_CNV <1% Deletes table contents written to the file system from the system Converts tables relevant to Basis Stops system Converts tables externally and writes contents into system Special handling of table TATAF Switches to new Repository Creates new ABAP load tables Adjusts substituted nametab entries for DB objects to the target system Deletes inactive nametabs of nondatabase objects Changes status in table UVERS Creates table VBDATA on the database Deletes views of the shadow tables Deactivates Session Manager for the upgrade Cleans up conflicts between delivered views and tables delivered previously Creates Basis views Stops system and changes profiles Tests/switches environment of the DEL_CNV.ELG ALPX.LOG LOADCRE.ELG UVERS_UP_S ALTER_VBDAT ALTER_D4V EXEC_SMOFF <1% <1% <1% <1% ALTERVB.LOG April 2001 233 .ELG XTERN_CNV.ELG CNV_SUBMIT2) STOPR3_BAS XTERN_CNV 1% <1% 2% CNV_SUB.ELG ALTER_TAF EU_SWITCH LOADCRE NTACT_RWR <1% <1% <1% <1% NTACT_NOBD <1% NTNOBD.ELG XTERN_CNV.ELG NTRWR40.SAP AG Upgrading to 4.LOG ALPXDP.LOG LOADCRE.LOG VIEWIMP_BAS MODPROF_BAS2) ENVCHK <1% <1% <1% VIEWIMP.LOG VIEWPRP <1% VIEWPRP.LOG DEL_CNV.LOG XTERN_CNV.LST ALTERTF.LOG CNV_SUB.LOG NTRWR40.LOG VIEWIMP.LOG NTNOBD.

LOG STARTR3_NBAS JOB_CLTAF2 JOB_RSWBOUP1 <1% <1% <1% RDCLTAF2.LOG RDDNEWPP.ELG RDDNEWPP.LOG PDDDL4TA.0D: Sets table for the language area Starts system Deletes table TATAF Initializes and adjusts tables for Workbench Organizer Reschedules RDDIMPDP Initializes new administration of customer modifications Clears defective records in table T510Q Adjusts matchcodes automatically Marks matchcodes for activation Appends shadow import in upgrade No actions Imports requests for porting-dependent modifications Deletes TADIR entries of temporarily generated objects If necessary.Upgrading to 4.ELG DDIC46C.LOG RDCLTAF2. imports the result of transaction SPDD from a development system KX_SW.ELG RPU510Q2.ELG ALTER_DLG TABUIMP_WBO2) AREA_SET <1% <1% <1% ALTERDLG.LOG TABUIMP.LOG RPU510Q2.ELG ADDMCM.LOG RSUMOD03.ELG DDIC_46C2) <1% 234 April 2001 .LOG RSWBOUP1.6C Support Release 2: UNIX SAP AG user <sapsid>adm KX_SWITCH TABUIMP_BAS2) <1% <1% Switches SAP Kernel Imports (a few) table entries needed to start the system with the new SAP Kernel Creates table DDLOG Imports standard transport layers Source Release 3.LOG TABUWBO.ELG RSUMOD03.LOG ADDMCM.ELG PDDMCMRG.ELG JOB_RDDNEWPP JOB_RSUMOD03 <1% <1% JOB_RPU510Q2 JOB_RDDMCMRG ADDTOBUF_MCM APPENDBUF_ UPGRADE APPENDBUF46C PORT_IM22) <1% <1% <1% <1% <1% <1% PORT_IM2.ELG RSWBOUP1.ELG LANGAREA.LOG PDDMCMRG.ELG JOB_DL4TA_46C <1% PDDDL4TA.

LOG ACT46C.6C Support Release 2: UNIX SVERSCHK_46C <1% Checks table SVERS to see whether the new SAP version was created successfully Renames data elements with naming conflict in customer namespace Checks and repairs entries in the table DDTYPES Adjusts structure of tables to DB Activates DDIC customer objects Checks secondary indexes Removes table TMF18 from the set of substituted tables Deletes inconsistent views DB2 for OS/390 PSUMOD20.ELG PADDREXE.LOG PCON_46C1)2) 7% PCON46C.LOG XTTSIZEI.ELG PDDMVSUB.SAP AG Upgrading to 4.LOG PADDREXE.LOG INDEXCHK. if necessary RUN_INDC_46C JOB_MVSUB_46C <1% <1% INDEXCHK.LOG STOPR3_I46C TMPLDINV <1% <1% PMVNTAB_46C 3% PMVNT46C.ELG PMVNT46C.LOG ALTERVID.LOG PSDB2XTT.ELG PSDB2XTT.LOG PREPCON.ELG PCON46C.ELG PDDMVSUB.LOG April 2001 235 .LOG RUN_DREXE_46C <1% JOB_RUTTYREP <1% JOB_UMOD20_46C ACT_46C1)2) <1% 2% Use SPDD to adjust ABAP Dictionary objects.ELG PSUMOD20.LOG SQLLDINV.LOG ALTER_VID JOB_RSDB2XTT <1% <1% Generates control entries for parallel conversion JOB_RSDB4XTT PREPPCON_INX <1% <1% No actions Prepares parallel DDL processing in PCON. selects tables that get an index Converts application tables and activates their nametab entries Stops system Validates ABAP loads created since the STARTR3_NBAS phase was generated Converts application views and activates remaining nametab TMPLDINV.

LOG PDDLDINV.6C Support Release 2: UNIX SAP AG entries STARTR3_I46C JOB_DCXTF_46C JOB_LDINV_46C STOPR3_L46C LD_SWITCH_46C VIEWIMP_46C STARTR3_NL46C JOB_DBDIF_46C TABIM_46C2) ALTER_TABIMUPD STARTR3_TB46C JOB_RSWBOUP2 <1% <1% <1% <1% <1% <1% <1% <1% 12% <1% <1% <1% Starts system Deletes and recreates table DDXTF Deletes temporary loads again Stops system Switches to new ABAP loads Creates Basis views (DROP/CREATE) Starts system Clears table DBDIFF on the database Imports entries to the control tables Updates statistics for some tables Starts system Initializes and adjusts tables for Workbench Organizer Imports ADOs Converts matchcodes Activates lock objects Automatically repeats phase once if an error occurs PSWBOUP2.ELG PSDCDDXT.LOG REIMPDOC.ELG UEXP_46C REIMPDDN_46C REIMPDOC1) <1% <1% <1% If necessary.ELG TABIM46C.ELG TABIMERR.LOG VIEWIM46C.Upgrading to 4.ELG PADDBDIF.ELG REIMPCDOC_LOG REIMPCDOC1) <1% 236 April 2001 .ELG PDDLDINV.LOG PSWBOUP2.LOG REIMPDDN.ELG REIMPDDN. exports adjusted DDIC objects Re-imports inactive DDIC versions Reimports customer extensions to SAP object documentation Re-imports UEXP46C.LOG PADDBDIF.LOG LDSWITCH.ELG REIMPDOC.ELG ADOIM46C.ELG ADOIM_46C1)2) 9% XPRAS_46C1)2) 11% Executes XPRAs Automatically repeats phase once if an error occurs XPRAS46C.LOG VIEWIM46C.LOG PSDCDDXT.

LOG REIMPMDOC.LOG JOB_RSTLANUPG . starts system Sets the status of the installed languages STARTR3_46C JOB_RSTLANUPG <1% <1% JOB_RSTLANUPG .ELG REIMPMDOC.LOG PSDLDSEQ.LOG JOB_RUTTYREP1 <1% JOB_DBPROD_46C1) <1% PRODCHK_46C <1% JOB_RDDIT022 JOB_RSMODACU DBCLEAN_46C1) JOB_RSDLDSEQ JOB_RDDNTPUR EXEC_SMON MODPROFP_46C <1% <1% <1% <1% <1% <1% <1% Confirm SAP DB Strategies A_on or A_switch: Prompts you to back up the Back up the database and confirm April 2001 237 .ELG TR_PATCH_STATUS _UPGRADE <1% Updates status information for Support Packages that have been included Checks and repairs entries in the table DDTYPES Executes DB-specific operations for restarting the system Checks requirements for production operation Updates table AVERS Activates CMOD enhancements Cleans up database Cleans up screen sequence control Cleans up nametab Reactivates Session Manager Stops system and resets profiles SAP DB DBCLEAN46C.LOG RDDIT022. LOG PUTTYREP1.ELG PSDBPROD.ELG EXECSMN. ELG PSDBPROD.ELG PDDNTPUR.LOG ALPXP.ELG PUTTYREP1. LOG PSDLDSEQ.SAP AG Upgrading to 4.LOG PDDNTPUR.LOG RDDIT022.6C Support Release 2: UNIX documentation on customer objects REIMPMDOC1) REIMPCDOC.ELG <1% Reimports modifications to documents If necessary.

LOG UEXPSPAU.6C Support Release 2: UNIX SAP AG database STARTR3_P46C REQJOBRES <1% <1% Starts system As of Source Release 4.LOG PDDDBSTA.Upgrading to 4.5B: Prompts you to schedule background jobs Imports authorizations into client 066 (EarlyWatch) --Tests target version Changes status in table UVERS Updates DB table statistics Sets installation status to OK Adjusts documentation for renamed data elements (executes report RADDRDOC) Prompts start of transaction SGEN Displays P errors PDDDBSTA.ELG PADDRDOC.ELG UEXPSPAU <1% JOB_UPGDELPROG SAVELOGS <1% <1% Choose between: normal (only important) all none EXITINFO EXIT --<1% Displays Notes on post-upgrade activities Ends R3up Confirm 238 April 2001 .LOG PSUPGEND. exports objects adjusted with transaction SPAU --Copies upgrade logs to /usr/sap/ trans/upgrade SAVELOGS.ELG PSUPGEND.ELG EWIMPORT_46C <1% END ENDCHK UVERS_UP_END JOB_RDDDBSTA JOB_UPGEND_46C JOB_DRDOC_46C <1% <1% <1% <1% <1% 2% REQGENLD CHK_POSTUP ----- Confirm Correct P errors before restarting production operation Confirm SPAUINFO --- Displays information for adjusting objects with transaction SPAU If necessary.LOG PADDRDOC.ELG EWTCH066.

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

Upgrade Assistant
Use
The Upgrade Assistant is the frontend for the upgrade process. It provides one or more graphic user interfaces (GUIs) for controlling and monitoring the upgrade. The Upgrade Assistant simplifies the upgrade procedure.

Integration
The Upgrade Assistant is a distributed program consisting of a server component and several GUI components. Only one person can control the upgrade from the GUI components.
• Server component

The server ensures communications between the upgrade control program R3up and the GUIs of the Upgrade Assistant. It must be started on the host on which you want the upgrade process to run.
• GUI components

The GUI components can be executed on any other hosts. You can log on to the server as the observer or the administrator. The observer role only authorizes you to monitor an upgrade. An administrator is authorized to take actions affecting the progress of the upgrade, for example an administrator can start or stop the upgrade and can enter any necessary commands. Only one GUI can assume the role of administrator. However, the GUI with this role can change in the course of the upgrade. The graphic below illustrates the architecture of the Upgrade Assistant and the interaction between the Upgrade Assistant and the R3up upgrade control program.
Upgrade Assistant

GUI GUI (Observer) (Observer)

Central Instance

GUI GUI (Administrator) (Administrator)

Server Server

R3up R3up

GUI GUI (Observer) (Observer)

Functions

You can control and monitor the progress of the upgrade from a number of different places.

April 2001

239

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Frontend and upgrade process are divided into separate components so that the entire upgrade does not terminate if a connection fails. This provides optimal support for a remote upgrade.

• •

You have an alert mechanism that lets you start an external program. Provided you have access to the Internet, you can access the SAP Notes database in the SAP Service Marketplace from a GUI.

The Upgrade Assistant is implemented in Java. A scroll mode is provided for the upgrade for platforms not supporting Java. We recommend using the Upgrade Assistant, since scroll mode does not provide the above features.

240

April 2001

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

Using the Upgrade Assistant
Use
The Upgrade Assistant offers you a number of functions. You can change the passwords for the roles, change roles, use and monitor PREPARE, or look for Notes.

Changing the Passwords
The passwords for the two roles can only be changed from the administrator GUI. In the main menu choose Administrator →Change passwords.

Changing the Role
By choosing File → Change role you can change role dynamically. The following dialog box appears:

If, for example, you are in the role of the observer and enter the password for the administrator you change to the administrator role. If an administrator already exists at this time then the administrator role is taken away from them. If you only want to change the User name or the Phone number, then enter the password of the role you are in. In this case only the entered data is updated.

Searching for Notes from the GUI
If you have an Internet connection, you can access SAP Notes in SAPNet using the GUI. In the main menu, choose Services → SAP Notes Search.

More Information on the Upgrade Assistant
To display a description of the Upgrade Assistant with all its functions, choose Help → Introduction in the main menu.

April 2001

241

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

Upgrade Monitor
Use
The Upgrade Monitor lets you monitor the upgrade, and helps you recognize any processes that have stopped.

Functions
The monitor estimates the time when the upgrade ends, as well as other important stages (milestones). These estimates are based on SAP reference times and the runtimes of upgrade phases that have already completed. The output of the monitor is updated every 60 seconds. The more advanced the progress of the upgrade is, the more precise the estimates are. If possible, the runtime estimate also includes any runtime that is lengthened for systematic reasons, however this is subject to restrictions. Systematic fluctuations can also occur if the upgrade phases run more quickly than expected. This means that the end of the upgrade cannot be estimated precisely. The data appears on the screen, but the way it is displayed depends on if you are upgrading the system with the Upgrade Assistant or in scroll mode.

Graphical Display in the Upgrade Assistant

242

April 2001

2. The upgrade processes that are running appear under Current activities. one of the upgrade processes is stopped. Procedure in Scroll Mode: 1. Starting the Upgrade Monitor Procedure Procedure in the Upgrade Assistant: Go to the main menu and start the Monitor by choosing Services → Upgrade Monitor. the bar appears in green. Enter the following commands in the new window: cd <upgrade_directory>/bin . Open another window at the operating system level. This may be the Upgrade Monitor. and therefore cannot display them. If the graphic is not moving.6C Support Release 2: UNIX The total runtime of the upgrade and the runtime of the next milestone appear as bar graphs. so the progress of the upgrade and the estimated runtime until the next milestone are shown in numerals. Numerical Display in Scroll Mode No graphics are displayed in scroll mode. the bars appear first in yellow and then in red. the Upgrade Assistant or the R3up program.SAP AG Upgrading to 4. As long as the runtime has not been exceeded. An animated graphic displays the activity of the upgrade processes. If the runtime has been exceeded. The upgrade processes that are running appear under Current activities. The monitor does not recognize any subprocesses of these processes./R3up gt=SCROLL Monitor April 2001 243 . Note that the process bar is updated only every 60 seconds.

First. If step one is not successful. 244 April 2001 . contact SAP Local Support. 2. This means that the upgrade processes are hanging. try and find out why the runtime is so long. 2. The restarted R3up must wait for these processes before the upgrade can continue with any other actions. restart R3up. Check the database and CPU activity. then either runtime has been exceeded significantly. any processes that are still running are displayed. The graphic that displays the activity of the upgrade processes is not moving. If the previous steps are not successful. restart the Upgrade Assistant GUI only. do not terminate the upgrade. When R3up is restarted. or the upgrade is in an endless loop. If you can still detect activity. instead. restart the Upgrade Assistant server. 3. • • One of the bars showing the progress of the upgrade is red. If you are unsure how to proceed. Procedure for Upgrade Processes that Are Frozen 1. Procedure for Status Red 1. If this is the case.Upgrading to 4.6C Support Release 2: UNIX SAP AG Understanding the Upgrade Monitor Display Use The following Upgrade Monitor display indicates that you may have to intervene.

Sign up to vote on this title
UsefulNot useful