Troubleshooting and Administration Windows

70
Troubleshooting and Administration For Upgrades Using SAPup For: n Windows Target Audience n System Administrators n Technology Consultants PUBLIC Document version: 1.0 ‒ 08/14/2008

Transcript of Troubleshooting and Administration Windows

Page 1: Troubleshooting and Administration Windows

Troubleshooting and AdministrationFor Upgrades Using SAPup

Forn Windows

Target Audience

n System Administratorsn Technology Consultants

PUBLICDocument version 10 ‒ 08142008

Document History

The following table provides an overview of the most important document changes

Version Date Description

10 8142008 First version ‒ no changes

270 PUBLIC 08142008

Table of Contents

Chapter 1 Accessing Documentation 5

Chapter 2 Troubleshooting 921 Error Handling for ABAP 1022 Upgrade Logs 1223 Evaluating the ELG Log Files 1524 Accelerating the Runtime of Certain Phases 1625 Correcting Errors in the HIAV_CHK Phase 1826 Correcting Errors in the DBCHK Phase 1927 Correcting Errors in the BATCHCHK Phase 2028 Correcting Errors in the INTCHK and INTCHK_SW Phases 2129 Correcting Errors in the START_SHDI_FIRST Phase 21210 Correcting Errors in the JOB Phases 21211 Cleaning Up Terminated Conversions in the DB Conversion Phases 22212 Correcting Errors in the TRBATCHK_XT Phase 25213 Correcting Errors in the ACT_ltRelgt Phase 25214 Correcting Conversion Errors in the PARCONV Phase 26215 Correcting Errors in the XPRAS Phase 27216 Correcting Problems when Starting the Upgrade Program 29217 Restarting the Upgrade GUI 29218 Preparing the Restart of the Upgrade After a System Failure 30219 Correcting Problems when Processing ABAP Steps 30220 Correcting Problems when Starting the SAP System 31221 Correcting Problems when Copying SAP Programs 32222 Use of Kernel and Instance Numbers During the Upgrade 33223 Providing SAP Support with Information 33

Chapter 3 Administration 3731 Reducing Downtime 3832 Manual Selection of Parameters 41321 Upgrade Strategy Parameter 41322 Database Archiving Parameter 44323 Background Process and Tool Parameters 46324 Shadow Instance Parameters 47325 Running the Shadow Instance Remotely 47

08142008 PUBLIC 370

33 Determining Versions 4834 Setting the Environment of the SAP Kernel 5035 Creating Shares and Directories and Checking Authorizations 5036 Changing the Virtual MemoryPaging File Size 5137 Isolating the Central Instance 5138 Extending Free Space in the DB2 for Linux UNIX and Windows Database 5339 Extending Free Space in the SAP MaxDB Database 54310 Extending Free Space in the MS SQL Server Database 54311 Extending Free Space in the Oracle Database 54312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode 56313 Changing the SAP MaxDB Database Recovery Mode 56314 Changing the MS SQL Server Database Recovery Mode 57315 Changing the Oracle Database Recovery Mode 57316 Standalone Database Server (Oracle) 58317 Upgrade Directory 59318 Releasing and Confirming Open Repairs and Requests 60319 Sending a Message when User Action Is Required 62320 Using the ABAP Phase List for the Upgrade 62

Chapter 4 Related SAP Notes 65

470 PUBLIC 08142008

1 Accessing Documentation

1 Accessing Documentation

Before during and after the upgrade you require additional documentation

n SAP NetWeaver online documentation for the source release and the target release

n

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Online documentation for your applicationEnd of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentation

There are different ways to access the documentation

n SAP Library documentationl SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal

l

Only valid for SAP ERPSAP SCMSAP SRM

SAP Library for your application on SAP Help PortalYou can access documentation for all product releases that are in maintenance on SAP HelpPortalEnd of SAP ERPSAP SCMSAP SRM

l

Only valid for SAP NetWeaver

Local installation of the SAP NetWeaver Library

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target releaseEnd of SAP NetWeaver

l

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local installation of the SAP Library for your application

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

08142008 PUBLIC 570

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 2: Troubleshooting and Administration Windows

Document History

The following table provides an overview of the most important document changes

Version Date Description

10 8142008 First version ‒ no changes

270 PUBLIC 08142008

Table of Contents

Chapter 1 Accessing Documentation 5

Chapter 2 Troubleshooting 921 Error Handling for ABAP 1022 Upgrade Logs 1223 Evaluating the ELG Log Files 1524 Accelerating the Runtime of Certain Phases 1625 Correcting Errors in the HIAV_CHK Phase 1826 Correcting Errors in the DBCHK Phase 1927 Correcting Errors in the BATCHCHK Phase 2028 Correcting Errors in the INTCHK and INTCHK_SW Phases 2129 Correcting Errors in the START_SHDI_FIRST Phase 21210 Correcting Errors in the JOB Phases 21211 Cleaning Up Terminated Conversions in the DB Conversion Phases 22212 Correcting Errors in the TRBATCHK_XT Phase 25213 Correcting Errors in the ACT_ltRelgt Phase 25214 Correcting Conversion Errors in the PARCONV Phase 26215 Correcting Errors in the XPRAS Phase 27216 Correcting Problems when Starting the Upgrade Program 29217 Restarting the Upgrade GUI 29218 Preparing the Restart of the Upgrade After a System Failure 30219 Correcting Problems when Processing ABAP Steps 30220 Correcting Problems when Starting the SAP System 31221 Correcting Problems when Copying SAP Programs 32222 Use of Kernel and Instance Numbers During the Upgrade 33223 Providing SAP Support with Information 33

Chapter 3 Administration 3731 Reducing Downtime 3832 Manual Selection of Parameters 41321 Upgrade Strategy Parameter 41322 Database Archiving Parameter 44323 Background Process and Tool Parameters 46324 Shadow Instance Parameters 47325 Running the Shadow Instance Remotely 47

08142008 PUBLIC 370

33 Determining Versions 4834 Setting the Environment of the SAP Kernel 5035 Creating Shares and Directories and Checking Authorizations 5036 Changing the Virtual MemoryPaging File Size 5137 Isolating the Central Instance 5138 Extending Free Space in the DB2 for Linux UNIX and Windows Database 5339 Extending Free Space in the SAP MaxDB Database 54310 Extending Free Space in the MS SQL Server Database 54311 Extending Free Space in the Oracle Database 54312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode 56313 Changing the SAP MaxDB Database Recovery Mode 56314 Changing the MS SQL Server Database Recovery Mode 57315 Changing the Oracle Database Recovery Mode 57316 Standalone Database Server (Oracle) 58317 Upgrade Directory 59318 Releasing and Confirming Open Repairs and Requests 60319 Sending a Message when User Action Is Required 62320 Using the ABAP Phase List for the Upgrade 62

Chapter 4 Related SAP Notes 65

470 PUBLIC 08142008

1 Accessing Documentation

1 Accessing Documentation

Before during and after the upgrade you require additional documentation

n SAP NetWeaver online documentation for the source release and the target release

n

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Online documentation for your applicationEnd of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentation

There are different ways to access the documentation

n SAP Library documentationl SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal

l

Only valid for SAP ERPSAP SCMSAP SRM

SAP Library for your application on SAP Help PortalYou can access documentation for all product releases that are in maintenance on SAP HelpPortalEnd of SAP ERPSAP SCMSAP SRM

l

Only valid for SAP NetWeaver

Local installation of the SAP NetWeaver Library

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target releaseEnd of SAP NetWeaver

l

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local installation of the SAP Library for your application

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

08142008 PUBLIC 570

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 3: Troubleshooting and Administration Windows

Table of Contents

Chapter 1 Accessing Documentation 5

Chapter 2 Troubleshooting 921 Error Handling for ABAP 1022 Upgrade Logs 1223 Evaluating the ELG Log Files 1524 Accelerating the Runtime of Certain Phases 1625 Correcting Errors in the HIAV_CHK Phase 1826 Correcting Errors in the DBCHK Phase 1927 Correcting Errors in the BATCHCHK Phase 2028 Correcting Errors in the INTCHK and INTCHK_SW Phases 2129 Correcting Errors in the START_SHDI_FIRST Phase 21210 Correcting Errors in the JOB Phases 21211 Cleaning Up Terminated Conversions in the DB Conversion Phases 22212 Correcting Errors in the TRBATCHK_XT Phase 25213 Correcting Errors in the ACT_ltRelgt Phase 25214 Correcting Conversion Errors in the PARCONV Phase 26215 Correcting Errors in the XPRAS Phase 27216 Correcting Problems when Starting the Upgrade Program 29217 Restarting the Upgrade GUI 29218 Preparing the Restart of the Upgrade After a System Failure 30219 Correcting Problems when Processing ABAP Steps 30220 Correcting Problems when Starting the SAP System 31221 Correcting Problems when Copying SAP Programs 32222 Use of Kernel and Instance Numbers During the Upgrade 33223 Providing SAP Support with Information 33

Chapter 3 Administration 3731 Reducing Downtime 3832 Manual Selection of Parameters 41321 Upgrade Strategy Parameter 41322 Database Archiving Parameter 44323 Background Process and Tool Parameters 46324 Shadow Instance Parameters 47325 Running the Shadow Instance Remotely 47

08142008 PUBLIC 370

33 Determining Versions 4834 Setting the Environment of the SAP Kernel 5035 Creating Shares and Directories and Checking Authorizations 5036 Changing the Virtual MemoryPaging File Size 5137 Isolating the Central Instance 5138 Extending Free Space in the DB2 for Linux UNIX and Windows Database 5339 Extending Free Space in the SAP MaxDB Database 54310 Extending Free Space in the MS SQL Server Database 54311 Extending Free Space in the Oracle Database 54312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode 56313 Changing the SAP MaxDB Database Recovery Mode 56314 Changing the MS SQL Server Database Recovery Mode 57315 Changing the Oracle Database Recovery Mode 57316 Standalone Database Server (Oracle) 58317 Upgrade Directory 59318 Releasing and Confirming Open Repairs and Requests 60319 Sending a Message when User Action Is Required 62320 Using the ABAP Phase List for the Upgrade 62

Chapter 4 Related SAP Notes 65

470 PUBLIC 08142008

1 Accessing Documentation

1 Accessing Documentation

Before during and after the upgrade you require additional documentation

n SAP NetWeaver online documentation for the source release and the target release

n

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Online documentation for your applicationEnd of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentation

There are different ways to access the documentation

n SAP Library documentationl SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal

l

Only valid for SAP ERPSAP SCMSAP SRM

SAP Library for your application on SAP Help PortalYou can access documentation for all product releases that are in maintenance on SAP HelpPortalEnd of SAP ERPSAP SCMSAP SRM

l

Only valid for SAP NetWeaver

Local installation of the SAP NetWeaver Library

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target releaseEnd of SAP NetWeaver

l

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local installation of the SAP Library for your application

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

08142008 PUBLIC 570

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 4: Troubleshooting and Administration Windows

33 Determining Versions 4834 Setting the Environment of the SAP Kernel 5035 Creating Shares and Directories and Checking Authorizations 5036 Changing the Virtual MemoryPaging File Size 5137 Isolating the Central Instance 5138 Extending Free Space in the DB2 for Linux UNIX and Windows Database 5339 Extending Free Space in the SAP MaxDB Database 54310 Extending Free Space in the MS SQL Server Database 54311 Extending Free Space in the Oracle Database 54312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode 56313 Changing the SAP MaxDB Database Recovery Mode 56314 Changing the MS SQL Server Database Recovery Mode 57315 Changing the Oracle Database Recovery Mode 57316 Standalone Database Server (Oracle) 58317 Upgrade Directory 59318 Releasing and Confirming Open Repairs and Requests 60319 Sending a Message when User Action Is Required 62320 Using the ABAP Phase List for the Upgrade 62

Chapter 4 Related SAP Notes 65

470 PUBLIC 08142008

1 Accessing Documentation

1 Accessing Documentation

Before during and after the upgrade you require additional documentation

n SAP NetWeaver online documentation for the source release and the target release

n

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Online documentation for your applicationEnd of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentation

There are different ways to access the documentation

n SAP Library documentationl SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal

l

Only valid for SAP ERPSAP SCMSAP SRM

SAP Library for your application on SAP Help PortalYou can access documentation for all product releases that are in maintenance on SAP HelpPortalEnd of SAP ERPSAP SCMSAP SRM

l

Only valid for SAP NetWeaver

Local installation of the SAP NetWeaver Library

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target releaseEnd of SAP NetWeaver

l

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local installation of the SAP Library for your application

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

08142008 PUBLIC 570

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 5: Troubleshooting and Administration Windows

1 Accessing Documentation

1 Accessing Documentation

Before during and after the upgrade you require additional documentation

n SAP NetWeaver online documentation for the source release and the target release

n

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Online documentation for your applicationEnd of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentation

There are different ways to access the documentation

n SAP Library documentationl SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal

l

Only valid for SAP ERPSAP SCMSAP SRM

SAP Library for your application on SAP Help PortalYou can access documentation for all product releases that are in maintenance on SAP HelpPortalEnd of SAP ERPSAP SCMSAP SRM

l

Only valid for SAP NetWeaver

Local installation of the SAP NetWeaver Library

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target releaseEnd of SAP NetWeaver

l

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local installation of the SAP Library for your application

Note

The documentation for the target release is not available online in your system until you havecompleted the upgrade and the installation procedure for the online documentation

08142008 PUBLIC 570

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 6: Troubleshooting and Administration Windows

1 Accessing Documentation

Before the upgrade you can make sure that you can read the DVD offline After the upgradeyou need to install the documentation for the target release

Only valid for SAP CRMSAP SCMSAP SRM

Note

The local installation of the SAP Library for your application does not contain the SAPNetWeaver Library

End of SAP CRMSAP SCMSAP SRM

End of SAP CRMSAP ERPSAP SCMSAP SRM

n Troubleshooting and administration documentationThe documentation is included in the upgrade program

SAP Help Portal

Target Release Documentation

Only valid for SAP NetWeaver

You can find the SAP Library for SAP NetWeaver 70 on SAP Help Portal at httphelpsapcom

SAP NetWeaver SAP NetWeaver ltReleasegt SAP NetWeaver ltReleasegt Knowledge Center SAP NetWeaverltReleasegt Library ltlanguagegt End of SAP NetWeaver

Only valid for SAP CRM

You can find the SAP Library for SAP CRM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Customer Relationship Management SAP CRM 70 End of SAP CRM

Only valid for SAP ERP

You can find the SAP Library for SAP ERP on SAP Help Portal at httphelpsapcom SAPERP SAP ERP Central Component ltreleasegt End of SAP ERP

Only valid for SAP SCM

You can find the SAP Library for SAP SCM 70 on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supply Chain Management ltreleasegt End of SAP SCM

Only valid for SAP SRM

You can find the SAP Library for SAP SRM on SAP Help Portal at httphelpsapcom SAPBusiness Suite SAP Supplier Relationship Management ltreleasegt End of SAP SRM

670 PUBLIC 08142008

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 7: Troubleshooting and Administration Windows

1 Accessing Documentation

Source Release Documentation

Only valid for SAP Web AS 640

You can find the SAP Library for SAPNetWeaver 2004 on SAPHelp Portal at httphelpsapcom

SAP NetWeaver 2004 ltlanguagegt SAP NetWeaver End of SAP Web AS 640

Only valid for SAP Web AS 620

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 620 ltlanguagegt End of SAP Web AS 620

Only valid for SAP Web AS 610

You can find the SAP Library for SAP Web Application Server 620 on SAP Help Portal athttphelpsapcom Prior to SAP NetWeaver 2004 SAP Web Application Server =lt 630 SAP Web

Application Server 610 ltlanguagegt End of SAP Web AS 610

Only valid for SAP R3 46C

You can find the SAP Library for SAP R3 46C on SAP Help Portal at httphelpsapcom

SAP R3 and R3 Enterprise SAP R3 Release 46C ltlanguagegt End of SAP R3 46C

Only valid for SAP R3 46B

You can find the SAP Library for SAP R3 46B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 46B ltlanguagegt End of SAP R3 46B

Only valid for SAP R3 45B

You can find the SAP Library for SAP R3 45B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 45B ltlanguagegt End of SAP R3 45B

Only valid for SAP R3 40B

You can find the SAP Library for SAP R3 40B on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 40B ltlanguagegt End of SAP R3 40B

Only valid for SAP R3 31I

You can find the SAP Library for SAP R3 31I on SAP Help Portal at httphelpsapcom SAPR3 and R3 Enterprise SAP R3 Release 31I ltlanguagegt End of SAP R3 31I

08142008 PUBLIC 770

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 8: Troubleshooting and Administration Windows

1 Accessing Documentation

Only valid for SAP NetWeaver

Local Installation of the SAP NetWeaver LibraryBefore and during the upgrade you must read the online documentation for the target release onthe DVD

Recommendation

If there is a Support Package available for the documentation use the documentation version onSAP Help Portal

End of SAP NetWeaver

Only valid for SAP CRMSAP ERPSAP SCMSAP SRM

Local Installation of the SAP Library for Your ApplicationBefore and during the upgrade you must read the online documentation for the target release onthe DVDEnd of SAP CRMSAP ERPSAP SCMSAP SRM

Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade programThe upgrade tool unpacks the documentation at the beginning of roadmap step ExtractionYou can access the documentation as follows

n From a link on the upgrade GUI Proceed as follows1 If it is not running yet start the upgrade program2 On page httplthost namegt4239 choose ABAP documentation3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

n From file Troubleshooting_and_Administration_Windowspdf in directory UPGabaphtdoc

870 PUBLIC 08142008

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 9: Troubleshooting and Administration Windows

2 Troubleshooting

2 Troubleshooting

This part of the document contains additional information on how to proceed when you want tocorrect known problems that have occurred during the upgrade

Note

In the following some information is related to phases As long as the upgrade program runs thephase name is displayed on the program tool tab pageIf the upgrade program displays a dialog box and you need further information about the requiredinput you can identify the upgrade phase you are currently in using the SAPupConsolelogThis log file is located at ltupgrade directorygtabaplog

n Error Handling for ABAP [page 10]n Logsl Upgrade Logs [page 12]l Evaluating the ELG Log Files [page 15]

n Correcting errors after phasesl Accelerating the Runtime of Certain Phases [page 16]l Correcting Errors in the HIAV_CHK Phase [page 18]l Correcting Errors in the DBCHK Phase [page 19]l Correcting Errors in the BATCHCHK Phase [page 20]l Correcting Errors in the INTCHK and INTCHK_SW Phases [page 21]l Correcting Errors in the START_SHDI_FIRST Phase [page 21]l Correcting Errors in the JOB Phases [page 21]l Cleaning Up Terminated Conversions in the DB Conversion Phases [page 22]l Correcting Errors in the TRBATCHK_XT Phase [page 25]l Correcting Errors in the ACT_ltRelgt Phase [page 25]l Correcting Conversion Errors in the PARCONV Phase [page 26]l Correcting Errors in the XPRAS Phase [page 27]

n General problemsl Correcting Problems when Starting the Upgrade Program [page 29]l Restarting the Upgrade GUI [page 29]l Preparing the Restart of the Upgrade After a System Failure [page 30]l Correcting Problems when Processing ABAP Steps [page 30]l Correcting Problems when Starting the SAP System [page 31]l Correcting Problems when Copying SAP Programs [page 32]l Use of Kernel and Instance Numbers During the Upgrade [page 33]

08142008 PUBLIC 970

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 10: Troubleshooting and Administration Windows

2 Troubleshooting21 Error Handling for ABAP

l Providing SAP Support with Information [page 33]

As well as the problems listed here also read the SAP Notes that are relevant to this upgrade

21 Error Handling for ABAP

If the upgrade program reports an error during the upgrade it is essential that you find out whatcaused this error before you continue with the upgrade

Tool Reaction

The upgrade program reacts on errors in different ways

n The phase in which the error occurs is interrupted There is an error message on the screen and inthe corresponding log file [page 12]

n The phase in which the error occurs continues but writes an error message into the correspondinglog file

n The tool aborts

n In rare cases the upgrade program waits for processes (tp background jobs and so on) which haveterminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Upgrade Program

The upgrade program provides help for many known errors

File dev_SAPup

Due to internal program errors the upgrade tool can abort An error message appears on the userinterface In some cases the upgrade tool creates a stack trace You can find it in file dev_SAPup eitherin subdirectory tmp of the abap subdirectory of the upgrade directory or directly in the upgradedirectoryIf the error persists after repeating a phase open a customer message and include the stack trace Thestack trace speeds up processing of the customer messageIf you can continue the upgrade after a restart open a customer message anyway and include thestack trace This helps SAP fix the tool error for future versions of the upgrade tool

Log Files

n ELG Log FilesProvided that an ELG file [page 15] was generated at the end of the phase that terminated this fileprovides helpful additional information on the error(s) that occurred during the phase Check theELG file according to the following criteria

1070 PUBLIC 08142008

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 11: Troubleshooting and Administration Windows

2 Troubleshooting21 Error Handling for ABAP

l No errors have occurred if the log contains a return code less than eight at the end of a stepand there are no error messages for this step

l Errors have occurred if the return code is eight or higher and there are error messagespreceding it Analyze the error using the detailed log file

l If a return code is equal to or greater than twelve or is missing entirely tp or a program calledby tp has terminated You can determine the termination point from the last line of the SLOGlog file If tp or R3trans has terminated you must analyze the last log file written

n Detailed Log FilesIn the ELG file the heading of each phase step displays the name of a log file that contains moredetailed information about the errorThe detailed log files are stored in subdirectory log of the abap subdirectory of the upgradedirectory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The joblog records the processing of background jobs All background job steps executed are listed in the joblog with their exit statuses If a background job is terminated you can obtain further informationabout the reasons using the job log Proceed as follows

1 Log on to the central instance of the SAP system

Caution

During phases STARTSHDI_FIRST and STOPSHDI_LAST you must log on to the shadow instanceinstead of the central instance

2 Call transaction SM37 as user DDIC3 Enter as the job name and specify the job conditions (for or after event enter )4 Start the job display ( F8 )5 Sort the job list so that it is displayed chronologically

The job name of the job displayed last is the most recent job and generally the job belonging tothe terminated step

6 To display the job log file double-click the terminated jobFor some releases you need to select the terminated job and choose Job Log to display the job log file

7 To display the long text for the error or the ABAP short dump if it was an ABAP job which hasterminated with a syntax error double-click the error line in the job log file

SAP System Log

The system log provides more accurate information about errors It logs the incorrect system statesoccurring during operation All irregularities such as a lack of resources or database errors duringoperation are collected here The system log is administered by the SAP system and is available in thefile system as a non-readable file You use transaction SM21 to display the system log

08142008 PUBLIC 1170

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 12: Troubleshooting and Administration Windows

2 Troubleshooting22 Upgrade Logs

Since the upgrade is always performed by user DDIC it is mainly the system log entries for this userthat are relevant for error analysis The upgrade itself does not know about the system logTo analyze the system log proceed as follows

1 Call transaction SM21 as user DDIC2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed whichcorrespond to the time when the terminated phase ran

3 Look for entries for user DDIC4 To display detailed error descriptions double-click a single line in the system log

Sometimes errors occur at the lowest system level These errors are normally stored in the instancelogs During the upgrade you can find these logs in the current working directory of your SAPinstance as follows

1 Open the current working directory of your central instanceltupgrade directorygtabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written3 Examine the log files generated last for errors that may be related to the upgrade

Further Sources of Problems

If no clear errors are found there may also be a lack of resources in the database or the file system orincorrect profile parameters may have caused the phase to terminate

22 Upgrade Logs

The upgrade program logs all actions in log files You can use these log files to monitor your upgradeUnless otherwise specified below the log files are stored in subdirectory log of the abap subdirectory ofthe upgrade directory If you encounter any errors you can analyze them to help you find a solution

Features

SAPupchklog and SAPuplog

The upgrade program records all actions on the ABAP system in the log files SAPupchklog (duringthe preparation roadmap steps) and SAPuplog (during the upgrade roadmap steps) These logfiles provide you with a general overview of the status of the upgrade They contain informationon all phases performed up to this point the number of reruns runtimes final status and so onSAPupchklog and SAPuplog are updated by the upgrade program onlyTemporary logs are located in subdirectory tmp of the abap subdirectory of the upgrade directory

1270 PUBLIC 08142008

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 13: Troubleshooting and Administration Windows

2 Troubleshooting22 Upgrade Logs

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logsa for each stepTo monitor the collective log you can display the log using the command type or tail (MKS tools)Do not use the option -f for the command tail and do not edit the file using an editor otherwise thefile is write-protected by tpEach tp-driven phase is divided up into a number of different steps whose start and end times arenoted in the SLOG log The start and end of a phase are indicated by the lines START put and STOP putThe section in the SLOG log relating to the ACT_ltrelgt phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksysX PS1 20010307182423ps1adm ds0007

STOP locksysX PS1 20010307182423ps1adm ds0007

START tpsapstart PS1 3 20010307182423ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423ps1adm ds0007

START locksys PS1 | 20010307182423ps1adm ds0007

STOP locksys PS1 | 20010307182423ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp Forinformation about these actions see section Transport Phase Log Files below

08142008 PUBLIC 1370

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 14: Troubleshooting and Administration Windows

2 Troubleshooting22 Upgrade Logs

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executedby the upgrade program during the upgrade

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectorytmp of the abap subdirectory of the upgrade directory where you can also monitor them withtail -f After the various steps of the phase have been completed tpmoves the individual logs tosubdirectory log of the abap subdirectory of the upgrade directoryThe names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgtwhere ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the nameof your SAP systemYou can determine the relevant transport request from the name of the log file by replacingthe transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period ExampleSAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgtThe table below lists the most important steps together with their log names and specifies whichprograms execute the steps

Log Files of Most Important Steps

Step Log Name Program Executing the Step

SHADOW_IMPORT SAPKltSAPSIDgt R3trans

DD IMPORT (H) SAPHltSAPSIDgt R3trans

DD ACTIVATION (A) SAPAltSAPSIDgt ABAP program (RDDMASGL)

DISTRIBUTION OF DD OBJECTS(S)

DSltDATEgtltSAPSIDgt ABAP program (RDDDIS0L)

TBATG CONVERSION OF DDOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MCOBJECTS (N)

NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINEDOBJECTS (D)

SAPDltSAPSIDgt ABAP program (RDDDIC1L)

1470 PUBLIC 08142008

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 15: Troubleshooting and Administration Windows

2 Troubleshooting23 Evaluating the ELG Log Files

Step Log Name Program Executing the Step

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTIONOF REPORTS AFTERPUT (R)

SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the upgrade directoryyou can also display them in the SAP systemYou can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays allthe logs for a specific transport request In the Transport Request field enter the name of the transportrequest (for example SAPKltrelgtD01) and then choose ExecuteA brief overview of all the logs existing for this transport request appears Double-click a line todisplay a log for this step The logs are broken down into several levels Level 1 only displays thereturn code for the step Check at least level 2 to display any error messages Double-click an error tosee its long textAfter completing each tp-driven phase the upgrade program creates a summary of all individuallogs in this phaseThe names of the summaries usually comprise the phase name (without underscores) and theextension ELG (for example DDICltrelgtELG) The summary contains the names of the individuallogs any errors that occurred and the return codes If no errors have occurred you need to checkthese summaries only

23 Evaluating the ELG Log Files

The ltPHASEgtELG log files are summary log files that contain a list of all the errors that occurredduring a specific phase of the upgrade From these files you can call up detailed log files that containmore information When errors are detected during a phase a message appears and prompts you torepeat that phase First check the ltPHASEgtELG log to find out why the step terminated In some casesyou can choose ignore in the upgrade program to continue with the upgrade and avoid repeating thefailed phase Generally you must always remove the cause of the error When you choose ignore theupgrade program prompts you to enter a password if the errors are serious In this case you mustget approval from SAP Support to ignore the error Remove all errors to avoid the risk of follow-onerrors If you are not sure how to proceed contact SAP Support

Procedure

1 Analyze the errors using the detailed log file if necessary The name of this log is listed in theheader of each phase stepn No errors have occurred if a return code less than 8 appears in the log at the end of a step

and no error messages appear for that step

08142008 PUBLIC 1570

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 16: Troubleshooting and Administration Windows

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

n A return code of 8 indicates that some individual objects have not been processed or not beenprocessed completely

n If a return code is greater than or equal to 12 then tp or a program called by tp has terminated2 Determine when the program terminated from the last two lines of the SLOG log If tp or R3trans

have terminated analyze the last log that was written For a chronological list of the files in bothlog directories enter the following commandsDIR OD usrsapputlog

DIR OD usrsapputtmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP systemto determine the cause of the errora) Log on as user DDIC and call transaction SM37 Enter the job name as the name of the report

that usually processes the terminated step (RDDMASGL for DD ACTIVATION for example)Make sure that the date on the SM37 input screen is correct and that an asterisk () appears inthe or after event field The job overview normally displays one canceled job and one backgroundjob that completed normally

b) Double-click the canceled job to display the job logc) Double-click the error line to display the long text for the error

Note

If you use a user ID other than DDIC to log on to the SAP system and correct the error the SAPsystem may prevent you from logging onIn this case proceed as followsA) Unlock the SAP systemB) Log on to the SAP system and correct the errorC) Lock the SAP system again

4 Once you have found and corrected the error repeat the phase by selecting repeat in the upgradeprogramThe repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

24 Accelerating the Runtime of Certain Phases

Phases Running ABAP ProgramsThese phases use the SAP system to operate If you improve the performance of the SAP system thiscan speed up these phases

1670 PUBLIC 08142008

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 17: Troubleshooting and Administration Windows

2 Troubleshooting24 Accelerating the Runtime of Certain Phases

Only valid for Oracle

Phases TABSPC_PREP and CNV_LISTYou experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Althoughyou have applied the actions recommended in SAP Note 871455 the runtimes of the phases havenot decreased considerably

Caution

This procedure is only a temporary workaround and needs to be reset after the phases have run

Proceed as described in SAP Note 762426End of Oracle

EU_IMPORT Phases

n If you chose the preconfiguration mode low resource use these phases run during downtime Toreduce the runtime you can allow the SAP system to start multiple R3load processes In phaseswhere only one package is imported this parameter has no influence on the runtime

n If you chose the preconfiguration mode standard resource use or high resource use you can slow downthe import of the substitution set to reduce its influence on the production system If you haveextended the runtime for the import of the substitution set this also extends the duration ofthe individual phases

n If archiving is still activated it can slow down the phases if the directory where the archives arestored is full or the mechanism that moves these archives is too slow

n A slow access to the DVDs or the directory to which you have copied the contents of the DVDs canincrease the runtime of the EU_IMPORT phases

Phase RUN_RDDIT006This phase analyzes the SAP system to find objects modified by the customer and customer objectsTherefore the runtime of phase RUN_RDDIT006 is longer for SAP systems with a lot of modificationsor customer objects As this phase starts an ABAP program you can use the respective ABAPtransactions to analyze the performance of this phase

DIFFEXP PhasesAs these phases perform copy-to-shadow actions or export the transport requests generated duringphase RDDIT006 they take longer for SAP systems with a lot of modifications or customer objects

Phase ACT_ltRelgtThe ACT_ltrelgt phase uses parallel processesIf you chose the preconfiguration mode standard resource use or high resource use it uses the number ofparallel processes used during production operation that you have entered during the preparationroadmap steps of the upgrade program If you chose the preconfiguration mode low resource use phase

08142008 PUBLIC 1770

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 18: Troubleshooting and Administration Windows

2 Troubleshooting25 Correcting Errors in the HIAV_CHK Phase

ACT_ltrelgt uses the number of parallel background processes that you have entered during phaseINITSUBSTAs phase ACT_ltrelgt calls up the ABAP Dictionary mass activator program it takes longer for SAPsystems with a lot of modifications or customer objects and if you have inlcuded a lot of add-onsand Support Packages

SHADOW_IMPORT PhasesThese phases import the upgrade data into Customizing tables as well as the transport requests ofadd-ons Support Packages and languages During this phase only the part for the shadow system isimported the remaining parts are imported during the TABIM_UPG phase These phases take longerfor upgrades where a lot of add-ons and Support Packages have been included in the upgrade orwhere many languages have to be imported The duration of the import also depends on the numberof clients in the systemWith preconfiguration mode manual selection These phases use parallel processes If you chose thepreconfiguration mode standard resource use or high resource use they use the number of parallel processesused during production operation that you have entered during the preparation phases If youchose the preconfiguration mode low resource use it uses the number of parallel background processesthat you have entered during phase INITSUBST

Phase PARCONV_UPGIn this phase tables are converted to the target release structure The PARCONV_UPG phase uses thenumber of parallel background processes you specified and three tp processesThe runtime of this phase may be longer for the following reasons

n Very large tables have to be converted The tables that are converted are listed in the upgradeanalysis file which also displays the conversion time for each table

n If tables get a new index on the target release or an index needs to be regenerated these tables arelisted in the upgrade analysis file under DDLs The time needed to create the index depends onthe size of the table

n Other DDL statements The runtime of ALTER TABLE or ADD FIELD statements with fields thathave default values depends on the size of the table

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions Ifthe instance profile name does not contain DVEBMGS the phase stops with an error message

ProcedureMake sure that the instance profile name is named after the SAP naming convention and repeatthe phase

1870 PUBLIC 08142008

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 19: Troubleshooting and Administration Windows

2 Troubleshooting26 Correcting Errors in the DBCHK Phase

26 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP systemTo do this the upgrade program runs the transport control program tp which logs on to thedatabase and reads the necessary information from thereAny problems in this phase are usually due to a failed database connection

PrerequisitesThe system has displayed the error message No information received from the database

Only valid for SAP R3 31I

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transactionFor more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 31I

Only valid for SAP R3 40BSAP R3 45B

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Workbench Organizer

2 If the Workbench Organizer has not been initialized call transaction SE06 in the SAP system asuser DDIC

3 In the initial screen of transaction SE06 select New installation as the system status and then thecorrect System configuration

4 Choose Set up5 Choose Yes or Continue in the dialog boxes that follow until all system settings have been made

Exit the transaction

08142008 PUBLIC 1970

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 20: Troubleshooting and Administration Windows

2 Troubleshooting27 Correcting Errors in the BATCHCHK Phase

For more information about transaction SE06 see the online documentation at Help Applicationhelp Setting up the Workbench Organizer and the Transport System Configuring the Workbench Organizer withTransaction SE06

End of SAP R3 40BSAP R3 45B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP

Web AS 640

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the upgrade directoryAny problems with tp are usually due to a non-initialized Transport Organizer

2 To initialize the Change and Transport System call transaction STMS from the TransportManagement System (TMS)For more information see the TMS online documentationTo display the documentation choose Information in transaction STMS or the following path inthe SAP Library [page 5] of your source release

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 46B

Basis Components Change and Transport System Transport Management SystemEnd of SAP Basis 46CSAP Basis 46DSAP R3 46B

Only valid for SAP Web AS 620SAP Web AS 610

SAP Library mySAP Technology Components SAP Web Application Server Change and TransportSystem Transport Management SystemEnd of SAP Web AS 620SAP Web AS 610

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SoftwareChange Management Change and Transport System Transport Management SystemEnd of SAP Web AS 640

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 46BSAP Web AS 610SAP Web AS 620SAP Web AS 640

27 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the upgrade directory To do this thebackground job RDDIT008 is started on the specified background server This job writes a test log inthe tmp subdirectory of the upgrade directory

Procedure

1 If errors occur call transaction SM37 to check whether the background job has run

2070 PUBLIC 08142008

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 21: Troubleshooting and Administration Windows

2 Troubleshooting28 Correcting Errors in the INTCHK and INTCHK_SW Phases

n If the background job cannot be started this is generally due to a problem with the nameof the background servera) Check whether the host specified in phase INITPUT is included in the list with a running

background serviceTo do this perform a test call of functionmodule TH_SERVER_LIST in transaction SE37 Todisplay the list double-click the table parameter LIST after executing the function module

b) Depending on the problem you either have to change the network configuration or changethe entries made in the INITPUT phase

n If the job terminates call transaction SM21 to check the system log of the SAP systemn If the job is successful however the upgrade program cannot find the log make sure of the

followinga) The file system of the upgrade directory must be mounted on the background serverb) The value of the SAP profile parameter DIR_PUTmust match the current upgrade directory

2 To repeat the phase choose repeat

28 Correcting Errors in the INTCHK and INTCHK_SW Phases

These phases check whether the inactive nametab is empty If not an error occurs

Procedure

1 To find the affected objects analyze the DDXTTCHKLOG file2 Activate these objects using transaction SE11

The inactive nametab is then empty3 Continue the upgrade with repeat

29 Correcting Errors in the START_SHDI_FIRST Phase

If the shadow instance does not start proceed as described in SAP Note 525677

210 Correcting Errors in the JOB Phases

A JOB phase starts a background job in the SAP system and waits for it to be completed If problemsoccur during execution of the background job you receive an error message

Note

The naming convention for the JOB phases is JOB_ltnamegt or RUN_ltnamegt where ltnamegt is the nameof the job or report

08142008 PUBLIC 2170

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 22: Troubleshooting and Administration Windows

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Procedure

1 Log on to the SAP system as user DDIC2 Call transaction SM37 and restrict the start time and start date of the background job as much

as possiblen If no background job was started this is generally due to a syntax error in the calling program

If there is no SAP Note explaining this error contact SAP Supportn If the background job was started there are two possible situationsl The job was terminated

Check whether the error can be reproduced by selecting repeat in the upgrade programIf the error occurs again contact SAP Support In this case proceed as described in ProvidingSAP Support with Information [page 33]

l The job was completed but with error messagesIn certain situations you can ignore these error messages In this case the upgrade programdoes not require a password if you choose ignore If you are not sure how to proceed contactSAP Support

211 Cleaning Up Terminated Conversions in the DBConversion Phases

These conversion errors are indicated by the following upgrade program error messages

n Restart logs of DB conversions found

n Outstanding DB conversions found

These errors can occur in the phases CNV_CHK_GEN CNV_CHK_IMP and CNV_CHK_XT

Note

If both messages appear process the message Restart logs of DB conversions found first

Procedure for ldquoRestart Logs of DB Conversions FoundrdquoTo clean up terminated conversions indicated by the message Restart logs of DB conversions

found proceed as follows

1 To find the terminated conversions call the database utility transaction (transaction SE14)2 Choose DB Requests Terminated

A list of the terminated conversions appears3 Double-click a table name to see its details4 Check the meaning and status of the table

a) Find out whether the table is still needed Sometimes the tables are test tables that are nolonger needed

b) Ask the last person who changed the table or the table owner to find out its status

2270 PUBLIC 08142008

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 23: Troubleshooting and Administration Windows

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

Only valid for SAP R3 31I

If the table is no longer needed choose Cancel adjustment in the detailed display This preventsthe conversion from being continued automatically The table itself does not return to aconsistent state Any data that is still in the temporary table is lost during the next conversionIn some cases however the table was already corrected without the reset log being deletedThe function Cancel adjustment is harmless in this caseEnd of SAP R3 31I

Only valid for SAP R3 40B

If the table is no longer needed choose Cancel adjustment in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionCancel adjustment is harmless in this caseEnd of SAP R3 40B

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

If the table is no longer needed choose Unlock table in the detailed display This prevents theconversion being continued automatically The table itself does not return to a consistent stateAny data that is still in the temporary table is lost during the next conversion In some caseshowever the table was already corrected without the reset log being deleted The functionUnlock table is harmless in this caseEnd of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

c) You can determine the state of the table with Check Database object and Check Runtime object d) Also check if the table contains the data you expect You can do this with transaction SE16

for example If the data does not exist it could still be in the temporary table Contact yourSAP consultant or SAP Support for help in saving this data

5 Determine the cause of the errorIf you find out that the table is still needed choose Object log Look for error messages that explainwhy the conversions were terminated You could encounter the following problems heren You cannot find a log because it was deleted at some time in the past Continue with step 6

(continue the conversion to the end)n The log does not contain an errormessage but ends abruptly This indicates that the conversion

was stopped by an external event Call transaction SM21 to read the system log and find out theapproximate time the conversion was terminated and to look for the cause of the error

n If the log clearly gives a reason for the error you must correct it6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this will takechoose processing type Background

08142008 PUBLIC 2370

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 24: Troubleshooting and Administration Windows

2 Troubleshooting211 Cleaning Up Terminated Conversions in the DB Conversion Phases

The situation can be as followsn The conversion finished successfully You can see this because the error message disappears

the Check function does not display any further problems and there is a success message inthe object log

n The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine thecause of the error)

If you still cannot complete the conversion after several attempts contact an SAP consultant orSAP Support

Procedure for ldquoOutstanding DB conversions foundrdquoTo clean up terminated conversions indicated by the message Outstanding DB conversions foundproceed as follows

Caution

Process this message after you have processed themessage Restart logs of DB conversions found

1 Determine the objects that are affecteda) Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing b) Choose All requests

The worklist of the conversion program appears This worklist was generated by developmentsor modifications in your SAP system but has not yet been processed

c) Choose DB requests Created with import The worklist that was not processed correctly during the last upgrade appears

2 Check the meaning and status of the requestsIn contrast to the procedure for the message Restart logs of DB conversions found thisprocedure can also include requests for indexes views and matchcode objects The requests thatare found are not always terminated They might not even have been starteda) Ask the last person who changed the object if the request should still be processedb) If the user does not want it to be processed select the request and choose Delete selected

This removes the objects from the worklist of the conversion programDo not remove requests from the last upgrade

3 Process the outstanding requestsYou can select the requests from the list of mass processing requests and schedule a job forexecution with the function Schedule selectionsa) Go to the detailed display of the object by double-clicking it in the list of requests created

by the importb) Schedule the request or continue it Since you do not know how long this will take choose

processing type Background

2470 PUBLIC 08142008

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 25: Troubleshooting and Administration Windows

2 Troubleshooting212 Correcting Errors in the TRBATCHK_XT Phase

212 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table containsentries they could be the remains of an import or export that either terminated or is still runningThe upgrade program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information on this see Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide under the following messagesUnresolved request found in TRBAT

TRBAT entry indicates that a batch job is running

TRBAT entry indicates that a batch job has finished

Corrupted TRBAT entry found

213 Correcting Errors in the ACT_ltRelgt Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_ltrelgt phase to adjustyour modifications to SAP objects so that they correspond to the latest SAP standard version ofthe objects If your SAP system has been modified error messages with return code 8might occurduring the ACT_ltrelgt phaseThe errors are listed in the ACTLOGELG log file It shows the same return code for all requestsno matter in which request the errors occurred Check the error messages in the log file Errorsoccurring several times for different objects can have the same cause In this case only the objectthat causes the original error must be corrected and the activation must be restarted For example amissing data element leads to error messages for all objects using it

PrerequisitesBefore you can correct ABAP Dictionary objects that cannot be activated you may need to unlock theshadow instance of the SAP system Proceed as follows

1 Log on as user ltSAPSIDgtadm2 Enter the following commands

cd ltupgrade directorygtabapbin

SAPupexe unlockshd ltSAPSIDgt

08142008 PUBLIC 2570

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 26: Troubleshooting and Administration Windows

2 Troubleshooting214 Correcting Conversion Errors in the PARCONV Phase

Procedure

1 Log on to the shadow instance as a user other than DDICIf you have not yet created users on the shadow instance do so now as described inMaking Entries forthe Roadmap Step Downtime in the upgrade guide

2 Make the required corrections

Caution

To make the corrections use only the maintenance transaction of the ABAP Dictionary (SE11)Do not try to repair the objects with the Database Utility transaction (SE14) This can cause seriousinconsistencies

3 If you had to unlock the SAP system as described under ldquoPrerequisitesrdquo lock it again with thefollowing commandscd ltupgrade directorygtabapbin

SAPupexe lockshd ltSAPSIDgt

ResultOnce you have corrected all the errors you can proceed with the upgrade where it terminated inthe ACT_ltrelgt phases by selecting repeat in the upgrade programIf you choose ignore severe errors all error messages with return code 8 are ignored

214 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors canroughly be divided into two classes

n Technical problems on the databaseYou can recognize these in the system log (transaction SM21) where they are marked withSQL-ERROR followed by an abbreviation with an error number The problem is often caused bya lack of space

n Logical errors in the object definitionThese could also appear in the form of SQL errors Some of them however are already detectedby the system before a command can be given to the database This type of error frequently occursif you decide to revert to the SAP standard when you use the modification adjustment functions intransaction SPDD (ACT_ltrelgt phase)

2670 PUBLIC 08142008

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 27: Troubleshooting and Administration Windows

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Example

A field was added to an SAP table This field was also used in an index or view In the ACT_ltrelgtphase however you decided to return to the standard definition of the table (using transactionSPDD) and this additional field was removed The index or view definition is now incorrect sincethe relevant table field is missing If the index definition is not corrected and the ACT_ltrelgt phasewas completed with ignore there will be errors when the objects are created

Procedure

1 Analyze the PARCONVELG log2 Remove the cause of the errorn Technical problems on the database

Read the documentation in the database system about how to correct the error If necessaryextend the database

n Logical errors in the object definitionCorrect the objects To do this you can use transaction SE11 In the above example you couldfor instance remove the deleted field from the index or view definition or reinsert the deletedfield into the table Also check whether the objects that are not contained in the standardsystem and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information on alternative procedures see SAP Note 177680

215 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the upgrade programstops and refers to the XPRASUPGELG log which contains error messages with the following headerIf errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation programstops and refers to the XPRASUPGELG log which contains error messages with the following header~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in ltfile namegt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If this header is followed by lines other than the return code then errors have occurred while thereports were being executed In addition to the actual error lines a separate line indicates the namesof the reports that generated the preceding error messagesYou can display a detailed help text for each of these error messages in the SAP system These textsusually contain all the information you need to correct the error

Finding Help Texts for Error Messages

1 Search the XPRASUPGELG log to find the file name specified in the header

08142008 PUBLIC 2770

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 28: Troubleshooting and Administration Windows

2 Troubleshooting215 Correcting Errors in the XPRAS Phase

Note

The file name that appears in the header of XPRASUPGELG is important for finding the help textThe file name always has the following format

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

SAPRltIDgtltSAPSIDgt

End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

ltIDgt can be any string of six charactersThe name of the relevant transport request can be derived from the two names Replace the Rwith a K and delete the period and all characters that follow itYou now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system3 Call transaction SE094 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt5 To display the individual transport logs choose Goto Transport logs 6 To navigate to the log display for this step double-click the line Exec after put

You can expand the log to view it in more detail The error messages will generally be visible asof the second level To display a help text position the cursor on the error message and chooseLong text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error2 When you have corrected all the errors repeat the upgrade phase with the upgrade program3 If you need more information or if the report still results in errors when you repeat the XPRAS_UPG

phase read the documentation of the report in question To access this information log on to theSAP system Call transaction SE38 and display the documentation for the report that is namedin the error log

4 If you choose ignore the upgrade program gives you two options for continuing the upgraden repair severe errors

n ignore all errorsChoose repair severe errors The upgrade program repeats the phase and ignores all error messageswith the return code 8 The errors must be removed after the upgradeYou require a password for ignore all errors The upgrade program then continues with the nextphase without executing the following XPRAs Before you can choose ignore you must haveapproval from SAP Support

Correcting Errors After the UpgradeIf possible correct errors immediately However you can correct some errors that occur during theexecution of XPRA reports after you have completed the upgrade This option makes sense for

2870 PUBLIC 08142008

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 29: Troubleshooting and Administration Windows

2 Troubleshooting216 Correcting Problems when Starting the Upgrade Program

example when special measures in the SAP application areas are necessary to correct the errors andthe corresponding specialists are not available right now To do this you must suppress the executionof the corresponding report before you repeat the upgrade phase After the upgrade correct the errorand run the report manually using transaction SE38For technical instructions on skipping an XPRA see SAP Note 122597

Caution

Only skip an XPRA report program if you are sure you can execute it later (for example if an SAPNote tells you that this is allowed)If you cannot execute an XPRA later and still want to skip it contact SAP Support

216 Correcting Problems when Starting the UpgradeProgram

The initial startup of the SL controller can fail if for example the hardware resources are notsufficient so that SAP JVM cannot run When you fix the problem and restart the SL controller theExtraction step issues an error messages because it cannot unpack the tools The reason is that whenyou restart the SL controller from the upgrade directory it can no longer access theMaster DVDand cannot extract the tools

ProcedureRestart the SL controller from the upgrade directory using the following commandltupgrade directorygt STARTUPBAT -srvarg=DSUServicecdpath=MASTERDVDPATH

217 Restarting the Upgrade GUI

If the graphical user interface (GUI) of the upgrade tool aborts proceed as follows

1 Stop the GUI process with operating system means2 Start the upgrade program as described in the upgrade guide in chapter Upgrade Process sections

Starting the Upgrade Program and Starting the Upgrade GUI

08142008 PUBLIC 2970

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 30: Troubleshooting and Administration Windows

2 Troubleshooting218 Preparing the Restart of the Upgrade After a System Failure

218 Preparing the Restart of the Upgrade After a SystemFailure

If the system fails (due to a power failure for example) the upgrade program tp and R3trans can nolonger perform certain cleanup actions Before you restart the upgrade after a system failure youmust make sure that you meet the requirements for restarting the system successfully

Procedure

1 Start the SAP system2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from

table TRBAT3 Call transaction SM37 to delete all the released background jobs related to the processing of a

phase with the exception of RDDIMPDP4 To change the status of all the current or active background jobs to canceled run report

RSBTCRPR and then call transaction SM37 to delete these jobs5 Call transaction SM50 to cancel any background jobs that have already been restarted6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the upgrade directory

to the log subdirectory7 Restart the upgrade as described in Restarting the Upgrade Program in the upgrade guide

219 Correcting Problems when Processing ABAP Steps

Some of the ABAP steps are performed in the SAP system These are

n ABAP Dictionary activation (A)n Distribution of ABAP Dictionary objects (S)n Table conversion (N)n Matchcode activation (M)n Import of application objects (D)n Update of version management (U)n Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP systemTo trigger an ABAP step tp writes control information to this tableThe JOB_RDDNEWPP phase schedules the event-driven background job

Procedure

1 Check that the SAP system was started correctly Log on in client 000 as user DDIC2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

In the or after event field enter an asterisk () so that event-driven jobs are also displayed

3070 PUBLIC 08142008

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 31: Troubleshooting and Administration Windows

2 Troubleshooting220 Correcting Problems when Starting the SAP System

3 Check when RDDIMPDP last ran and whether it ran without errors4 Check whether the control information in table TRBAT has been entered correctly

The table must have one HEADER entry and should contain one entry for each transport requestWhile the ABAP Dictionary objects are being distributed (S) and the tables converted (N) tableTRBAT may contain only one HEADER entry since these steps are not carried out by transportrequest

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started thebackground job that processes the ABAP step

For more information on the transport control program tp and the communication between tp andthe SAP system see the SAP Library [page 5] for your source release at

Only valid for SAP R3 31I

R3 Library BC ‒ Basis Components System Administration Transport Control Transport Control Program tpEnd of SAP R3 31I

Only valid for SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

SAP Library Basis Components Change and Transport System BC ‒ Transport Tools Transport ControlProgram tpEnd of SAP Basis 46CSAP Basis 46DSAP R3 40BSAP R3 45BSAP R3 46B

Only valid for SAP Web AS 610SAP Web AS 620

SAP Library mySAP Technology Components SAP Web Application Server Change and Transport SystemTransport Tools Transport Control Program tpEnd of SAP Web AS 610SAP Web AS 620

Only valid for SAP Web AS 640

SAP NetWeaver Library SAP NetWeaver by Key Capability Solutions Life Cycle Management SoftwareChange Management Change and Transport System Transport Tools Transport Control Program tpEnd of SAP Web AS 640

220 Correcting Problems when Starting the SAP System

tp the transport control program automatically restarts the SAP system several times during theindividual phases If the startup attempt fails and the next step requires processing within the SAPsystem (such as a table conversion) then tp waits for this step to end without result You might thennot be able to start the SAP system during the upgrade

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started orstopped at this point Starting at the end of the log search upwards for the latest entry markedtpsapstop or tpsapstart

08142008 PUBLIC 3170

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 32: Troubleshooting and Administration Windows

2 Troubleshooting221 Correcting Problems when Copying SAP Programs

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on asuser DDIC enter the following command to stop any SAP processes that are running

3 Check whether all the processes of the SAP system have really been stopped To do this enter thefollowing command

4 Enter the following command to try to start the SAP system

If you cannot start the SAP systemmanually then this is usually due to changes in the SAP profile inthe MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programsin the KX_SWITCH_1 phase In both cases the increased demands on computer resources may havecaused the problems In this case try to run the SAP system with fewer dialog processes

1 Check whether the system is running Log on to the SAP system2 Use the Windows Task Manager to check if all if the SAP system processes were stopped when the

system was stoppedThe display must not contain the processes disp+work and msg_serverIf these processes do exist proceed as followsn Make sure that the processes do not belong to a second SAP system on this hostn Use the Windows Task Manager to end the processes

3 Attempt to start the SAP System manuallyIf you cannot start the systemmanually this is probably caused by changes to the SAP profile madein the phases MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG or by SAP programs being switchedin the KX_SWITCH_1 phase In both cases the increased demands made on computer resources mayhave caused the problems If this is the case try to run the SAP system with fewer dialog processes

4 If the work processes fail check the trace files in the directoryusrsapltSAPSIDgtltINSTANCEgtwork for any entriesIn particular monitor the files stderrxxx and dev_w0

221 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtsysexerun areswitchedDo not start the SAP system during this period otherwise the upgrade program cannot overwritethe old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgtIt is located in the log subdirectory of the upgrade directory

2 Repeat the phase or copy the program manually from the exe subdirectory of the upgradedirectory to the directory usrsapltSAPSIDgtsysexerun

3270 PUBLIC 08142008

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 33: Troubleshooting and Administration Windows

2 Troubleshooting222 Use of Kernel and Instance Numbers During the Upgrade

222 Use of Kernel and Instance Numbers During the Upgrade

During the upgrade the upgrade tools use different versions of the kernel and instance numbers forthe source target and shadow system This is done automatically and requires no user action Ifhowever in case of an error you need to log on to the shadow instance or to exchange the kernelyou must know which version to useIn the ABAP system the kernel version and instance numbers are used as follows

n The source release kernel is used until the system switch The validated kernel is used for theoriginal system between the system switch and the SAP kernel switch and for the shadow systemYou can either install the latest kernel after the upgrade or let SAPup install it for you in phaseKW_SWITCH_1

n During downtime the instance number of the shadow system is temporarily used for the originalsystem It is switched back to the original instance number at the end of downtime

Figure 1 Kernel and Instance Numbers During the Upgrade

223 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 9] solves your problem contact SAP SupportTo enable us to help you as quickly and efficiently as possible follow the procedure given here

ProcedureIf you encounter problems that are specific to the upgrade create an error message in SAP SupportPortal (httpservicesapcomsupport) and assign it to component BC-UPG Answer thefollowing questions and put these answers in your customer message

1 For which SAP component do you want to perform the upgrade2 Which release are you upgrading from Which release are you upgrading to

08142008 PUBLIC 3370

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 34: Troubleshooting and Administration Windows

2 Troubleshooting223 Providing SAP Support with Information

3 Which operating system version are you using4 What was the original release of your SAP system5 In which upgrade program phase does the error occur

This information is listed at the end of the of the SAPuplog file located in the upgrade directory6 Did you have problems with the SAP system before upgrading

Note

We can find the cause of the error more quickly if you set up an online connection to the SAPsystem

If the program aborts due to an Access violation and Dr Watson responds then add the last pages ofthe log file written by Dr Watson to your message The log file is called drwtsn32log and is locatedin your main Windows directory for instance CWINNTdrwtsn32logFor tips on the correct configuration of Dr Watson see SAP Notes 33772 and 130334If you are certain that the problem is not an upgrade-specific one but a product-specific one assignyour error message to the appropriate product-specific component The following table gives youinformation on the different components to which you can assign your message in SAP SupportPortal

Components for Error Messages

SAP Product Component

SAP Solution Manager SV-SMG

Index Management Server BC-SRV-TRX

OLTP R3 System BC-UPG

R3 Standalone Gateway BC-UPG

SAP Add-On BC-UPG-ADDON

SAP Supply Chain Management APO-BAS

SAP Business Connector BC-MID-BUS

SAP Business Information Warehouse BW-SYS

SAP Business-to-Business Procurement BBP-SAD

SAP Customer Relationship Managementn Communication Station andMobile Development

Workstationn CRM Servern Internet Pricing and Configurator (IPC)n Mobile Client Componentn SAP R3 SAP R3 Enterprise SAP ECC

n CRM-MW

n BC-MID-INT-SRVn CRM-MT-IU-SPEn CRM-WBT-IUn BC-UPG

SAP TREX Search Engine (SAP DrFuzzy SearchEngine)

BC-SRV-TRX

3470 PUBLIC 08142008

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 35: Troubleshooting and Administration Windows

2 Troubleshooting223 Providing SAP Support with Information

SAP Product Component

SAP Front End BC-INS

SAP Internet Transaction Server BC-FES-ITS

SAP Knowledge Management KM-KW

SAP Enterprise Core Component BC-UPG

SAP Strategic Enterprise Management BC-UPG-ADDON

SAP NetWeaver Application Server ABAP BC-UPG

SMART Installation BC-UPG

08142008 PUBLIC 3570

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 36: Troubleshooting and Administration Windows

This page is intentionally left blank

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 37: Troubleshooting and Administration Windows

3 Administration

3 Administration

This part of the document contains additional information on the various administrative tasks thatyou can or must perform before and during the SAP system upgrade

n Reducing Downtime [page 38]n Manual Selection of Parameters [page 41]n Determining Versions [page 48]n Setting the Environment of the SAP Kernel [page 50]n Creating Shares and Directories and Checking Authorizations [page 50]n Changing the Virtual MemoryPaging File Size [page 51]n Isolating the Central Instance [page 51]

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Extending Free Space in the DB2 for Linux UNIX and Windows Database [page 53]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Extending Free Space in the SAP MaxDB Database [page 54]End of MaxDB

n

Only valid for MS SQL Server

Extending Free Space in the MS SQL Server Database [page 54]End of MS SQL Server

n

Only valid for Oracle

Extending Free Space in the Oracle Database [page 54]End of Oracle

n

Only valid for IBM DB2 for Linux and UNIX and Windows

Changing the DB2 for Linux UNIX and Windows Database Recovery Mode [page 56]End of IBM DB2 for Linux and UNIX and Windows

n

Only valid for MaxDB

Changing the SAP MaxDB Database Recovery Mode [page 56]End of MaxDB

n

Only valid for MS SQL Server

Changing the MS SQL Server Database Recovery Mode [page 57]End of MS SQL Server

08142008 PUBLIC 3770

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 38: Troubleshooting and Administration Windows

3 Administration31 Reducing Downtime

n

Only valid for Oracle

Changing the Oracle Database Recovery Mode [page 57]End of Oracle

n

Only valid for Oracle

Standalone Database Server (Oracle) [page 58]End of Oracle

n Upgrade Directory [page 59]n Releasing and Confirming Open Repairs and Requests [page 60]n Sending a Message when User Action Is Required [page 62]n Using the ABAP Phase List for the Upgrade [page 62]

31 Reducing Downtime

The System Switch upgrade has been designed to reduce downtime to a minimum Thepreconfiguration modes for the shortest possible downtime are standard resource use and high resource use Inaddition to the preconfiguration mode there are other options to further reduce the downtime

Preconfiguration ModeTo reduce downtime we recommend that you first try the preconfiguration mode high resource use orstandard resource use This means that you run the shadow instance while your central instance is stillin production operation When you run these two instances in parallel there may be insufficientmemory on your central instance

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If so consider using a remote shadow instanceEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

If you are not able to run the shadow instance in parallel to the production instance you can use thepreconfiguration mode low resource use This way you get an upgrade model where the data is loadedduring uptime but the activation phase is executed during downtime

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Remote Shadow InstanceInstead of running the shadow instance on the central instance you can run it remotely [page 47] onone of your application servers During roadmap step Configuration you are asked if you want touse this optionIn this case the application server does not have to run on the same operating system as the centralinstance For more information see SAP Note 430318

3870 PUBLIC 08142008

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 39: Troubleshooting and Administration Windows

3 Administration31 Reducing Downtime

Caution

You cannot mix Windows and UNIX operating systems

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

HardwareFast hardware is key to speeding up the upgrade With faster hardware the overall runtime decreasesand therefore the downtime as wellSome phases benefit from a faster CPU and additional memory Other phases require fast disk IO

n CPUSeveral phases run parallel processes However as the number of parallel processes is usually notlarger than 8 more CPUs may thus not be exploited fully 4 CPUs with 800 MHz are faster than 8CPUs with 400 MHz for example

n RAMAdditional memory for the database and the SAP kernel can improve speed especially for phasesthat use the SAP system such as the activation phase or the XPRAS phase

n Disk IODuring the main import phases (EU_IMPORT SHADOW_IMPORT TABIM) a fast disk IO is the keyto reducing the upgrade runtime

BackupYou need to be able to restore the upgrade to the point when downtime began You can do this usingyour usual backup and archiving model You also need to make a backup of your database after theupgrade has finishedYou can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-basedmechanism or a hardware based mirror mechanism

ConfigurationYou can configure the upgrade by modifying the number of processes used

n Number of background processesThis is the key parameter for running ABAP reports in parallel Increasing this parameter speedsup phases like ACT_ltrelgt PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 doesusually not decrease the runtime

n Number of R3trans processesThis parameter affects the number of R3trans processes that tp starts during phasesSHADOW_IMPORT and TABIM A value larger than 8 does usually not decrease the runtime

n Number of load processesFor several databases the EU_IMPORT phases may run with parallel load processes if you use thepreconfiguration mode low resource use

Do not increase these parameters to values much larger than the number of CPUs of your system

08142008 PUBLIC 3970

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 40: Troubleshooting and Administration Windows

3 Administration31 Reducing Downtime

ClientsThe number of clients has a significant influence on the runtime During phases SHADOW_IMPORT andTABIM the data import for some client-specific tables needs to be cascaded into the different clientsThe import time therefore increases with the number of clientsThe XPRA phase especially the after-import methods also depends on the number of clientsIf you no longer need certain clients you should delete them before you start the upgrade programbecause the free space calculation depends on the number of clients

ArchivingIn some cases it is useful to archive some of the content of large tables If tables are converted duringthe upgrade the conversion time depends on the size of the table If you can decrease the size of atable that needs to be converted the downtime is reduced The tables converted during the upgradeare summarized in the upgrade analysis report RSUPGSUMThe duration of the ICNV and phase XPRAS_UPG also depends on the size of large tables

ICNVThe incremental table conversion transaction (ICNV) is provided only if you use the preconfigurationmodestandard resource use or high resource use The incremental table conversion enables you to start theconversion during uptime The upgrade procedure provides a list of tables for which you can usetransaction ICNV If the upgrade program finds these tables the upgrade stops and prompts you tocall transaction ICNV The downtime does not start until at least 90 of the data transfer has beencompleted Phase MODPROF_TRANS checks the progressAs the duration of the ICNV also depends on the size of large tables you should check if you canarchive data before the upgrade

ModificationsIf you have modified some tables in the source release you may need to convert them if you choose toreturn to the SAP standardThis may mean that you need to remove some fields or reduce a field length You may want toconsider keeping your modification to avoid such a conversion

ErrorsDuring a test upgrade most probably errors will occur Usually these errors increase the runtime anddowntime of the upgrade significantlyDuring the tests find out if necessary with the help of SAP Support how to prepare the SAP systemso that these errors do not occur again For example if the process fails in phase PARCONV_UPG dueto the fact that the tablespaces or containers are too small increase the free space by the amountof space you need to run the phase

4070 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 41: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parametersto tailor the upgrade to your specific needs In the following you can find a description of theparameters and their influence on the runtime of the upgrade

n Upgrade Strategy Parameter [page 41]n Database Archiving Parameter [page 44]n Background Process and Tool Parameters [page 46]n Shadow Instance Parameters [page 47]n Running the Shadow Instance Remotely [page 47]

321 Upgrade Strategy Parameter

The SAP upgrade technology offers two upgrade strategy parameters downtime-minimized andresource-minimized Choose the parameter that is best suited to your SAP system and to yourrequirements concerning system availability Your decision depends on two factors

n Maximum permitted downtimen System resources

Characteristics of Parameter Downtime-Minimized

n Parallel operation of production system and shadow systemn Higher demand on system resourcesn Shorter downtime

n Import of the substitution set into the shadow tables during production operationn Modification adjustment of the ABAP Dictionary objects during production operationn Activation and distribution during production operationn Production operation stops in phase DOWNCONF_TRANS (at the end of the Preprocessing roadmap step)

Characteristics of Parameter Resource-Minimized

n Operation of production and shadow system only possible independently of each othern Increased downtime

n No ICNV

n Production operation stops before import of substitution set into shadow tables (phaseDOWNCONF_R1 at the end of the Preprocessing roadmap step) or at the latest before the shadowinstance is started for first time (phase DOWNCONF_R2 at the end of the Preprocessing roadmap step)

Benefits of the System Switch Upgrade Procedure

If you choose the downtime-minimized strategy the System Switch Upgrade procedure offers you thefollowing benefits

08142008 PUBLIC 4170

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 42: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

n ABAP object modification adjustment during production operationThe modification adjustment of the ABAP Dictionary objects is performed before downtime Thisis possible since the complete version management is available in the shadow system

n ABAP object activation and distribution during production operationYou need to activate and distribute all ABAP Dictionary objects (including their dependentobjects) that Support Packages modify in the delivered release as well as objects that are modifiedor created by the customer Where a large number of included Support Packages or add-ons areconcerned or where systems have been modified greatly this procedure may take several hours

n Specific use of the incremental ABAP table conversion function (transaction ICNV)You can also increase the number of candidates for transaction ICNV since the amount and targetstructure of the tables can be calculated at the customer site Transaction ICNV can thereforebe used for tables modified by customers add-ons and Support Packages This is particularlynoticeable in the shorter downtime for upgrades that include one or more add-ons

Since these processes occur during production operation downtime is reduced considerably andsome phases during downtime are much shorter This mainly affects the phases PARCONV_UPG andTABIM_UPGOther benefits of the System Switch Upgrade for both upgrade strategy parameters include

n Use of target release tools for the upgradeTo upgrade an ABAP system from the source release structure to the target release structureactivation and distribution actions need to be specified and executed This is now done by tools ofthe target release which removes restrictions caused by using source release tools

n Extended shadow importThe shadow system is used to calculate the target release state of a table before downtime startsBecause the shadow tables are created in their final structure during production operation theamount of tables into which data can be imported in advance can be increased Until now this wasonly possible for new tables and substituted tables

Comparison of Upgrade Strategies

Strategy Advantages Disadvantages

Downtime-minimized n Short downtimen Medium amount of space

required to be able to recoverthe database

n Increased demand on systemresources due to paralleloperation of production andshadow system

n Offline backup required afterupgrade if archiving deactivatedat some stage

n Disk capacity for a possibledatabase recovery is monitored

Resource-minimized n No additional system resourcesduring upgrade

n Long downtime

4270 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 43: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

Strategy Advantages Disadvantages

n No additional spacerequirements to be able torecover the database

n Disk capacity for a possibledatabase recovery is notmonitored

n Offline backup required afterupgrade

The upgrade strategy parameter is one of the main factors in determining how much downtimeis involvedThe upgrade is divided into roadmap steps and phases The downtime of the SAP system starts in theDowntime roadmap step EU_IMPORT1 REQSTOPPROD and MODPROF_TRANS are important phases sincethey define the start of the Downtime roadmap step depending on the chosen upgrade and archivingstrategyThe course of the upgrade is identical in all strategies up to the EU_IMPORT1 phase For theresource-minimized strategy the Downtime roadmap step either begins in the EU_IMPORT1 phase or theREQSTOPPROD phase For the downtime-minimized strategy the Downtime roadmap step begins in theMODPROF_TRANS phaseThe following graphic shows the course of the upgrade for the various strategies It does not showthe differences in the duration of the upgrade

Figure 2 Course of the Upgrade

08142008 PUBLIC 4370

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 44: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

Upgrade Runtime

The following factors influence the total runtime of the upgrade program

n Import runtime for the substitution setn Languages installedn Number of clients

n Add-on software

n Hardware used

n Extensive customer developmentsn Modifications to standard SAP tables and componentsn Integration of Support Packages

Only valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

The upgrade runtime and the downtime depend on the upgrade strategy parameter you choosethe hardware and the amount of time required to create the database archives With strategydowntime-minimized the shadow system runs in parallel with the production system which increasesthe overall runtime but shortens downtime The size of your database only has a secondary rolein determining the runtime of the upgrade Your source release can influence the runtime anddowntime of the upgrade by up to approximately 25End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle

322 Database Archiving Parameter

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

The archiving strategy determines the time intervals in which database mechanisms save actions tothe database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and Windows

If the archiving mode is on you will receive the message LOG ARCHIVING is enabledEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

If the archiving mode is on you will receive the message Logging is switched onEnd of MaxDB

Only valid for MS SQL Server

If the archiving mode is on you will receive the message Database runs with recovery mode FullEnd of MS SQL Server

4470 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 45: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

Only valid for Oracle

If the archiving mode is on you will receive the message Database is operated in ARCHIVELOG

modeEnd of Oracle

Only valid for IBM DB2 for zOS

Caution

For DB2 for zOS it is not possible to deactivate archivingSo the phase you choose simply determines when the downtime of the ABAP upgrade starts

End of IBM DB2 for zOS

The upgrade program prompts you in the Configuration roadmap step to select when you want todeactivate archivingThe following options are available

Archiving Strategy and Upgrade Strategy

Archiving Strategy Downtime-Minimized Resource-Minimized

Archiving is activated during theentire upgrade

Possible Possible

Archiving is deactivated in theEU_IMPORT1 phase

‒ Recommended

Archiving is deactivated before youstart the shadow instance for thefirst time in the START_SHDI_FIRSTphase

‒ Recommended

Archiving is deactivated in theMODPROF_TRANS phase

Recommended ‒

Caution

Once you have deactivated archiving you can no longer use the SAP system in production operation

Note

The archiving strategies that are marked as ldquorecommendedrdquo ensure that you can run your SAPsystem in production mode as long as possible The archiving strategies that are marked as ldquopossiblerdquoare only useful in certain cases In the following only the ldquorecommendedrdquo archiving strategies aredescribed

At the selected time you are then prompted to deactivate archiving

08142008 PUBLIC 4570

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 46: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Caution

MCOD systems If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD) which means that multipleSAP systems are installed in your database you are not prompted about archiving Archiving isautomatically activated during the entire upgradeFor more information on MCOD systems see SAP Service Marketplace athttpservicesapcommcod

End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Sizes for comparing the archives up to the MODPROF_TRANS phase and to the end of the upgrade canbe found in section Quick Guide of the upgrade guide They can vary considerably depending on theamount of customer dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

323 Background Process and Tool Parameters

n Host name of the background serverThere is usually a background service available on the central instance You can check this withtransaction SM51However in larger systems the background service may be elsewhere to improve load distributionIn this case enter the host name and the name of the relevant application serverAlso make sure that the upgrade directory is mounted on the host with the background serviceand that the background server can process background jobs of class CThe server you select must be available for background operations round the clock Check theactive operation modes with transaction SM63 to find out if it satisfies this requirement

n Number of parallel processes used by R3trans during production operation (MAXIMUMUPTIMEPROCESSES)This is the number of background and activator processes used by R3trans that can run in thesystem during production operation We recommend a value of 1 which is the default value Ifyou have enough main memory you can use up to four processes

n Number of parallel import processes used by R3trans during downtime (R3TRANS PROCESSES)This is the number of parallel processes used by R3trans to import data into the database Werecommend three processes for machines with 512 MB (and greater) main memory 3 is alsothe default value Up to eight parallel import processes are possible for multiprocessor hostswith sufficient main memory

n Longest synchronization time of the buffers on all application servers (MAXIMUM SYNC TIME)

4670 PUBLIC 08142008

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 47: Troubleshooting and Administration Windows

3 Administration32 Manual Selection of Parameters

Usually 120 seconds is entered for the bufreftime parameter in the instance profiles of the servers

Caution

If you have installed multiple instances you must specify the largest value of all the profiles Theupgrade programmust wait for this length of time at certain points during the upgrade so that allthe instances are synchronized If the time entered is too short time intervals might occur inwhich users can make unchecked changes

n Upgrade strategy downtime-minimized or resource-minimizedn If you have selected only one R3load process Time for EU_IMPORT phasesn Phase for disabling archive moden Number of background processes

324 Shadow Instance Parameters

If you install the shadow instance locally using the upgrade program you have to enter an instancenumber that has not yet been used in your system landscape

Only valid for IBM DB2 for zOS

Note

The shadow instance cannot be run on a remote application server

End of IBM DB2 for zOS

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

Decide whether you want to operate the shadow instance on a different host For more informationsee Running the Shadow Instance Remotely [page 47]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle

325 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you candetermine another host for the shadow instance in this phaseIf you have chosen preconfiguration mode manual selection you are asked in step Configuration if you wantto run the shadow instance remotely If you have answered the question with Yes proceed as follows

Note

On the application server the DB client software may have to be updated

08142008 PUBLIC 4770

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 48: Troubleshooting and Administration Windows

3 Administration33 Determining Versions

Procedure

1 Enter the host name of the server for the shadow instance2 Determine the path of the upgrade directory for remote access from the application

server of the shadow instance For example enter the UNC path to the upgrade directoryltHOSTgtSHARE_PUT

3 Install a license for the shadow instancea) To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 949984 Continue with the upgrade

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Caution

If the shadow instance is not on the same server as the original system you have tomanually startthe instance in the START_SHDI_FIRST phase andmanually stop it in the STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Only valid for IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

Note

After you have stopped the shadow instance sometimes the sapstartsrv keeps running Youneed to stop it with the following commandsapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle

33 Determining Versions

Determining the Operating System VersionChoose Windows Explorer Help About Windows

Only valid for IBM DB2 for Linux and UNIX and Windows

Determining the Database Version for DB2 for Linux UNIX and WindowsOpen a DB2‒CLP window and enter the following commanddb2level

For version 9 the value SQL09012 is displayedEnd of IBM DB2 for Linux and UNIX and Windows

4870 PUBLIC 08142008

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 49: Troubleshooting and Administration Windows

3 Administration33 Determining Versions

Only valid for MaxDB

Determining the Database Version for SAP MaxDBEnter the following operating system commanddbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB

Only valid for MS SQL Server

Determining the Database Version for MS SQL ServerExecute the following command in the MS SQL Server Query Analyzerselect version

The first line of the output displays the MS SQL server release numberEnd of MS SQL Server

Only valid for Oracle

Determining the Database Version for OracleEnter the following SQL statementSELECT BANNER FROM V$VERSION

The first line of the display contains the Oracle server releaseEnd of Oracle

Determining the SAP System ReleaseTo find out what SAP source release you have choose System Status in your SAP systemThe release appears in the SAP Release field

Determining the SAP Kernel VersionTo determine the version of the SAP kernel you are using and its patch level proceed as follows

1 In the SAP system choose Administration System Administration Monitor System MonitoringServer

2 Select a server and choose Release Notes

Determining the Date of R3transCall R3trans without optionsThe program displays the date and the version number

Determining the Version of tpCall tp with the following commandtp ndashV

The last line displays the highest patch level

08142008 PUBLIC 4970

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 50: Troubleshooting and Administration Windows

3 Administration34 Setting the Environment of the SAP Kernel

34 Setting the Environment of the SAP Kernel

Setting the Environment of the SAP KernelThe runtime environment of the SAP kernel consists of the following

n system environment variables set when the system is startedn environment variables listed in Registry under the key HKEY_LOCAL_ MACHINE

SOFTWARE SAP ltSAPSIDgt Environment These environment variables correspond to the user environment of the user entered in theRegistry under the key HKEY_LOCAL_ MACHINE SOFTWARE SAP ltSAPSIDgtAdmUser Each time the SAP System is started the user-specific environment for this user is copied to thesubkey Environment so that manual changes in this subkey do not have any effects

35 Creating Shares and Directories and CheckingAuthorizations

You must check the authorizations on a shared directory or create a share

ProcedureCreating a share

1 Open the Windows Explorer and position the cursor on directory that you want to share2 Choose File Properties Sharing Shared As

Checking the permissions of a share

1 In the Windows Explorer position the cursor on directory that you have released2 Choose File Properties

In the Share Name field you can see all shares that are set for this directory Select your sharename and choose Permissions

Creating a directory

1 In the Windows Explorer position the cursor on directory under which you want to createa subdirectory

2 Choose File New Folder 3 Replace the name New Folder of new subdirectory with the new directory name

Checking the permissions for a directory

1 In the Windows Explorer position the cursor on directory that you want to check for a permission2 Choose File Properties

Displaying attributes of an executable

5070 PUBLIC 08142008

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 51: Troubleshooting and Administration Windows

3 Administration36 Changing the Virtual MemoryPaging File Size

1 In the Windows Explorer position the cursor on file where you want to check or set the attributes2 Choose File Properties

36 Changing the Virtual MemoryPaging File Size

n For Windows 2000 choose Start Settings Control Panel System Advanced PerformanceOptions Virtual Memory Change

n For Windows 2003 choose Start Settings Control Panel System Advanced Performance SettingsAdvanced Virtual Memory Change

37 Isolating the Central Instance

You need to isolate the central instance so that only the upgrade program can work with the systemduring downtime This means that you can use the central instance exclusively for the upgrade Theupgrade program asks you to isolate the central instance when downtime beginsDuring downtime all users must have logged off the system You can use transaction SM02 toinform the users logged on to the system

Procedure

1 Make sure that no job is scheduled in the NT Scheduler that affects the SAP system such asstarting and stopping the SAP system backing up the database or similar actionsThis could impair the full control of the upgrade program over the SAP system

2

Only valid for SAP R3 31I

Delete scheduled jobs in transaction DB13End of SAP R3 31I

3 As of SAP Basis Release 40B transaction DB13 uses different internal job formats Since transactionDB13 can no longer read the old job formats after the upgrade you must delete all jobs scheduledfor the futureProceed as followsa) Call transaction DB13b) Double-click a day header to see its job overviewc) Position the cursor on the job that you want to delete and choose Delete d) Repeat steps b and c until you have deleted all jobs that have not yet been executed

4

Only valid for SAP R3 31ISAP R3 40B

No background job other than RDDIMPDP may be active during the upgradeYou must cancel the release of all background jobs except RDDIMPDP before the upgrade in allclients To do this proceed as follows for each client

08142008 PUBLIC 5170

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 52: Troubleshooting and Administration Windows

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

a) Log on to the client as user DDICb) Call transaction SM37c) Determine the jobs involved

Fill in the necessary information on the screen Select background jobs as described in theexample below In the Start date field make sure that the from date is in the past The Todate must be far enough in the future to include all the background jobs that could becomeactive during the upgrade

d) Choose Execute e) Cancel the release by choosing Job Schedule job Cancelf) Special feature in client 000

The background job RDDIMPDPmust be scheduled in client 000 If it is not schedule it byexecuting the report RDDNEWPP (transaction SE38)

The upgrade is not affected if RDDIMPDP is also scheduled in other clientsEnd of SAP R3 31ISAP R3 40B

5 Make sure that no change of operationmode is defined on the central instance during the upgradeIf this is the case in normal operation call transaction SM63 to either choose a single operationmode for all time spans or delete all the assignments

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps inthe upgrade guide when the message Update records still exist - Please process appears

7 Shut down all application servers if necessary (secondary SAP instances)8 Make sure that you can recover the database to its current state9 If you have chosen strategy downtime-minimized back up the upgrade directory now

If a hardware problem occurs during downtime you may need to reset the upgrade to thestate it had when the SAP system was isolated So that the upgrade program has the correctcontrol information the upgrade directory must have the same state as at the beginning of theMODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the databaseagainst remote access Contact the database administrator

Caution

Make sure that no transport requests are imported into the system during downtime Otherwiseyou may lose data For example by manually importing requests for the automatic adjustmentyou may lose all your modifications to the SAP system

5270 PUBLIC 08142008

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 53: Troubleshooting and Administration Windows

3 Administration38 Extending Free Space in the DB2 for Linux UNIX and Windows Database

Only valid for IBM DB2 for Linux and UNIX and Windows

38 Extending Free Space in the DB2 for Linux UNIX andWindows Database

Extend existing tablespaces and create new tablespaces as requested by the upgrade programTo create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the upgrade program (see the CHECKSLOG file)To create or extend tablespaces you should use the DB2 Command Line Processor TemplateDB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)Alternatively you can use the DB2 DB6COCKPITWith DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to AutoextendDMS tablespaces instead of extending the tablespace manually You can do this using the commanddb2 alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or highernew tablespaces are automatically created as Autoextend DMS tablespaces when DB6TBSXTCLP is used

Recommendation

When you extend tablespaces use the option of extending existing tablespace containers This meansthat the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 forLinux UNIX and Windows

PrerequisitesFor performance reasons you must consider the following restrictions when you create the newtablespaces (in the order they are listed)

n Different containers of a tablespace must be located on different (physical) disksn PSAPESltRELgtD and PSAPELltRELgtD or ltSAPSIDgtESltRelgtD and ltSAPSIDgtELltRelgtD should not

be on the same disk

Procedure

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

08142008 PUBLIC 5370

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 54: Troubleshooting and Administration Windows

3 Administration39 Extending Free Space in the SAP MaxDB Database

Tablespace Extensions for DB2 for Linux UNIX and Windows

For a system with old layout For a system with new layout

PSAPESltRELgtD ltSAPSIDgtESltRelgtD

PSAPESltRELgtI ltSAPSIDgtESltRelgtI

PSAPELltRELgtD ltSAPSIDgtELltRelgtD

PSAPELltRELgtI ltSAPSIDgtELltRelgtI

where ltRelgt stands for the current target release

End of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

39 Extending Free Space in the SAP MaxDB Database

To extend your database use the database tools to add new data volumes For a precise descriptionsee SAP Note 34690End of MaxDB

Only valid for MS SQL Server

310 Extending Free Space in the MS SQL Server Database

If you are asked to extend the database it may be due to the following reasons

n The default option Automatically grow file is not activen There is not enough disk space on the drives where the SQL Server data files are locatedn The maximum size of the data files for the Automatically grow file option is restricted

Extend the available disk space by at least the values determined by the upgrade programEnd of MS SQL Server

Only valid for Oracle

311 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the upgrade program

5470 PUBLIC 08142008

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 55: Troubleshooting and Administration Windows

3 Administration311 Extending Free Space in the Oracle Database

Caution

If you use tablespaces where the AUTOEXTEND feature is turned on the upgrade program freespace check includes this in its calculation However youmay still have to create the new tablespaces

Note

Avoid fragmenting the database too stronglyBe generous when you extend existing tablespacesChoose a low degree of fragmentation when you create tablespaces

PrerequisitesFor performance reasons you must take the following restrictions into consideration when creatingthe new tablespaces

n Index tablespaces and data tablespaces that belong together must not be on the same disk andmust not be in the same sapdata directory

n PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

Recommendation

We recommend the following combinationDisk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

ProcedureBRSPACE proposes other values for the extension than those specified in the list You can overwritethese values with the minimum values from the upgrade programProceed as follows

1 Extend the listed tablespaces by at least the specified values2 Create the new tablespaces as prompted by the upgrade program This applies to the following

tablespaces in a System Switch Upgrade

For a system with old layout For a system with new layout

PSAPESltRelgtD

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

PSAPltSAPSIDgtltRelgt

where ltRelgt stands for the current target release

08142008 PUBLIC 5570

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 56: Troubleshooting and Administration Windows

3 Administration312 Changing the DB2 for Linux UNIX and Windows Database Recovery Mode

Caution

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of thesubstitution set terminatesIf you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total size ofthe tablespace where n is the number of fragments

End of Oracle

Only valid for IBM DB2 for Linux and UNIX and Windows

312 Changing the DB2 for Linux UNIX and WindowsDatabase Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database

Recommendation

If the last full backup was a long time ago and the number of archives collected up to that point islarge we recommend that you make a full backup before you disable log archiving

ProcedureProceed as described in the document IBM DB2 for Linux UNIX and Windows New Log File ManagementEnd of IBM DB2 for Linux and UNIX and Windows

Only valid for MaxDB

313 Changing the SAP MaxDB Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

Procedure

n At the start of downtimeThe upgrade program automatically deactivates archiving

n At the end of downtimeArchiving can only be reactivated by making a full backup in operating mode ADMIN

5670 PUBLIC 08142008

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 57: Troubleshooting and Administration Windows

3 Administration314 Changing the MS SQL Server Database Recovery Mode

That is why the upgrade can be continued only after you have made a backup of the databaseif archiving is deactivated

End of MaxDB

Only valid for MS SQL Server

314 Changing the MS SQL Server Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtimeDuring the upgrade you have to set the recovery model to Simple and then later back to Full

ProcedureTo do this use the SQL Server Enterprise Manager

1 Select your ltSAPSIDgt database by clicking it2 Click right mouse key and choose Properties 3 Choose Options and make necessary changes

End of MS SQL Server

Only valid for Oracle

315 Changing the Oracle Database Recovery Mode

You need to change the recovery mode of the database at the beginning and end of downtime

PrerequisitesMake sure that you can recover the current state of the database before you deactivate databasearchiving

Recommendation

If the last complete database backup was a long time ago and the number of archives collected upto that point is large SAP recommends that you make a complete database backup before youdeactivate archiving

ProcedureOn the database server deactivate archiving as follows

1 Log on as user ltsapsidgtadm2 Start program BRSPACE using the following command

brspace [-c force] -f dbalter -a noarchlog -f

08142008 PUBLIC 5770

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 58: Troubleshooting and Administration Windows

3 Administration316 Standalone Database Server (Oracle)

In the same way as when you deactivate archiving you can reactivate it as user ltsapsidgtadm withprogram BRSPACE using the following commandbrspace [-c force] -f dbalter -a archlog -f

Note

You can call BRSPACE for information about the current status of redo log archiving using thefollowing commandbrspace -c force -f dbshow -c dbstate

End of Oracle

Only valid for Oracle

316 Standalone Database Server (Oracle)

The following database commands are used together with mode ARCHIVELOG

1 Check the mode ARCHIVELOG as user ORAltSAPSIDgtEnter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt archive log list

SQLgt exit

If NOARCHIVELOG is displayed then mode ARCHIVELOG has been deactivated2 Deactivate mode ARCHIVELOG

To do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database noarchivelog

SQLgt alter database open

SQLgt exit

3 Activate mode ARCHIVELOGTo do this the database must be shut down Enter the following commands in SQLPLUSSQLgt connect as sysdba

SQLgt startup mount

SQLgt alter database archivelog

SQLgt alter database open

SQLgt exit

End of Oracle

5870 PUBLIC 08142008

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 59: Troubleshooting and Administration Windows

3 Administration317 Upgrade Directory

317 Upgrade Directory

The SAP system is upgraded using the upgrade directory which is divided into subdirectories Boththe upgrade directory and the subdirectories can be a softlinks to other physical directoriesThe upgrade program creates the upgrade directory on the host with the central instance and copiesdata and programs into this directoryThe default path of the upgrade directory isusrsapltSAPSIDgtupg

The upgrade directory is divided into the following subdirectories

n sdt

Contains the SL controller

n jvm

Depending on your operating system and database this directory contains the Java VirtualMachine delivered by SAP

n STARTUP

Contains the startup files with which you can restart the upgrade program

n abap

l log

The central log directory contains most information on the upgrade All log files generatedduring the upgrade and related to it are collected here

l tmp

The tmp directory is used for temporary storage R3trans also stores its log files there beforethey are handled by tp Some jobs which run directly in the SAP system also generate outputfiles in the tmp directory The most important of these output files include the distributionprogram the activation program and the conversion program which are started by SAPupseveral times during the upgrade At the end of each phase the directory only contains thefollowing files ECO EClt0-9gt files or dev_evt dev_rfc trace files

l data cofilesThe data and cofiles directories contains files which are imported by R3trans during theupgrade They also contain the files for the language import as well as the data files of SupportPackages and add-ons included in the upgrade

l bin

Contains SAPup its libraries and control files The control files of SAPup are always updatedautomatically The data they contain is critical for the smooth operation of the upgrade toolsIt is maintained exclusively by SAPup

l exchange

The files for the R3load import during the phases EU_IMPORTltxgt VIEWIMPltxgt and LOADCREltxgt

reside in this directory It is maintained exclusively by SAPup

l ltSAPSIDgt

Contains the installation of the shadow instance

08142008 PUBLIC 5970

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 60: Troubleshooting and Administration Windows

3 Administration318 Releasing and Confirming Open Repairs and Requests

l exe

Contains the target release SAP kernel that has been validated by SAP for the upgrade

l exenew

Contains the files for the latest SAP kernel if available

l htdoc

Contains ABAP phase documentation

l mig

This subdirectory is needed for the synchronization of SAPup with SAPJup

l ua

Contains the SDT server

l save

Contains files saved [external document] during the upgrade by SAPup that can be used forfollow-up upgrades for example the shadow system profile and results from phase BIND_PATCH

l platform

Contains the SAP kernel files for your dialog instances if they run on a different platformthan the central instance

318 Releasing and Confirming Open Repairs and Requests

Before you start the upgrade you must release and confirm all the open repairs and requests thatconflict with the SAP delivery The upgrade program determines a list of these repairs and requests Ifyou ignore open repairs you could lose modifications

Procedure

Only valid for SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web

AS 610SAP Web AS 620SAP Web AS 640

1 Log on to the SAP system as the owner of the open repair You can find the user names of theowners in CHECKSLOG

Note

If you cannot log on with a specific user ID you can change the owner of the repair in transactionSE09 as followsa) In the list of open repairs position the cursor on the repairb) Choose Change ownerTo be able to change an owner in transaction SE09 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

2 Call transaction SE093 Choose Requesttask Find requests

6070 PUBLIC 08142008

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 61: Troubleshooting and Administration Windows

3 Administration318 Releasing and Confirming Open Repairs and Requests

4 For Request type only select Repair5 For Request status select everything except Released6 Choose Execute

A list of all open repairs for the selected user appears7 Position the cursor on the request that you want to release8 Choose Release9 Release the request to which the repair is assigned

End of SAP Basis 46CSAP Basis 46DSAP NetWeaver 70SAP R3 40BSAP R3 45BSAP R3 46BSAP Web AS 610SAP

Web AS 620SAP Web AS 640

Only valid for SAP R3 31I

1 Log on to the SAP system as the owner of an open repair You can find the user names of theowners in CHECKSLOG

2 Call transaction SE013 Choose Find

Note

You can also release the repairs from the Workbench Organizer (transaction SE09)

4 Make sure that the field User name contains the correct name5 In the Type field enter REPA

Do not change any other default values6 Choose Execute

A list of all the open repairs for this owner appears7 Select the repair that you want to release8 Choose Repair Release repair 9 If the repair is assigned to a superordinate transport request this transport request must also

be released

Note

If you are cannot log on with a specific user ID you can change the owner of the repair intransaction SE01 as followsa) In the list of open repairs position the cursor on the repairb) Choose Edit Change owner To be able to change an owner in transaction SE01 you need project authorization for theWorkbench Organizer (S_CTS_PROJEC)

End of SAP R3 31I

08142008 PUBLIC 6170

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 62: Troubleshooting and Administration Windows

3 Administration319 Sending a Message when User Action Is Required

319 Sending a Message when User Action Is Required

If a user entry is not made within 60 seconds during the upgrade you can send a message to anothercomputer

PrerequisitesAmessage informing you that the upgrade has stopped can be sent from the upgrade host if

n You are not permanently monitoring the upgrade during its runtime but still want to avoidlong delays

n Your workstation host can be reached from the upgrade host with the NETBIOS protocoln You have started the workstation service on the upgrade hostn You have started the messenger service on your workstation host

ProcedureCall SAPup with the option messagehost=lthostgt As lthostgt specify the workstation host onwhich you want to be informed about the upgrade delay SAPup sends a dialog box to the specifiedworkstation host if no user entries are made for 60 seconds and SAPup is waiting for an entry

320 Using the ABAP Phase List for the Upgrade

In the Extraction roadmap step the upgrade program creates a phase list that is specific for yourupgrade The phase list contains all ABAP phases of the upgrade in the right order It consists of thefollowing parts

n The Phase List Table of Contents contains a list of all the phases with links to the correspondingdescription in the Phase List part

n The Phase List part contains a table with all phases and their descriptionThe upgrade program stops at the end of each roadmap step It also stops for user actions if thereare errors or if you manually stop the upgrade at a particular phase The table contains thefollowing columnsl Phase

Table fields of phases that run while the shadow system is in operation are indicated by a graybackground

l Upgrade Program ActionsGives a brief explanation of the tool actions Constraints are printed in bold

l DurationIndicates the percentage of the total runtime of the upgrade program required for this phaseThe runtime depends on the following criteria

uAmount of customer data

uNumber of SAP components implemented

6270 PUBLIC 08142008

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 63: Troubleshooting and Administration Windows

3 Administration320 Using the ABAP Phase List for the Upgrade

uQuantity and type of modifications and customer developments involved

uNumber of clients

uNumber of included packagesThe duration of some of the phases depends on the gap between the source and target releaseof the SAP system The smaller the gap all the shorter the duration of the phase

l Log FilesLists the log files that are generated by the upgrade program for each phase

l User ActionsIf there is no entry in this column the upgrade program does not require an operator at thispoint Otherwise the upgrade program prompts you to make the entries described

Some phases have comments next to them in the various columns These are as follows

Comment Meaning

(var) The runtime of the phase depends on your dataThe percentage duration of these phases can be verydifferent in your upgrade

(log) Not all logs can be included in the Log Files columnFor more information see Upgrade Logs [page 12]

ProcedureYou can open the phase list from the entry page of the upgrade program

08142008 PUBLIC 6370

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 64: Troubleshooting and Administration Windows

This page is intentionally left blank

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 65: Troubleshooting and Administration Windows

4 Related SAP Notes

4 Related SAP Notes

The following table lists all SAP Notes that are mentioned in this document

SAP Note Number Description Area

871455 Performance When AccessingDBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREPCNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadowinstance

General upgrade

177680 Correcting conversion problems inthe PARCONV_UPG phase

General upgrade

122597 Ignore errors in the XPRAS_UPGphase

General upgrade

33772 Configuring Dr Watson Correctly System administration troubleshooting

130334 Windows SAP requests crash dumpof an SAP process

System administration troubleshooting

430318 Shadow instance on anotheroperating system

General upgrade

29972 Instance numbers in a distributedsystem

General upgrade

94998 Requesting a license key for asystem

General upgrade

34690 Add Devspace under SAP DB SAPMaxDB

SAP MaxDB-specific

08142008 PUBLIC 6570

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 66: Troubleshooting and Administration Windows

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

6670 PUBLIC 08142008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 67: Troubleshooting and Administration Windows

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendorsMicrosoft Windows Excel Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 System z9 z10z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise ServerPowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipesBladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIXIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2007-12-10 (V72) XSL-FO V51 Gamma and XSLT processor SAXON 652from Michael Kay (httpsaxonsfnet) XSLT version 1

08142008 PUBLIC 6770

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 68: Troubleshooting and Administration Windows

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

6870 PUBLIC 08142008

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 69: Troubleshooting and Administration Windows

This page is intentionally left blank

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice

Page 70: Troubleshooting and Administration Windows

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may bechanged without prior notice