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

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

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

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

and SAP Basis knowledge. Read these sections for an overview of the actions required before. and any other documentation referred to in this documentation. In addition to this documentation. this documentation also includes a checklist for the upgrade [Page 13] with all the necessary actions for planning.Upgrading to 4. the SAP Implementation Guide (IMG). The following four sections explain the procedure for the upgrade. such as the Release Notes for the applications that you implement. you require some other information. database. preparing. 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. 8 April 2001 . the Notes that are specific to this upgrade [Page 40]. performing and following up the upgrade. The information in this documentation is intended for SAP system administrators with operating system.6C Support Release 2: UNIX Purpose This documentation describes the upgrade and provides you with additional information on upgrade topics. the administration tasks you need to perform before and after the upgrade.6C Support Release 2: UNIX SAP AG Upgrading to 4. Constraints This documentation only applies if you are upgrading your SAP System on UNIX. 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.

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

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

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

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

If necessary. since it does not include all the information relevant to the upgrade. 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. and following up the upgrade. preparing. upgrade the operating system and database system Preparations for PREPARE Preparing for PREPARE Activity Choose the correct host for PREPARE and the Upgrade Assistant. If necessary. 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 . meet the requirements for the SAP Internet Transaction Server and the SAP@Web Studio according to the installation guide SAP@Web Installation Guide. make preparations for importing additional languages If necessary. Upgrade Assistant. 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.SAP AG Upgrading to 4. Prepare the empty upgrade directory with <sapsid>adm as the owner. operating system) Meet the requirements for installing the online documentation according to the guide Installing the SAP Library.6C. performing.6C Support Release 2: UNIX Checklist for the Upgrade Definition This checklist includes all activities necessary for planning. It is not intended to replace the documentation Upgrade to 4.

process batch input sessions For source releases 3.0x. check version of SAP Kernel For source release 4. 3.0x/3. 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.6C Support Release 2: UNIX SAP AG work.1x. 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. Make operating system-specific preparations: Make sure that you can recover the database to the state it had before the upgrade. upgrade frontend software 14 April 2001 . Make database-specific preparations for PREPARE For source releases 3. provide an extra 300 MB of memory for each language in the database. such as entering CD mount directories Making Entries for the Initialization Module Make entries for the Read CD module.x. such as including Support Packages. If you want to import languages other than English and German.Upgrading to 4. 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. material master (industry): process the direct input error data If necessary.1x in translation systems. Also do this if you want to include Support Packages and add-ons.1x. back up the SAP start and stop scripts.1x.0x/3.0x/3. 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.

start secondary application server For A_switch and A_off. and back up upgrade directory For A_switch. lock the ABAP Workbench if necessary Phase EU_IMPORT0: For A_off. stop application server. check converted percentage rate Phase REPACHK2: For A_switch and A_on. determine P errors.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. enter keyword for industry solution Phase INITSUBST: Determine when to restart production operation For A_switch and A_on. change database recovery mode. confirm the transfer request if necessary Phase VIEWCHK2: delete customer tables if necessary Phase MODPROF_TRANS: For A_switch and A_on.SAP AG Upgrading to 4. determine P errors. last chance to lock the ABAP Workbench Phase ADJUSTCHK: If there are modifications. adjust any modified SAP objects with the SAP standard Phase PRODCHK_<Rel>: Choose a new time for restarting production operation or: For A_on. start secondary application server April 2001 15 . back up database. specify the runtime of the import of the substitution set Phase LOCKEU_PRE: For A_switch and A_on. change database recovery mode. isolate central instance. 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. and change database recovery mode. stop application server. change the database recovery mode if necessary Phase ENVCHK: if necessary. if necessary For ICNV. isolate central instance.

distribute SAP programs For source releases 3. reschedule jobs with transaction DB13 If necessary.0x/3.0x/3. perform upgrade and delta Customizing For HR customers: reload table T512W (Wage Types in HR) 16 April 2001 . adjust Repository objects with transaction SPAU If necessary. 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.6C Support Release 2: UNIX SAP AG Post-Upgrade Activities Activities Before Starting Production Operation Activity Execute the script saproot.1x. 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: if remote application servers exist. re-install additional programs such as RFC-SDK or CPIC-SDK from the CD Presentation For source releases 3. reset to default value Actions After Starting Production Operation Activity Import any Support Packages that you need If you want to install additional languages.sh Perform database-specific actions If there is no central software storage point.0x/3.1x. rename local system logs Check profile parameters using transaction RZ10 and if necessary.Upgrading to 4. post-upgrade activities: If necessary. migrate matchcodes in search help objects. 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.

install more dialog instances Evaluating the Upgrade Runtime Activity Analyze the runtime of the upgrade using report RSUPGSUM / Send list to SAP with SAPNet .R/3 Frontend connection April 2001 17 .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.0x/3.SAP AG Upgrading to 4.

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

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

Upgrading to 4. you can recover the database to its state after the import of the substitution set. The upgrade strategy also determines the times at which you must make a complete backup of the system. This part of the procedure can run during production operation. 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 . SAP Upgrade Strategies There are three upgrade strategies available: A_switch • • • Imports the substitution set during production operation. Database mechanisms save database actions that occur in the first half of the upgrade. "Shadow tables" are tables which the running SAP System does not recognize at this point. In the second half of the upgrade.6C Support Release 2: UNIX SAP AG Planning the Upgrade Strategy Purpose Choose the upgrade strategy best suited for your SAP System. You can recover the database to its current state during the first half of the upgrade. You can no longer operate the system productively. • 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. • 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. − 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.

For A_switch the mode in which the database operates is changed. A_on and A_switch are identical until phase MODPROF_TRANS. The upgrade is divided into phases. the downtime begins in phase EU_IMPORT0. It does not take differences in the duration of the upgrade into consideration. 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. The mode in which the database operates changes. A_off • • • Production operation ends before the substitution set is imported.6C Support Release 2: UNIX A_on • • • Imports the substitution set during production operation.SAP AG Upgrading to 4. The procedure is the same for all the strategies up to phase EU_IMPORT0. You can recover the database to its current state during the entire upgrade. since these mark the beginning of downtime. Database mechanisms save database actions that occur in the during the entire upgrade. The important phases are EU_IMPORT2 and MODPROF_TRANS. Database mechanisms do not save database actions during the upgrade. You can only recover the database to its state before the import of the substitution set. Then downtime begins for both. depending on the strategy chosen. 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. With strategy A_off. The graphic below shows the upgrade procedure for the different strategies. but not for A_on. April 2001 21 .

0 The following graphics show an analysis of the upgrade runtimes and downtimes registered by SAP customers for Releases 4. you choose the runtime of the import [Page 26] yourself. and the time it takes to create the database archives.Upgrading to 4. the better the performance during production operation. 22 April 2001 .5 15.0 0.6.0 .0 13.5 A_off 0. The longer the runtime you choose. This data has not been sorted by operating system. The downtime depends on the upgrade strategy you choose.0 12. Comparison of the Archives in GB A_switch SAP DB DB2 UDB Informix Oracle 7.0 0. source release or database size. If you choose the strategies A_switch or A_on.0 22.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. Each additional language that you import increases the minimum duration of the import by about an hour. These sizes are based on sample data. The following table shows the sizes of the archives created for the different upgrade strategies and databases.4. database type.5 7.5 7.0 0.5 A_on 9.

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 .SAP AG Upgrading to 4.

Strategy A_on also allows you to work productively at the end 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. 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.6C Support Release 2: UNIX SAP AG Your source release can influence the runtime and downtime of the upgrade by up to approximately 25%. The following table shows you how much time you can gain for production operation by using strategy A_switch or A_on. 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. 24 April 2001 .Upgrading to 4. Both strategies allow you to work productively during the first half of the upgrade.

April 2001 25 . you do not need to wait until R3up completes its run before resuming production operation. for example. When selecting this time.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. The upgrade always executes up to the PRODCHK_46C phase. In this case R3up informs you that the SAP System can resume production operation although R3up is still active. You are also requested to carry out certain actions (for strategies A_off and A_switch.SAP AG Upgrading to 4. even if the time you entered is earlier. If R3up has reached the post-upgrade phases when this time is reached. pay attention to the following: Production operation is only possible from upgrade phase PRODCHK_46C onwards. This reduces the downtime towards the end of the upgrade and during post-upgrade activities. it is necessary to make an offline backup).

the import will be slowed down accordingly. DB2 for OS/390 and Informix) that need to be saved per hour.Upgrading to 4.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. specify total runtimes of about 24 hours. 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. If you enter a longer runtime. DB2 Universal Database. Depending on the start time of the upgrade. an import takes about six hours without delays. 26 April 2001 .

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

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

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

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

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

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. Start post-upgrade activities Back up database offline Friday Saturday Saturday 21:00 9:00 April 2001 35 . as described under Isolating the Central Instance.SAP AG Upgrading to 4.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. 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. if required. as described under Isolating the Central Instance. Adjust modifications.

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

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.6C Support Release 2: UNIX Planning the Modification Adjustment Purpose If you are sure that your SAP System corresponds exactly to the SAP standard.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. Requests in the customer namespace (number range 900000 to 999999) “modify” the SAP objects included in them. The modification adjustment lets you make your modifications to the appropriate new objects in the upgrade.Basis Components → ABAP/4 Development Workbench → Enhancements to the SAP Standard → The SAP Software Change Registration Procedure (SSCR). Objects belonging to the central Basis component are always returned to the SAP standard by the Repository Switch. When you upgrade the system. To safeguard existing modifications of this kind. see the SAP online documentation.x Choose Help → SAP Library → BC . the error message TG140 appears in phase RUN_RDDIT006. which you should obtain before upgrading. you lose any modifications you made to objects that conflict with SAP modifications. For more information. then contact an experienced Basis consultant for help. Release 4. Prerequisites To adjust modifications.x Choose Help → R/3 library → BC . During the Repository Switch. Release 3. the modifications have to be preliminary corrections.Basis Components →ABAP Workbench → BC . 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. including Support Packages. you might need an SSCR key. If the development system contains more modifications. The following explanation assumes that the levels of modification are identical. otherwise the SAP System would not be able to operate. April 2001 37 .Changing the SAP Standard → The SAP Software Change Registration Procedure (SSCR). All other requests are dealt with as preliminary corrections. you can skip this section. You can identify modifications as repairs to the SAP standard or as imports of SAP objects.

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

SAP AG Upgrading to 4. After this has taken place. logging on with an old version of SAP GUI may cause errors. log on only with new frontend software Production op. 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. 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. For more information. 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.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. April 2001 39 . The latest possible time for upgrading is before you log on to the new version of the SAP System for the first time. see the SAP Frontend Installation Guide.

which give you additional information. You must read the general Upgrade Note before you prepare the upgrade. 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 . which you can get from the current general Upgrade Note 390062. you require some additional information. If you do not have a SAPNet link. When you actually upgrade the system you need the information from some additional SAP Notes.Upgrading to 4. This information is kept in a number of SAPNet – R/3 Frontend Notes. not included in the documentation. There are separate SAP Notes for the database-specific sections. 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. if necessary. This SAP Note contains current non-database-specific information on preparing for the upgrade. You cannot start the upgrade until you have entered the keyword. this documentation also refers you to other SAP Notes. The following is a list of these SAP Notes. use the fax request form included in the software package. Other SAP Notes As well as the SAP Notes you need for preparing the upgrade.6C Support Release 2: UNIX SAP AG Notes for the Upgrade Definition To prepare and perform the upgrade of your system. you are asked to enter a keyword. These SAP Notes are named at the appropriate places in this documentation.

0B Preliminary information on freespace in the database System requirements for frontend workplaces / SAP GUI Installation of a 3.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.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. 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 .0A/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 .6C Resource requirements for Release 4.6A Resource requirements for Release 4.SAP AG Upgrading to 4.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. 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.

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.2.5 B00 Add Devspace under SAP DB (ADABAS for R/3) 6.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.1 SAP DB load with parallel R3LOADS Change a database parameter in SAP DB Release 7.6C language import Space requirements for the 4.2 New software structure as of SAP DB Version 7.6x SAP DB SAP DB database upgrade to 7.2.6x DB2 UDB DB2 Universal Databasespecific 42 April 2001 .2 Back up the database SAP DB 7.Upgrading to 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.

4.1H.6A.6B) DB2/390: Free space for 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.1I.0F.SAP AG Upgrading to 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.6x DB2/390 DB2/390: APAR list Conversion of partitioned tables SQL error -540 Maintaining catalog statistics DB2/390: Upgrade. 4. 3.6x Oracle Changing the storage parameters NEXT and MAX EXTENTS Oracle . 4. ICLI servers DB2/390: Manual saposcol installation DB2/390: DDIC corrections (3.5A. 3.Problems with Rollback segments Installation of the Oracle Client Software Oracle-specific Oracle-specific Oracle-specific Oracle-specific April 2001 43 .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.0B) DB2/390: DDIC corrections (4.5B) DB2/390: DDIC corrections (4.

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

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

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

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

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

End of the operating system-specific explanations April 2001 49 .tar.Z. Check this using the following UNIX command: lslpp -l | grep perfagent If you have any questions. which you received with your computer. or which you can order from your technical consultant. ReliantUNIX You must install the runtime system ReliantUNIX C++ Runtime System Version 2.SAP AG Upgrading to 4. contact your IBM or Bull Competence Center. you can install this software from the CD-ROM CD-DEV-MI. The compressed file is called CDS_PL_PLRTS_NYMS_1_0C32. Check this using the following UNIX command: pkginfo -l CDS++RTS If necessary.0 A00 or higher.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.

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

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

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

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

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

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

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

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

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

April 2001 59 . The Upgrade Assistant server also runs on this host. For a description of these actions. • Other hosts The graphical user interfaces (GUIs) provided by the Upgrade Assistant can run on any hosts that meet the necessary requirements.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. 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.SAP AG Upgrading to 4. you may later also need or want to use your database host or another host.

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

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

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

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

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.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.6C Support Release 2: UNIX SAP AG Checking SAP Programs (Source Release 4.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. • Finding out the version of tp in Release 4. • Finding out the version of the SAP Kernel Call the program disp+work with the following command: disp+work -V 64 April 2001 . 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. The program displays the date and the version number.Upgrading to 4. 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. Required Versions of the SAP Programs for 4.5B Call tp with the following command: tp -V The last line displays the highest patch level.

You can always find the correct versions of these SAP Kernel programs on the SAP Support Servers sapserv<X>. Directory /<CD mount directory>/UNIX/<OS>/45B April 2001 65 .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.6C Kernel CD.6C Kernel CD.SAP AG Upgrading to 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. You can also use the following options to obtain these versions more quickly: Locations of the Correct Versions of SAP Kernel Programs for 4.

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

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

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

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

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

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

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

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

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

SAP AG Upgrading to 4. The name of the phase is given in parentheses to help you. 3. in particular RUNSTATS during the table import. For a list of the necessary entries for this PREPARE module. 4. Data set for LOAD library Enter the name of the data set that contains the LOAD library. see below. 6. Stop before execution of the JCL job Several JCL jobs are executed during PREPARE and the upgrade. Here you have to decide whether you want the upgrade to stop before the JCL job is executed. User who starts the ICLI server Enter the name of the user who starts the 4. DB2 subsystem name Enter the name of the DB2 subsystem. Confirm or change the default entry. so that you can make corrections to the job. 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. 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. Default entries appear where possible. These jobs can also run at night. 2. 5. The default name is ICLIRUN.6C ICLI server. 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 . Data set for DSNTIAD library Enter the name of the data set that contains the DSNTIAD library.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.

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

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 . for example. see Drawing Up an Upgrade Schedule [Page 32]. you now have the chance to update the database statistics for tables and indexes. For more information on using multiple CD drives. We recommend the 3 processes for machines with 512 MB main memory. DB2 Universal Database • Update database statistics To avoid lock situations and any resulting problems during the upgrade. see the file README on the CD. • Language key Enter E or D to define whether the help texts displayed by R3up in error situations appear in English or German. Up to 4 parallel import processes are possible for multiprocessor hosts with sufficient main memory.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.SAP AG Upgrading to 4. but by other programs within the upgrade. to import a new version of the database system. • Number of parallel import processes The number of parallel processes used by R3trans to import data into the database. However. You can change your entries each time you run PREPARE or R3up. You can skip this step. 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. enter all the mount directories used. Add-Ons The other CDs in the upgrade package are not required by PREPARE or R3up.

the background service may be elsewhere to improve load distribution.Upgrading to 4. 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). see the script startsap for the correct name of the start profile. 78 April 2001 . change it. 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. Password of user DDIC in the system. If in doubt. In this case. see the start profile for the correct name. Check whether the password is correct by logging onto the system.PFL can be found in directory /usr/sap/<SAPSID>/SYS/profile. R3up asks you to verify the password by entering it a second time. client 000 This password is needed for the RFC connection to the system. in larger systems. choose MEDIUM. If in doubt. • Path of the DEFAULT. enter the host name and the name of the relevant application server. Long runtime. • 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. and that the background server can process background jobs of class C. If it is not correct. you have another opportunity to update the statistics. If you do not know the state of the database statistics.6C Support Release 2: UNIX SAP AG At the beginning of R3up (actual upgrade). Also make sure that the upgrade directory is mounted on the host with the background service.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. However. You can check this with transaction SM51. • Host name of the background server Normally a background service is available on the central instance.

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

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

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

see Importing Additional Languages [Page 52]. 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.Upgrading to 4. • 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.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. Phase IS_READ All add-ons appear that are found in the IS_CHK phase. Phase PATCH_CHK3 The system tests to see if all the Support Packages (previously known as Hot Packages. Phase LANG_CHK If you have a source release lower than 3. If you exclude a language. it is possible to install additional languages during the upgrade. you can exclude certain languages from the upgrade. A password is required for this alternative. Phase IS_CHK You are asked if any add-ons are installed that are not automatically recognized. The data is copied to the upgrade directory. 82 April 2001 . you are prompted to make the relevant changes. you are asked to insert the corresponding CD. In principle. confirm the prompt with nothing else. The standard languages are always imported. The following alternatives are offered for each add-on: • Upgrade the component with the CD for the add-ons When you choose this alternative. Legal Change Patches) are confirmed.0E and R3up is unable to determine a standard setting for the territory of your system. you cannot work in this language after the upgrade. • Delete the add-on You can only choose this alternative if your add-on supplier has confirmed that this does not cause any problems. If you have installed languages other than the standard languages. For more information. If you have not installed any add-ons.

6C Support Release 2: UNIX Unconfirmed Support Packages are displayed on the screen and in the PATCHOUT.6C Support Release 1. You can include the Support Packages for multiple software components in this phase. you must include the HR Support Packages. 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. If you use an add-on component. we recommend that you always include all available Support Packages for the target release. April 2001 83 . TABIM_46C and XPRAS_46C increases. As of Release 4. We recommend that you include all existing R/3 HR Support Packages in phase BIND_PATCH (see the next section) of the upgrade.6. Confirm these Support Packages with transaction SPAM. To include Basis Support Packages.SAP AG Upgrading to 4. However. the overall runtime of the upgrade is reduced. SAP Note 73510 specifies which R/3 HR Support Package in the target release is equivalent to your current state. One disadvantage of including Support Packages in the upgrade is that the runtime of the upgrade phases SHADOW_IMPORT_REP. a warning appears that informs you which Support Packages these are. For information on this and on other subjects. ACT_46C. If the source release contains Support Packages that are more recent than those in the delivered target release. Reimporting the R/3 HR Support Packages in the target release does not solve this problem. 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. This means that your system is completely up-to-date after the upgrade. and all released Basis Support Packages. All software components appear whose Support Package level is more up-to-date than the status of the software components on the upgrade CD. the R/3 HR Support Packages already imported into your SAP System are canceled and data is lost. you need a Package Key as of 4.LOG file in the log subdirectory of the upgrade directory. then you need to do this in the next phase BIND_PATCH. If you use SAP HR. If you upgrade your system without doing this. see SAP Note 119738. 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.

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

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

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

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

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

You can now create tablespaces with sapdba.6C Support Release 2: UNIX available in these dbspaces as in the original dbspaces of the tables. Reboot your AIX System to activate the new values. Oracle Extend the listed tablespaces by at least the specified values. April 2001 89 . 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. error messages are issued if tablespaces greater than 1 GB are created. End of AIX sapdba suggests other values for the extension than those specified in the list. Otherwise <sapsid>adm is unable to start up the database after large tablespaces have been created. 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>. - 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. Be generous when you extend existing tablespaces. For performance reasons. however. A typical example is moving the ATAB from the dbspace psappool. Where necessary. Create the new tablespaces as required by PREPARE. You can find further information in the SAP online documentation on the program sapdba. you must meet the minimum requirements of the list.SAP AG Upgrading to 4. increase the value of fsize. 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. Note that the parameter fsize is increased by the same amount for the user <sapsid>adm. Choose a low degree of fragmentation when you create tablespaces. use the program <upgrade_directory>/exe/sapdba as user ora<sapsid>. and must not be in the same sapdata directory PSAPES<Rel>D and PSAPEL<Rel>D must not be on the same disk. Avoid fragmenting the database too strongly.

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

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

. 3. To determine the terminated or outstanding updates. Terminated or outstanding updates have to be followed up or deleted in all clients. The views will be created in this upgrade. user and time. Consult a Basis consultant. The changed parameter only becomes active after you have stopped and started the database.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. proceed as follows: 1. To do this. Start Transaction SM13. If you need the table data later. Delivered views may have names identical to the names of customer tables in the SAP namespace. Choose all the update requests. 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. 2.<TABNAME> drop primary key" 3. 92 April 2001 . SAP DB • Insufficient DB parameter MAXLOCKS. proceed as follows: 1. These must be cleaned up before you start the upgrade.Upgrading to 4. since otherwise table or index modifications could terminate. you only have to delete the terminated updates. Therefore . Log on to the system as user DDIC and start Transaction SE14. Delete the default values for the client. Reconstruct the primary index (index ID 0) on the database. If you are still in the preparation phase (PREPARE) and therefore in production operation. 2. You must delete these tables. • The following database tables have names that are identical to names of Basis views.please process Make sure that you have cleaned up all outstanding updates by the phase JOB_RSVBCHCK3 (during downtime) at the latest. you must first make a backup. Enter the following command: db2 "alter table sapr3. Repeat this check when the system stops operating productively (see Isolating the Central Instance [Page 202]). • Update records still exist .. Use the SAP DB tool xcontrol to give MAXLOCKS the correct value.

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

If you have modified the standard scripts. 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. you must back up the scripts before you upgrade. Depending on the operating system setting displayed with the command uname.Upgrading to 4. Make sure that you can recover the old Kernel if this becomes necessary. 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. Make a backup copy of these programs to guarantee this. so that you can repeat the modifications after the upgrade. the SAP Kernel programs are replaced under /usr/sap/<SAPSID>/SYS/exe/run. /install/os_version/Relia=SINIX 2.6C Support Release 2: UNIX SAP AG Making Preparations at the Operating System Level Backing Up the SAP Kernel During the upgrade. End of ReliantUNIX 94 April 2001 . Making Operating System-Specific Preparations ReliantUNIX You must change the instance profiles of all the SAP instances. /install/os_version/ReliantUNIX=SINIX 3. 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.

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

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

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. End of the database-specific explanations April 2001 97 .SAP AG Upgrading to 4. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version. unpack this archive again into the subdirectory exe of the upgrade directory. After you execute PREPARE.

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. 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.0x/3.1x) [Page 105] 98 April 2001 .0x/3.1x) [Page 102] Converting the Translation Proposal Pool (Source Releases 3.0x/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.

This means that you cannot create new users. To perform the modification adjustment. you must log on in the correct client as the user who performs the modification adjustment using transaction SPDD. April 2001 99 . User DDIC needs to have the authorization SAP_ALL to be able to perform all the actions required during the upgrade. or call transaction SU01. we recommend temporarily assigning the SAP_ALL profile to the user who performs the modification adjustment with transaction SPDD. because the system is undefined. Remove this assignment after the upgrade. You cannot use transaction SU01 at this point. 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. The initial password for DDIC is 19920706 in a newly installed system. If your system contains the SAP_NEW profile. go to user maintenance. You must perform the modification adjustment during the upgrade in the ACT_<rel> phase. DDIC cannot perform the modification adjustment. Procedure To make sure that the authorization has been assigned. Choose Tools → Administration → Maintain users → Users.SAP AG Upgrading to 4. This must be a user other than DDIC.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.

In addition.Upgrading to 4. If you do not make sure that you have met the requirements for 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. we cannot guarantee complete support during adjustment. make sure that changes to the Repository are allowed in the client in which you want to perform the modification adjustment.Changing the SAP Standard → The Modification Assistant. To check this. see the documentation CD for the target release under SAP Library → BC . you might also risk losing the data for ABAP Dictionary objects. make sure that you meet the requirements for the modification adjustment. 100 April 2001 . use Transaction SCC4. For more information on the requirements for the modification adjustment.Basis Components → ABAP Workbench → BC . In particular.

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

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

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

use Transaction SE16. In the field TCODE. Procedure 1. 2. This affects data in the table TSTCP. stored for posting transactions with transaction codes between F-01 and F-99 (such as F-52 Post Incoming Payments). To do this. Prerequisites You use the SAP application component FI (Financial Accounting). are lost during the upgrade.Upgrading to 4. Reenter the data manually after the upgrade. use report RFTSTCP0. Back up the data before the upgrade by printing out the contents of the table. 104 April 2001 . Enter TSTCP as the table name and then choose Enter. enter F-01 to F-99.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. To do this.

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

right up until the system starts operating productively again.Upgrading to 4. you can enter multiple CD mount points in the phase INITPUT. The program PREPARE has run successfully. You have made all manual preparations. 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. If your central instance and database are running on different hosts. as well as any particularly critical areas. The program R3up controls the complete upgrade from checking that the requirements for the upgrade are met. 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.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. You can use the alert function [Page 199] to gather information if the upgrade has stopped. R3up logs all actions in the log files [Page 171]. During the upgrade. the abbreviation <rel> is used as a synonym for 46C. for example). If you have multiple CD drives. If an error occurs. This documentation assumes that you only have one CD drive. and helps you recognize any processes that have exceeded their runtime. you are prompted to insert a CD when necessary. You can use the Upgrade Monitor. Some phases of the upgrade require you to make few user entries. 106 April 2001 . you can continue the upgrade. you must perform the actions that affect the database on the database host. We recommend that you perform the upgrade with the Upgrade Assistant. For a complete list of all phases. or none at all. Process Flow You use the program R3up to upgrade the system. User actions are generally required if problems arise (subdirectories are missing. see R3up Phase List [Page 225]. as well as all structural requirements. R3up is located on the application server of the central instance. The Upgrade Monitor [Page 242] lets you monitor the upgrade. remove the cause of the error and repeat the phase [Page 109] in which it occurred. you can ignore the information on changing CDs. which you can use as the basis of any troubleshooting. the log files and an alert function to monitor the upgrade. Once you have repeated the phase successfully. Prerequisites • • • You must meet the hardware and software requirements.

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

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

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

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

names. • • If you confirm this. confirm with ENTER. for example. paths and passwords. correct it as described under Correcting Entries from the INITPUT and INITSUBST Phases [Page 185]. If you skip this phase and realize in the following phases that you made an incorrect entry. Activities At the start of this phase R3up asks you whether you want to change any parameters.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. If the default values are correct. you are prompted for all the parameters. You can modify the entries you made in PREPARE in the INITPUT phase. April 2001 111 .

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

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

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

Activities 1. − − and you have already included Support Packages in the BIND_PATCH phase of PREPARE. 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. see the description of the phase PATCH_CHK3 under Making Entries for the Read CD Module. and you have not included any Support Packages in the BIND_PATCH phase of PREPARE. call transaction SPAM and confirm the Support Packages that are proposed there. 2. For more information about this.SAP AG Upgrading to 4. If a warning appears that the Support Package version of your source release is too high. you can ignore the warning.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. repeat PREPARE. April 2001 115 .LOG file in the log subdirectory of the upgrade directory. If you still have to confirm Support Packages for the source release. In this case. and include the necessary Support Packages. you must reset the upgrade. you will lose data if you continue with the upgrade.

The inactive nametab is then empty.LOG. Activities If you have not already done so. see Notes for the Upgrade [Page 40]. 3. you will also be prompted for other keywords. For a list of the Notes you require for the upgrade. display the log file DDXTTCHK. Activate these objects with Transaction SE11. request the most recent Notes now. To determine the objects that are affected. 2. 116 April 2001 . 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. Phase KEY_CHK Use This phase prompts you for the keyword specified in the current Upgrade Note. If you use SAP add-on components in your system (such as IS components).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. The Notes are continually being updated. Call R3up again using repeat.Upgrading to 4. Activities 1.

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

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

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

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

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

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

SAP AG Upgrading to 4. the SAP Kernel is switched in the Kernel directory /usr/sap/<SAPSID>/SYS/exe/run. make sure that you are able to restore the old Kernel. For more information. All files and subdirectories in /usr/sap/<SAPSID>/SYS/exe/run are overwritten during the upgrade when the kernel is switched. During downtime.LOG. April 2001 123 . if this becomes necessary. You must have enough free space in the log directory so that the upgrade can run without errors. Activities At this point. This phase also compares the free disk space in the Kernel directory with the space requirements of the new SAP Kernel. 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.

This lock is needed to prevent development objects (for example. Activities If you have chosen strategy A_switch or A_on. 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). ABAP reports. This increases the time in which R3up does not need user input after the last change of CD (EU_IMPORT5 phase). and so on) from being changed during the upgrade. If you want to do this. 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. If you confirm the lock now: • R3up does not stop in phase REPACHK2 to allow you to confirm the lock on the Workbench.Upgrading to 4. • • You may not perform any more transports into or out of the SAP System. you must confirm that the ABAP Workbench can be locked. you can continue to use your SAP System productively. 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. since such modifications would be lost. table definitions.

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

If you miss this prompt.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. For strategies A_on and A_switch. The majority of the substitution set is imported directly from CD-ROM into the database during this phase. EU_IMPORT3 and EU_IMPORT4. 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 made up of the total time you specified for the import. SAP DB and DB2 Universal Database The statistics for newly imported tables are updated automatically. your time schedule could be seriously disrupted. For strategies A_on and A_switch. you are prompted to change the CD. less the time taken up by EU_IMPORT2. the expected runtime is computed from the total time you specified for the import less the time computed in EU_IMPORT2. 126 April 2001 .Upgrading to 4. Phase EU_IMPORT5 Use At the beginning of the this phase.

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

128 April 2001 .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. proceed as described under Cleaning Up Terminated Conversions in the DB Conversion Phases [Page 179].Upgrading to 4.

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

For more information. you can adjust and retain the modifications later in transaction SPDD. 2.Upgrading to 4. You can only skip the error message by choosing ignore. 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. Prerequisites The RUN_RDDIT006 phase ends with an error message stating that the central Basis tables have been modified. If necessary. Use transaction SE11 to check which table types are affected. If the tables are database tables. the SAP System might be unable to run with the target release. data might be lost if the table structures were modified. These modifications cannot be retained during the upgrade. Procedure 1. at least temporarily. skip the error message with ignore. If the modifications are retained. contact SAP Local Support. This resets the modifications to the standard SAP version. You cannot adjust modifications at this stage of the upgrade. and continue with the upgrade. If you have any questions. modified objects that are not delivered. Back up any contents of the table. no data is lost. see SAP Note 33888.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. 130 April 2001 . − − If the tables are structures. and your own developments.

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

depending on your database and the upgrade strategy you have chosen. If you chose the upgrade strategy A_switch. so that you can reset the upgrade to this state at a later point. the rest of the data is converted in the conventional manner during downtime. Result Once you have completed and confirmed all the activities. End of DB2 for OS/390 So that you can recover your SAP System after errors. All upgrade strategies: Back up the upgrade directory now. All changes to the profile are written to the ALPXPOOL. Isolate the central instance as described under Isolating the Central Instance. 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. you are not prompted to do this. For details on the status of the incremental conversion. 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.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. • If you called transaction ICNV when you prepared the upgrade. R3up prompts you to perform several activities. If you do not do this. 132 April 2001 . perform the following actions: Strategy A_switch: Make sure that you can recover the database to its current state. R3up informs you if you have not.LOG file.Upgrading to 4. If you ignore the information from R3up. All secondary application servers are shut down. • DB2 for OS/390 If you use DB2 for OS/390. start by reimporting the current version of the profile into your system. also make sure that you have switched off the capability of the database to continually restore data. the changes made by the upgrade are reset. which can cause the upgrade to stop running. R3up checks whether you have already converted the recommended percentage of the selected data (see Incremental Table Conversion [Page 30]). call transaction ICNV. If you want to use transaction RZ10 to adjust the instance profile during the upgrade.

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

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

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

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. 136 April 2001 .Upgrading to 4. You must usually remove the cause of these problems before you start using SAP applications again. R3up displays a complete list of these P-messages in this phase. Any messages that you do not handle immediately need to be handled at the next possible opportunity. This type of problem is indicated by a P in the second column of the . proceed as described in the long text of the message.ELG logs. Some of the secondary indexes may not have been created because they were not unique. Activities To remove errors. Use the ABAP Dictionary tools (Transaction SE14) to create these indexes in the database.

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

0x/3. Then perform the following actions: • • • • • • • • • Executing the Script saproot. 138 April 2001 .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. At the same time you can perform the post-upgrade activities specified by R3up.Upgrading to 4.1x Only) [Page 150] Checking the Profile Parameters with Transaction RZ10 [Page 151] You can start operating the system again productively after these actions. R3up then executes the last phases and completes the upgrade.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.

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

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

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

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

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

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

Basis Components →=Client Server Technology → System Services → Setting Up Local Executables on UNIX R/3 Instances. AIX_64. HP10_32. Procedure 1. April 2001 149 . DEC_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. To keep the network load low. Shut down the application server. you have to distribute the programs in directory /usr/sap/<SAPSID>/SYS/exe/run to all servers. HP11_64.SAP AG Upgrading to 4. RLX_64. we recommend that you use NFS to share programs in /usr/sap/<SAPSID>/SYS/exe/run. 2. RLX_32. 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. Mount the CD. you can also save the programs locally on the servers and update them automatically with the program sapcpe. SUNOS_32 or LINUX_32. This avoids inconsistent programs and having to distribute them manually. You can copy the programs directly from the CD SAP Kernel to the target directory of the application server with R3up. For more information on using sapcpe see Help → SAP Library → BC . If you use distributed servers. HP11_32.

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

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

0x/3.Upgrading to 4.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.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.1x) [Page 155] Adjusting Repository Objects [Page 156] Reimporting Additional Programs [Page 156] Migrating Matchcodes to Search Help Objects (Source Releases 3.0x/3.

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

since the report variants will no longer be correct. Log on as user DDIC in client 000.Upgrading to 4.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.0B only: 1. 2. If this is the case. 154 April 2001 . Call Transaction SM37. To release the jobs. Execute the report BTCTRNS2. 4. Procedure For Source Releases up to and including 4.5: 1. As of Source Release 4. Errors may occur if a background report was changed by the upgrade. Result The jobs are released. 2. Find all the relevant jobs. Log on as user DDIC in client 000. 3. choose Job → Schedule → Release. you have to reschedule the job.

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

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

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

There are no input parameters. so execute it in the background. and not yet imported into the actual database tables of the system.Upgrading to 4. You are using a glossary or terminology in your system. Prerequisites You have imported a language during the upgrade.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. The report unpacks the contents of the container tables and copies the data to the corresponding database tables. The contents of the container tables are then deleted. depending on the number of languages you have imported. use the following procedure to copy the data from the container tables to the database tables. some data from the language CDs was only imported into container tables. This data includes glossary and terminology data. If you want to use a glossary or terminology in your system. 158 April 2001 . Procedure Use the report RSTLAN_AFTER_UPGRADE to copy the data.

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

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

sapdba executes the Drop command on the database and deletes the data files at the operating system level. 2. System performance is reduced considerably during this time. Choose Drop tablespace.1x) You must switch the database optimizer to cost-based mode after the upgrade.x. 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.SAP AG Upgrading to 4.0x/3.6C Support Release 2: UNIX Delete the tablespaces as follows: 1. Check the success of the action with one of the following options: April 2001 161 . Proceed as follows: 1. SAP no longer supports the parameter setting optimizer_mode = rule after the upgrade to 4. The cost-based optimizer requires table statistics to be created. The runtime depends strongly on the size of your database and can take several hours. Choose Tablespace administration. You can make this switch during production operation. 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. If the tablespace is empty. see the following documentation on the documentation CD for the target release under: • SAP Library → BC . 4.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. When you run the database in rule-based mode you significantly reduce the performance of the system. Enter the name of the tablespaces you want to delete. Start sapdba at the operating system level as user ora<sapsid>. For background information on this subject. 3.

End of Oracle 162 April 2001 .6C Support Release 2: UNIX SAP AG − − In the SAP System. 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. send a problem message and the log file to SAP. your database is already running in cost-based optimizer mode. After the upgrade you only need to update the statistics.ora: optimizer_mode = choose db_file_multiblock_read_count = 8 3. Updating the Statistics (For Source Release 4. $ORACLE_HOME/sapcheck/*. System performance is reduced considerably during this time. The Optimizer must be set to cost-based mode. Restart the database to activate the parameters. Make sure that the following parameters are set in the file $ORACLE_HOME/dbs/init<SAPSID>.x) If you had Release 4. see the online documentation under Help → Application help. 2.opt If there are errors. If you cannot solve the problem yourself.Upgrading to 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.x before the upgrade. Friday/Saturday night): sapdba -checkopt PSAP% (for example. For more information on DB13. you can analyze the cause by double-clicking the log line and pushbutton SAPDBA Detail Log in the menu above. Correctly created optimizer statistics are essential for the performance of your system. Saturday/Sunday night): sapdba -analyze DBSTATCO You can schedule these actions with transaction DB13. Scheduling Periodic Statistics Updates (For All Source Releases) Make sure that the statistics are updated at regular intervals.aly or *. 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.

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

1G: To copy the latest SAP default values while retaining your own modifications. 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. For source releases before 3. use Transaction SU25 (step 1). Installation of a Web browser/viewer For instructions.Upgrading to 4. Only for help type PlainHtmlHttp: Set up the Web server 3. Installation of the online documentation 2.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. see the guide Installing the SAP Library. see the online documentation for Transaction SU25. You can change these values with Transaction SU24.1G.1G: To copy the SAP default values. Maintain the settings variants for the Online Help in the IMG 4. For source releases as of 3. Performing Post-Upgrade Activities in the Authorizations Area Procedure Adjusting the Assignments Between Check Flags and Transactions Transaction SU24 was introduced in Release 3. use Transaction SU25 (steps 2 and 3). 164 April 2001 . 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.

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

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

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

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.Upgrading to 4.4. Procedure Proceed as described in Note 137478 Installing a Dialog Instance/Gateway . 168 April 2001 .

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

Request the Notes [Page 40] that are relevant to this upgrade.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 .R/3 Frontend Notes. 170 April 2001 .Upgrading to 4.

If you encounter any errors you can analyze them to help you find a solution. The start and end of a phase are indicated by the lines START put and STOP put. where you can also monitor them with tail -f. A simple method of monitoring the progress of all tp-driven phases is to observe the SLOG log using tail. 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. Additional detailed logs are usually written for these tp steps. After the various steps of the April 2001 171 . 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.SAP AG Upgrading to 4. You can use these log files to monitor your upgrade.log in the subdirectory log of the upgrade directory. To do this. The tp steps are also listed in the file SLOG46C in the subdirectory log of the upgrade directory.6C Support Release 2: UNIX Upgrade Logs Use R3up logs all actions in log files. Functions R3up records all actions in the log file R3up. These are in the tmp subdirectory of the upgrade directory.

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

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

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

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

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

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

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

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

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

SAP AG Upgrading to 4. April 2001 181 . Since you do not know how long this will take. a. Schedule the request. Go to the detailed display of the object by double-clicking it in the list of requests created by the import. choose the processing type Background. b. or continue it.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.

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

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

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

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

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

you might also have to reset the SAP Kernel and the SAP profiles. Also perform one or more of the following actions. including the operating system. Reset the database to the state it had before the SAP upgrade. see the vendor’s specifications. Some of the actions are listed in italics. If you have any questions. 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. In addition to resetting the database. see the log file R3up. see SAP Note 158358. depending on what stage the upgrade has reached. contact SAP Local Support. 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.log. see the end of this section under Detailed Description of the Individual Actions. 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 perform various actions. For additional information on resetting an upgrade. For downgrading options. Delete the upgrade directory.SAP AG Upgrading to 4. Procedure After Database Failure Depending on the upgrade strategy you have chosen and the stage of the upgrade reached. The safest method is to reload a complete backup of the whole system. To perform these actions. For information on the progress of the upgrade. April 2001 187 . for example). Upgrade Strategy A_off 1. Restart the upgrade with PREPARE. These actions are listed in the tables below: The actions are explained in more detail later. 4. 2.6C Support Release 2: UNIX Resetting the Upgrade Use You need to take different measures to reset the upgrade (because of hardware problems.

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

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

dbenv_<host name>. Reset the SAP Kernel The new Kernel is active after the KX_SWITCH phase. You must reimport the old Kernel when you make the recovery. You can exclude the data directory if you have space problems.csh . Then delete the contents of the upgrade directory. Reset the upgrade directory You must recover the whole upgrade directory with all its subdirectories. The old files are in <upgrade directory>/exe/INSTALL. 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]). You must unpack the packages SAPEXE.SAR from the CD. These profiles have the latest state after the ENVCHK phase. Delete the upgrade directory We recommend that you archive all the subdirectories before you delete the contents of the upgrade directory.sh All the files are in the home directory of user <sapsid>adm.Upgrading to 4.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. 190 April 2001 .6C Support Release 2: UNIX SAP AG .SAR and SAPEXEDB.profile startsap_<host name>_<instance number> stopsap_<host name>_<instance number> .

If it is.SAP AG Upgrading to 4. 3. R3up logs any processes it has started. Restart the upgrade as described under Restarting the Upgrade [Page 109]. If so. Check whether R3up is running in the background on the host. If so. note the process number. If the transport control program was active when R3up terminated. 2. When you restart R3up. You must prevent R3up from starting two processes of the same type. both in the SAP System. April 2001 191 . R3up must wait until these processes have ended. Check whether a tp process still exists. a check is made to see if any of the processes you noted are still running.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. and at the operating system level. it keeps running independently of the upgrade. R3up does not need to wait if the processes found are of a different type. use the command kill to stop R3up. Procedure 1.

Enter an asterisk (*) in the field or after event.x: Choose Help → SAP Library → Basis Components → Change and Transport System → BC Transport Tools → Transport Control Program tp. proceed as follows: 1. To trigger an ABAP step. tp writes control information into this table.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. In Release 4. Check that the SAP System was started correctly.x: Choose Help → R/3 Library → BC Basis → System Administration → Transport Control → Transport Control Program tp. so that event-driven jobs are also displayed. To access this documentation: In Release 3. table TRBAT may contain only one HEADER entry. 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. 4. The table must have one HEADER entry and should contain one entry for each transport request. During distribution of the Dictionary objects (S) and table conversion (N). 2. 192 April 2001 . see the documentation Transport Control Program tp. Log on as user DDIC in client 000.Upgrading to 4. Enter Transaction SM37 and check if background job RDDIMPDP has been scheduled. Result For more information on the transport control program and on communication between tp and the SAP System. Procedure If you encounter problems when editing the ABAP steps. 3. 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. Check when RDDIMPDP last ran and if it ran without errors. Use Transactions SM37 and SM50 to check if RDDIMPDP has already started the actual background job for editing the ABAP step. as these steps are not carried out by transport request.

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

Repeat the phase or copy the program manually from subdirectory exe of the upgrade directory to directory /usr/sap/<SAPSID>/SYS/exe/run. 2. it cannot overwrite the old files.<SAPSID>. Analyze the log of the copy process. 194 April 2001 . otherwise. 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. Procedure 1. the SAP programs in the directory /usr/sap/<SAPSID>/SYS/exe/run are replaced. Do not start the SAP System during this period.Upgrading to 4.

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

ELG or the last file written with the . In which R3up phase does the error occur? This information is listed at the end of the of the R3up.R/3 Frontend. 196 April 2001 .R/3 Frontend customer message: 1. 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. Procedure If you encounter problems that are specific to the upgrade. 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. assign your error message to the appropriate product-specific component. see SAP Note 40024. contact your SAP Local Support.Upgrading to 4. Which operating system version are you using? 4. For which SAP component do you want to perform the upgrade? 2. • For transport phases we also require SLOG46D. follow the procedure given here. if one exists (use transaction ST22 to find this out). Which release are you upgrading from? Which release are you upgrading to? 3. What was the original release of your SAP System? 5. 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.ELG suffix and the detailed log file that contains the error message For the phases JOB_<name> or RUN_<name>. 6. To enable us to help you as quickly and effectively as possible. Answer the following questions and put these answers in your SAPNet .log file located in the upgrade directory. create an error message in the SAPNet – R/3 Frontend and assign it to the component BC-UPG.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.

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 .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 .Internet Pricing and Configurator (IPC) .SAP AG Upgrading to 4.

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.Upgrading to 4. • • • • • • • • • Using the Alert Function [Page 199] Determining the Operating System Version. 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 .

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

Upgrading to 4.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. 200 April 2001 . enter the following command as user informix: onstat Oracle Execute the following SQL command: SELECT BANNER FROM V$VERSION. The first line of the output contains the Oracle server release. 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.

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

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

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

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

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

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

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

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

it is overwritten each time a module is executed again.LOG already exists. This file is in the subdirectory log of the upgrade directory. If the file CHECKS. you may need to import software. you can choose certain PREPARE modules more than once. such as SAP Support Packages. Results of PREPARE PREPARE writes the results for the modules that you selected for execution to the file CHECKS. languages.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. or add-ons (and add-on updates). For more information. After you start PREPARE. see Importing Software after Starting PREPARE. Activities • • Start PREPARE as soon as possible before the upgrade so that you can initiate or perform the necessary preparations in time. Its contents are saved in file CHECKS.SAV. April 2001 213 . see the online help for PREPARE. To be sure that all the requirements are met.LOG.SAP AG Upgrading to 4. Look at this file and carry out the necessary measures based on the information it contains. You can find it easily by choosing Help when selecting the modules.

LOG Unlock clients for SAP upgrade. if necessary VALCHK.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 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 EXECCT.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.LOG Upgrade to a valid source release. if necessary 214 April 2001 .Upgrading to 4.

6A or 4.5B.LOG KRN_CHK.LOG Use transaction SPAM to confirm any unconfirmed Support Packages INTCHK_INI SPACECHK_INI KRN_CHK_INI DBFPREP. 4.0B: reads data files from Upgrade CD2 Source Releases 4. 4.LST Extend free disk space.SAP AG Upgrading to 4.1H.6B: Mount Upgrade CD3 READDATA2 CPYFIL0_CBU EXEC_CPYFIL1_CBU INFO_STORE_READ CONFCHK_IMP If necessary.5B. 3.1I or 4.1H. 3.LOG EXECPT.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.0F and data files required for all source releases from Upgrade CD1 Source Releases 3. upgrade OS or DB April 2001 215 . 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.6A or 4. if necessary Import current downwardcompatible Kernel.0D or 3.1I or 4.0B: Mount Upgrade CD2 For Source Releases 4.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 ICNVCHK.LOG SCRIPTCHK.LOG ICNVCOUNT.0x and 3.LOG CLCNVTST.LOG ALTER_TO TOOLIMPD1 ALTER_TO.LOG CLCNVTAB.LOG CNVTST.LOG CLCNVTST.LOG Determines outstanding conversions and restart logs of terminated conversions Checks whether incremental conversion from previous upgrade has finished Source Release 3. if necessary Use transaction SPAM to confirm any unconfirmed Support Packages NTHISTCRE NTABHIST.LOG EXECCT.6C Support Release 2: UNIX SAP AG version CNV_CHK_IMP to required version Make conversions (after discussion with Basis consultant).LOG CNVTST.LOG SCRIPTCHK.Upgrading to 4.x: Avoids critical conversions in tool import Source Release 4.LOG ICNVLIST. if necessary CLNT_CHK_IMP INTCHK_IMP SPACECHK_IMP PATCH_CHK2 Extend free disk space.LOG ICNVCHK_IMP Complete incremental conversion with transaction ICNV. if necessary SCRIPT_CHK_TOOL3 SCRIPT_CHK_TOOL4 TRBATCHK_IMP Perform any actions specified by R3up Unlock clients for SAP upgrade.LOG CLNTOUT.1x: Prepares ABAP Dictionary for DBFPREP.ELG 216 April 2001 .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 TOOLIMPD.LOG EXECPT.LOG CLCNVTAB.LOG PATCHOUT.LOG ICNVEX.

ELG UVERS_INIT UVERS_CHK_IMP BATCHCHK_IMP UVERSINI.ELG RDPUTTB.ELG TOOLIMPD3 TOOLIMPD.LOG JOB_RDDGENRS RUN_RDDITCUG RUN_RSINCGEN_IMP RDDGENRS.0B. LOG JOB_RSCVINIT READPUTTB PSCVINIT.ELG PREPIMP.ELG PSINCGEN.ELG TOOLIMPM.SAP AG Upgrading to 4.LOG PDDITCUG.LOG PDDITCUG. 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.LOG MVNTTOOL. prepares ABAP Dictionary for upgrade tools For source release 4.LOG PSINCGEN.ELG TOOLIMPI.6C Support Release 2: UNIX upgrade tools TOOLIMPD2 For source release 4.ELG NPREPCRE1 DDYIMP. LOG BATCHCHK_IMP.LOG UVERSCHK_IMP.ELG PRE_IMPORT0 April 2001 217 .LOG PSCVINIT.ELG MVNTAB_TOOL TOOLIMPI TOOLIMPM NPREPCRE0 MVNTTOOL.5B.

LOG Add add-ons manually. BIND_PATCH Includes Support Packages for the target release Determines installed languages Checks whether the new release supports the installed languages Source release 3. check using Note 73510 if upgrade can be performed or which Support Packages are equivalent in the target release. if necessary 218 April 2001 . if necessary Source release 3. PATCHOUT. or confirm with nothing else Mount add-on CDs.Upgrading to 4.0D: determines language area PATCHINT.0D: enter language area.LOG PATCH_CHK3 Use transaction SPAM to confirm any unconfirmed Support Packages If necessary.LOG ISOUT. 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. if necessary EXECLANG LANG_CHK EXECLG.LOG Delay upgrade until next release.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. if necessary.LOG LANGOUT.LOG EXECPT.LOG Include Support Packages in the upgrade.

LOG INTEG_PATCH INTGPTCH.<SID> PCMDIMP.LOG PDDIT021. Confirm language selection. 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. if necessary.ELG PEVALLAN.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.ELG Mount language CDs.ELG TPSHBUF. select command file ISC_IMP IS_MERGE ISC_IMP.LOG ICNV_CND_IMP ICNVXRQ ICNVCNDI.LOG April 2001 219 .ELG If necessary.ELG ICNVXRQ.LOG TR_HYP2HEAP_ICNV TRICVNBUF. TR_CMDIMPORT_ PATCH TR_TODIR_MERGE_ PATCH GETSPAREQ_N DBFINTEQ.LOG LANGSEL.LOG PCMDIMP.LOG ADDSPAREQ_N ADDSPAREQ_T ADJUSTPRP ADJUSTPRP.SAP AG Upgrading to 4.ELG JOB_RDDIT021 TR_TRK2HEAP_ADDON PDDIT021.

update OS or DB to required version Extend free disk space.Upgrading to 4.LOG If necessary. 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. DBFPLUSD. 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.LOG DDICNV.ELG ICNVCAND. if necessary If necessary. check write authorizations for SAP Kernel.LOG ICNVINIT.ELG DDICNV. REPACHK. if necessary Perform any actions specified by R3up CNV_CHK_GEN TRBATCHK_GEN 220 April 2001 .LOG ICNVREQP. if necessary Increase disk space.6C Support Release 2: UNIX SAP AG prerequisites for ICNV and filters candidates for ICNV ICNVINIT ICNVXRQ. if necessary Make conversions (after discussion with Basis consultant).LOG ICNVINIT.ELG DDICNV.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.LOG Checks the volumes of the candidates.LOG Call transaction ICNV.

LOG EXECCT.ELG PSVBCHCK.LOG Perform any actions specified by R3up INTCHK_GEN SINXCHK Delete indexes.LOG PXPRECHK.LOG Unlock clients for SAP upgrade.LOG FRONTREQ_PRE UVERS_CHK_GEN BATCHCHK_GEN PROFCHK PROFCHK. if necessary JOB_RXPRECHK_PRE PXPRECHK.LOG Delete tables. if necessary UVERSCHK_GEN. if necessary VIEWCHK VIEWCHK.LOG PSVBCHCK.LOG Correct entries with R3up set stdpar.ELG JOB_RSVBCHCK1 Delete any terminated updates CHECKGROUP_END April 2001 221 .ELG NTCHK.SAP AG Upgrading to 4.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. LOG BATCHCHK_GEN. if necessary ENVCHK_PRE If necessary assign write authorization to the user profile Upgrade the frontend software. if necessary JOB_RS_NAMT_CL NTACT_CHK NTCHK.

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.6C Support Release 2: UNIX SAP AG PREPARE Module Activation Checks Phase JOB_RADDRCHK Actions Taken by PREPARE Log PADDRCHK.LOG RSTODIRX.ELG CHECKGROUP_END PREPARE Module Necessary Checks for Conversions Phase CNV_AVOID Actions Taken by PREPARE Log RSUPGTAA.LOG RSUPGTAA.ELG CHECKGROUP_END End of module PREPARE Module Optional Checks for Conversions Phase CNV_LIST Actions Taken by PREPARE Log TABCONV. start report for preparing the address data conversion as described in Note 82167 JOB_RSCNVADR PSCNVADR.Upgrading to 4.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 .LOG RSUPGTAL.LST RSUPGTAL.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 PADDRCHK.LOG PSCNVADR.

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

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

otherwise R3up requests that you make the entries described.x to 4.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. The percentage duration of these phases can be very different in your upgrade.6C. The following assumptions are made: − − Only one CD drive is used. Some phases are considerably shorter when you upgrade from 4. • User Actions If nothing is entered here. This is based on the upgrade from 3. R3up does not require an operator at this point. You have not specified a latest time at which you want to go live (query define upgrade stop in the INITSUBST phase). also read the section Logs under Troubleshooting. 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 . the runtime depends to a great extent on your own data. April 2001 225 . If you have a problem.x to 4.6C. If a phase is marked with comment .LOG Enter parameters DB2 Universal Database 1% Update database statistics DB2 for OS/390 Choose MEDIUM or HIGH Checks parameters. 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.SAP AG Upgrading to 4. not all the logs can be specified in this column.

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.LOG FRONTREQ --- Confirm 226 April 2001 .Upgrading to 4.LOG EXECCT. upgrade OS or DB to required version VIEWCHK1. if necessary Enter parameters 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 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 . if necessary CLNT_CHK <1% CLNTOUT.LOG BATCHCHK. if necessary REPACHK1 <1% REPACHK1.LOG EXECPT. if necessary UVERSCHK.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 INTCHK <1% KEY_CHK --- Enter keyword for the upgrade Enter password for industry solution. asks for keyword for industry solution PATCH_CHK <1% PATCHOUT.LOG Use transaction SPAM to confirm any unconfirmed Support Packages Unlock clients for SAP upgrade.

if necessary Confirm Enlarge the file system.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.LOG EU_IMP0.ELG PSWBO230.ELG For strategy A_off. if necessary BTCTRNS1.SAP AG Upgrading to 4. if necessary JOB_RDDPURI2 <1% PDDPURI2. isolate the central instance and stop all application servers Mount CD Upgrade CD3 April 2001 227 .LOG FREECHK_X <1% Checks freespace in file system JOB_BTCTRNS0 <1% As of Source Release 4.ELG ICNVREQ.LOG PDDPURI2.ELG ICNVCAND. stops system. Imports information on code page conversion from Upgrade CD3 into shadow area EU_IMP0.LOG PSWBO230.LOG ICNVREQ.LOG PXPRECHK.LOG BTCTRNS1. 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. but ICNV has not yet been started Deletes incorrect templates for Create Table statements Checks freespace in the database SAP DB PSVBCHCK2.LOG SPACECHK_ALL <1% Extend the database.ELG DBFPLUSD.ELG PXPRECHK.LOG PSVBCHCK2.ELG LOCKEUPR.LOG Delete any terminated updates RUN_RSWBO230 <1% JOB_RXPRECHK ICNVREQ <1% <1% Call transaction ICNV.

LOG REPACHK2 <1% REPACHK2.ELG EU_IMP2.ELG Mount CD Upgrade CD5 EUVIEWIMP STARTR3_IMP <1% <1% ALTER34V.BUF into the R3up buffer Puts upgrade requests of the buffer TABULONG.LOG TR_BUF2HEAP_ TABULONG <1% TPSHBUF.LOG TRB2H.LOG Confirm locks for ABAP Workbench if not yet done in LOCKEU_PRE Make conversions (after discussion with Basis consultant).ELG Mount CD Upgrade CD4 EU_IMPORT5 14% EU_IMP5. if necessary CNV_CHK_XT <1% TRBATCHK_XT TR_BUF2HEAP_ INSTIMP <1% <1% Perform any actions specified by R3up TPSHBUF.ELG Mount CD Upgrade CD3 EU_IMPORT4 9% EU_IMP4.LOG TR_APPENDBUF_ <1% TRAPPB.ELG Mount CD Upgrade CD3 Mount CD Upgrade CD3 DB2 for OS/390 Edit RUNSTATS jobs.6C Support Release 2: UNIX SAP AG EU_IMPORT1 EU_IMPORT2 <1% <1% Creates substitution tables for ABAP loads Creates ABAP tables EU_IMP1.Upgrading to 4.LOG EU_IMP2.LOG EU_IMP1.LOG EU_IMP3.BUF into the R3up buffer Copies upgrade EU_IMP3.LOG EU_IMP5.LOG TRB2H.LOG EU_IMP4.LOG 228 April 2001 . 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.

LOG SHDTTABS.LOG ADJUSTCK.LOG TR_CMDIMPORT_ UPG NEWTAB_CHK NEWTAB_CRE LIST_LOAD 2% <1% NEWTABCR.LOG SHDTTABS.LOG PSINCGEN.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.SID PREPCON.ELG DIFFCALC.ELG Confirm R3up message.LOG NEWTABCK.LOG JOB_RDDTAXIT SUBSTNT_INS <1% <1% SYSPREP.LOG SYSPREP.LOG SHDTABU.INF SHDTSEL.ELG STBNTINS.ELG NTSHDCP.LOG PDDNT4MD.SAP AG Upgrading to 4.LOG PDDNT4MD.LOG PN*.ELG ADJUSTMT.ELG NTSHDCP.LOG DIFFCALC.ELG RUN_RDDIT0061) 1% ADJUSTCHK1) <1% ADJUSTCK.LOG XTTSIZE0.LOG RUN_RSINCGEN <1% PSINCGEN.ELG SHDTABU.LOG LISTLOAD.ELG TRCMDUPG. if necessary SHADOW_CAND_SEL <1% SHADOW_PUTTB_ FILL SHADOW_NTACT_CP <1% <1% PREPPCON_INIT RUN_RDDNT4MD <1% <1% April 2001 229 .

LOG DIFFEXPR.ELG DIFFEXPO.LOG PDDSAVTE.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.LOG DIFFEXPO.LOG 230 April 2001 .LOG DIFFEXCO.LOG DIFFEXPG.ELG PSPUSCA4.ELG DIFFEXPC.ELG DIFFEXPT.ELG JOB_RDDSAVTE RUN_RDDCP4TB <1% <1% PDDSAVTE.ELG DIFFEXPMDOC1) DIFFEXPTSAP1) <1% <1% SHADOW_IMPORT_ ALL <5% SHDALLIMP.ELG JOB_RSPUSCAD1) <1% DIFFEXPADD <1% DIFFEXPGEN1) 2% DIFFEXPMOD1) <1% DIFFEXPCUST1) <1% DIFFEXPDDIV DIFFEXPDOCU1) <1% <1% DIFFEXPCDOC1) <1% DIFFEXCO.ELG DIFFEXPD.ELG SHADOW_IMPORT_ REP <5% SHDREPIMP.ELG PDDCP4TB.ELG DIFFEXPA.ELG DIFFEXPR.LOG DIFFEXPT.ELG DIFFEXMO.LOG PSPUSCA4.LOG DIFFEXPC.Upgrading to 4.ELG DIFFEXPA.LOG DIFFEXMO.LOG DIFFEXPG.LOG PDDNT4DL.LOG DIFFEXPD.

LOG ALPXDEF.ELG PDDPURIF. 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.LOG NTSHDDEL.ELG RUN_RSTRESNC <1% RSTRESNC.LOG NTACT_PREMV VIEWCHK2 <1% <1% Delete tables.LOG For strategies A_switch and A_on. if necessary MODPROF_TRANS <1% ALPXPOOL.ELG <1% TRBATCHK_SW INTCHK_SW <1% <1% April 2001 231 .LOG STARTR3_TRANS JOB_BTCTRNS1 <1% <1% JOB_RDDPURIF SUBSTNT_DEL <1% <1% SHADOW_NTACT_ DEL CNV_CHK_SW <1% NTSHDDEL.SAP AG Upgrading to 4.6C Support Release 2: UNIX that have not been delivered to the shadow tables RUN_RDDDL4TB PDDCP4TB.LOG NTMOVPRE.LOG 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 NTMOVPRE.LOG PDDDL4TB.LOG BTCTRNS1.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.ELG STBNTDEL.ELG VIEWCHK2.LOG RSTRESNC.

ELG STOPR3_DIST STARTR3_DIST RUN_PRELDIST <1% <1% <1% DISTBPRE.ELG BASDDIMP.ELG INXPREP.ELG PORT_IMP.LOG DISTBPRE.ELG DUMP_CNV.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.ELG DISTBAS.ELG JOB_RDDGENBB <1% DUMP_CNV 1% 232 April 2001 .ELG PADISWTC.ELG Clear all outstanding updates JOB_RDDINDPR JOB_RDDINDDL <1% <1% JOB_CLTAF1 PORT_IMP2) <1% <1% RDCLTAF1.LOG DISTBAS.LOG INXPREP.ELG UVERS_UP_B JOB_RSVBCHCK3 <1% <1% PSVBCHCK3.LOG RDCLTAF1.LOG PADISWTC.LOG NTDELFIN.LOG DUMP_CNV.Upgrading to 4.LOG PDDYT2NT.ELG NTDELFIN.ELG NTACT_MV NTACT_DEL BASDDIMPORT2) <1% 1% <1% NTMOVFIN.ELG INXDEL.LOG NTMOVFIN.LOG INXDEL.LOG PSVBCHCK3.

LOG EXECSMF.LOG ALPXDP.LOG EUSWITCH.ELG XTERN_CNV.LOG DEL_CNV.LOG XTERN_CNV.ELG UVERS_UP_S ALTER_VBDAT ALTER_D4V EXEC_SMOFF <1% <1% <1% <1% ALTERVB.LOG NTNOBD.ELG XTERN_CNV.LST ALTERTF.LOG LOADCRE.ELG ALPX.LOG April 2001 233 .LOG NTRWR40.SAP AG Upgrading to 4.LOG VIEWIMP.LOG VIEWPRP <1% VIEWPRP.ELG ALTER_TAF EU_SWITCH LOADCRE NTACT_RWR <1% <1% <1% <1% NTACT_NOBD <1% NTNOBD.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.LOG ALTERD4V.LOG VIEWIMP_BAS MODPROF_BAS2) ENVCHK <1% <1% <1% VIEWIMP.LOG LOADCRE.ELG CNV_SUBMIT2) STOPR3_BAS XTERN_CNV 1% <1% 2% CNV_SUB.LOG CNV_SUB.ELG NTRWR40.

ELG ADDMCM.LOG RDCLTAF2.LOG RPU510Q2.LOG RSWBOUP1.ELG LANGAREA.LOG TABUWBO.LOG STARTR3_NBAS JOB_CLTAF2 JOB_RSWBOUP1 <1% <1% <1% RDCLTAF2.ELG RSWBOUP1.ELG RSUMOD03. imports the result of transaction SPDD from a development system KX_SW.LOG RSUMOD03.ELG RPU510Q2.ELG DDIC_46C2) <1% 234 April 2001 .ELG DDIC46C.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.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.ELG PDDMCMRG.LOG RDDNEWPP.ELG RDDNEWPP.LOG ADDMCM.ELG JOB_DL4TA_46C <1% PDDDL4TA.LOG 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.LOG TABUIMP.ELG ALTER_DLG TABUIMP_WBO2) AREA_SET <1% <1% <1% ALTERDLG.LOG PDDDL4TA.

ELG PSDB2XTT.LOG PCON_46C1)2) 7% PCON46C.ELG PDDMVSUB.ELG PADDREXE.LOG PADDREXE.ELG PCON46C.SAP AG Upgrading to 4.LOG ACT46C.ELG PSUMOD20. 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 XTTSIZEI.ELG PDDMVSUB.LOG ALTERVID.LOG PSDB2XTT.LOG STOPR3_I46C TMPLDINV <1% <1% PMVNTAB_46C 3% PMVNT46C.LOG PREPCON. if necessary RUN_INDC_46C JOB_MVSUB_46C <1% <1% INDEXCHK.LOG April 2001 235 .ELG PMVNT46C.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.LOG INDEXCHK.LOG SQLLDINV.LOG RUN_DREXE_46C <1% JOB_RUTTYREP <1% JOB_UMOD20_46C ACT_46C1)2) <1% 2% Use SPDD to adjust ABAP Dictionary objects.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.

ELG REIMPCDOC_LOG REIMPCDOC1) <1% 236 April 2001 .ELG ADOIM46C.ELG TABIMERR.LOG LDSWITCH.ELG REIMPDDN.ELG PSDCDDXT.ELG REIMPDOC.ELG PADDBDIF. exports adjusted DDIC objects Re-imports inactive DDIC versions Reimports customer extensions to SAP object documentation Re-imports UEXP46C.Upgrading to 4.LOG PSWBOUP2.LOG VIEWIM46C.LOG PDDLDINV.LOG REIMPDOC.ELG UEXP_46C REIMPDDN_46C REIMPDOC1) <1% <1% <1% If necessary.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.LOG PADDBDIF.ELG TABIM46C.ELG ADOIM_46C1)2) 9% XPRAS_46C1)2) 11% Executes XPRAs Automatically repeats phase once if an error occurs XPRAS46C.LOG VIEWIM46C.ELG PDDLDINV.LOG REIMPDDN.LOG PSDCDDXT.

starts system Sets the status of the installed languages STARTR3_46C JOB_RSTLANUPG <1% <1% JOB_RSTLANUPG .ELG REIMPMDOC. ELG PSDBPROD.LOG RDDIT022. LOG PUTTYREP1.ELG PUTTYREP1.6C Support Release 2: UNIX documentation on customer objects REIMPMDOC1) REIMPCDOC.ELG <1% Reimports modifications to documents If necessary.LOG REIMPMDOC.LOG PDDNTPUR.LOG PSDLDSEQ.LOG JOB_RSTLANUPG .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 . LOG PSDLDSEQ.SAP AG Upgrading to 4.ELG EXECSMN.ELG PSDBPROD.LOG RDDIT022.ELG PDDNTPUR.LOG ALPXP.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.

6C Support Release 2: UNIX SAP AG database STARTR3_P46C REQJOBRES <1% <1% Starts system As of Source Release 4.LOG PDDDBSTA.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 .ELG EWTCH066.ELG PADDRDOC.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. exports objects adjusted with transaction SPAU --Copies upgrade logs to /usr/sap/ trans/upgrade SAVELOGS.Upgrading to 4.LOG PSUPGEND.LOG UEXPSPAU.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.LOG PADDRDOC.

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

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

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

Sign up to vote on this title
UsefulNot useful