011000358700000065622009 e

Troubleshooting and AdministrationFor Installations Using SAPehpi

For ABAP UNIX

Target Audience System Administrators Technology Consultants

CUSTOMERDocument version 13 ndash 2010-06-22

Document History

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

Version Date Description

10 2008-09-11 First version ndash no changes

11 2009-10-02 Information about trouble ticket and changing DDIC password added

12 2010-04-15 Information added about troubleshooting in phases DBCLONE and VALCHK_INI

Several minor changes

13 2010-06-22 Section Enhancement Package Installation Directory moved to SAP Enhancement Package Installation Guide

256 CUSTOMER 2010-06-22

Table of Contents

Chapter 1 Accessing Documentation 5

Chapter 2 Troubleshooting 7

21 Error Handling for ABAP 8

22 Installation Logs 11

23 Evaluating the ELG Log Files 13

24 Accelerating the Runtime of Certain Phases 15

25 Correcting Errors in the HIAV_CHK Phase 16

26 Correcting Entries Made in the INITPUT Phase 16

27 Correcting Errors in the DBCHK Phase 16

28 Correcting Errors in the BATCHCHK Phase 17

29 Correcting Errors in the INTCHK and INTCHK_SW Phases 17

210 Troubleshooting in the DBCLONE Phase 18

211 Correcting Errors in the START_SHDI_FIRST Phase 19

212 Correcting Errors in the JOB Phases 19

213 Cleaning Up Terminated Conversions in the DB Conversion

Phases 20

214 Correcting Errors in the TRBATCHK_XT Phase 22

215 Correcting Errors in the ACT_UPG Phase 23

216 Correcting Conversion Errors in the PARCONV Phase 24

217 Correcting Errors in the XPRAS Phase 24

218 Correcting Errors in the VALCHK_INI Phase 27

219 Running SAPehpi Process After the Installation 27

220 Restarting the Installation GUI 27

221 Preparing the Restart of the Installation After a System Failure 27

222 Correcting Problems when Processing ABAP Steps 28

223 Correcting Problems when Starting the SAP System 29

224 Correcting Problems with Starting the Shadow Instance 30

225 Correcting Problems when Copying SAP Programs 30

226 Use of Kernel and Instance Numbers During the Installation

Process 30

2010-06-22 CUSTOMER 356

227 Providing SAP Support with Information 31

Chapter 3 Administration 33

31 Reducing Downtime 34

32 Manual Selection of Parameters 35

321 Database Archiving Parameter 36

322 Background Process and Tool Parameters 37

323 Running the Shadow Instance Remotely 38

324 Shadow Instance Parameters 39

325 SGEN Execution Modes 39

33 Changing the DDIC Password 40

34 Incremental Table Conversion 40

35 Determining Versions 42

36 Isolating the Central Instance 43

37 Extending Free Space in the DB2 for Linux UNIX and Windows

Database 45

38 Extending Free Space in the SAP MaxDB Database 46

39 Extending Free Space in the Oracle Database 46

310 Changing the DB2 for Linux UNIX and Windows Database Recovery

Mode 48

311 Changing the SAP MaxDB Database Recovery Mode 48

312 Changing the Oracle Database Recovery Mode 48

313 Releasing and Confirming Open Repairs and Requests 49

314 Using the ABAP Phase List for the Enhancement Package

Installation 50

Chapter 4 Related SAP Notes 53

456 CUSTOMER 2010-06-22

1 Accessing Documentation

There are different ways to access the documentation

SAP Help Portal

You can access the SAP NetWeaver Library and the SAP Library for your application for all product

releases that are in maintenance on SAP Help Portal

Local installation of the SAP Library

Troubleshooting and administration documentation

The documentation is included in the installation program

Procedure

SAP Help Portal

You can find the SAP Library for SAP NetWeaver 70 including enhancement package ltxgt on SAP Help

Portal at httphelpsapcomnw70 SAP NetWeaver 70 including Enhancement Package ltxgt SAP

NetWeaver 70 Library (including Enhancement Package ltxgt) ltLanguagegt

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

SAP ERP Central Component

To access the SAP Library for other Business Suite applications choose httphelpsapcom SAP

Business Suite ltYour applicationgt

Troubleshooting and Administration Documentation

You can access the troubleshooting and administration documentation as follows

From a link on the enhancement package installation GUI Proceed as follows

1 If it is not running yet start the installation program

2 On page httplthost namegt4239 choose ABAP documentation

3 Choose Troubleshooting and Administration for Systems Running on ltplatformgt

From file Troubleshooting_and_Administration_UNIXpdf in directory ltinstallation

directorygtabaphtdoc

From SAP Service Marketplace at httpservicesapcominstguides under the same path

where this installation guide is available

2010-06-22 CUSTOMER 556

This page is left blank for documents that are printed on both sides

2 Troubleshooting

This part of the document contains additional information about how to proceed when you want to

correct known problems that have occurred during the enhancement package installation

NOTE

In the following some information is related to phases As long as the installation program runs

the phase name is displayed on the program tool tab page

If the installation program displays a dialog box and you need further information about the

required input you can identify the phase you are currently in by using the

SAPehpiConsolelog

This log file is located at EHPIabaplog

Error Handling for ABAP [page 8]

Logs

Installation Logs [page 11]

Evaluating the ELG Log Files [page 13]

Correcting errors after phases

Accelerating the Runtime of Certain Phases [page 15]

Correcting Errors in the HIAV_CHK Phase [page 16]

Correcting Entries Made in the INITPUT Phase [page 16]

Correcting Errors in the DBCHK Phase [page 16]

Correcting Errors in the BATCHCHK Phase [page 17]

Correcting Errors in the INTCHK and INTCHK_SW Phases [page 17]

Troubleshooting in the DBCLONE Phase [page 18]

Correcting Errors in the START_SHDI_FIRST Phase [page 19]

Correcting Errors in the JOB Phases [page 19]

Cleaning Up Terminated Conversions in the DB Conversion Phases [page 20]

Correcting Errors in the TRBATCHK_XT Phase [page 22]

Correcting Errors in the ACT_UPG Phase [page 23]

Correcting Conversion Errors in the PARCONV Phase [page 24]

Correcting Errors in the XPRAS Phase [page 24]

Correcting Errors in the VALCHK_INI Phase [page 27]

Running SAPehpi Process After the Installation [page 27]

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Correcting Problems when Starting the Shadow Instance [page 30]

Restarting the Installation GUI [page 27]

Preparing the Restart of the Installation After a System Failure [page 27]

Correcting Problems when Processing ABAP Steps [page 28]

Correcting Problems when Starting the SAP System [page 29]

Correcting Problems when Copying SAP Programs [page 30]

Use of Kernel and Instance Numbers During the Installation Process [page 30]

Providing SAP Support with Information [page 31]

21 Error Handling for ABAP

If the installation program reports an error during the installation it is essential that you find out what

caused this error before you continue with the installation

Tool Reaction

The installation program reacts on errors in different ways

The phase in which the error occurs is interrupted There is an error message on the screen and

in the corresponding log file [page 11] and a trouble ticket is created

The phase in which the error occurs continues but writes an error message into the corresponding

log file

The tool aborts

In rare cases the installation program waits for processes (tp background jobs and so on) which

have terminated or cannot be started In this case the current phase has very long runtimes

Error Analysis

Help in the Enhancement Package Installation Program

The installation program provides help for many known errors

Trouble Ticket

As soon as the installation program writes an error message to the log file it also creates a trouble ticket

The trouble ticket mentions the phase in which the error occurred and various system parameters In

addition an archive is created that contains all the relevant log files

You can find the SAPehpi_troubleticketlog and SAPehpi_troubleticket_logssar files in the

ltinstallation directorygtabaplog directory

Note that these files are overwritten as soon as a new error occurs

If you cannot solve the cause of the error yourself create an error message in SAP Support Portal [page 31]

and attach the SAPehpi_troubleticketlog and SAPehpi_troubleticket_logssar files

File dev_SAPehpi

The installation tool can abort due to internal program errors An error message appears on the user

interface In some cases the installation tool creates a stack trace You can find it in file dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

either in subdirectory tmp of the abap subdirectory of the enhancement package installation directory

or directly in the enhancement package installation directory

If the error persists after repeating a phase open a customer message and include the stack trace The

stack trace speeds up processing of the customer message

If you can continue the installation after a restart open a customer message anyway and include the

stack trace This helps SAP fix the tool error for future versions of the installation tool

Log Files

ELG Log Files

Provided that an ELG file [page 13] was generated at the end of the phase that terminated this file

provides helpful additional information about the error(s) that occurred during the phase Check

the ELG file according to the following criteria

No errors have occurred if the log contains a return code less than eight at the end of a step

and there are no error messages for this step

Errors have occurred if the return code is eight or higher and there are error messages

preceding it Analyze the error using the detailed log file

If a return code is equal to or greater than 12 or is missing entirely tp or a program called by

tp has terminated You can determine the termination point from the last line of the SLOG

log file If tp or R3trans has terminated you must analyze the last log file written

The following commands show a chronological list of the files in the log directories

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

In the ELG file the heading of each phase step displays the name of a log file that contains more

detailed information about the error

The detailed log files are stored in subdirectory log of the abap subdirectory of the installation

directory

Background Jobs

The reasons for terminated background jobs are either a lack of resources or program errors The job

log records the processing of background jobs All background job steps executed are listed in the job

log with their exit statuses If a background job is terminated you can obtain further information about

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 instance

instead of the central instance

2 Call transaction SM37 as user DDIC

3 Enter as the job name and specify the job conditions (for or after event enter )

2 Troubleshooting

2010-06-22 CUSTOMER 956

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 to

the terminated step

6 To display the job log file double-click the terminated job

For 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 that has

terminated 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 states

occurring during operation All irregularities such as a lack of resources or database errors during

operation are collected here The system log is administered by the SAP system and is available in the

file system as a non-readable file You use transaction SM21 to display the system log

Since the enhancement package installation is always performed by user DDIC it is mainly the system

log entries for this user that are relevant for error analysis The installation program itself does not

know about the system log

To analyze the system log proceed as follows

2 Choose Reread system log

Make sure that you enter the correct period so that only those entries are displayed which

correspond to the time when the terminated phase ran

3 Look for entries for user DDIC

4 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 instance

logs During the installation process you can find these logs in the current working directory of your

SAP instance as follows

1 Open the current working directory of your central instance

EHPIabapltSAPSIDgtDVEBMGSltshadow instance nogtwork

2 Find out which log files have been written

To do this you can use command ls -ltr

3 Examine the log files generated last for errors that may be related to the installation

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 or

incorrect profile parameters may have caused the phase to terminate

2 Troubleshooting

1056 CUSTOMER 2010-06-22

22 Installation Logs

The installation program logs all actions in log files You can use these log files to monitor the

enhancement package installation Unless otherwise specified below the log files are stored in

subdirectory log of the abap subdirectory of the installation directory If you encounter any errors

you can analyze them to help you find a solution

Features

SAPehpichklog and SAPehpilog

The installation program records all actions on the ABAP system in the log files SAPehpichklog (during

the preparation roadmap steps) and SAPehpilog (during the installation roadmap steps) These log

files provide you with a general overview of the status of the installation They contain information

about all phases performed up to this point the number of reruns runtimes final status and so on

SAPehpichklog and SAPehpilog are updated by the installation program only

Log Files Written by tp

SLOGltRelgt

The ABAP program tp lists all its steps in log file SLOGltrelgt It also writes additional detailed logs for

each step

A simple method of monitoring the progress of all tp-driven phases is to use tail to monitor the

SLOG log To do this open another terminal window and enter the following command

tail -f EHPIabaplogSLOGltrelgt

Each tp-driven phase is divided up into a number of different steps whose start and end times are noted

in the SLOG log The start and end of a phase are indicated by the lines START put and STOP put The

section in the SLOG log relating to the ACT_UPG phase looks like this

Section of SLOG Log Relating to the ACT_ltRelgt Phase

START put PS1 20010307182423 ps1adm ds0007

INFO event SAP_IMPORT_START triggered successfully

START SET STOPMARK PS1 20010307182423 ps1adm ds0007

INFO Buffer saved as usrsapltsapsidgtupg_ps1bufferPS1SAV

STOP SET STOPMARK PS1 20010307182423 ps1adm ds0007

LIST put PS1 (33|

START tplock_eu PS1 ( 20010307182423 ps1adm ds0007

STOP tplock_eu PS1 ( 20010307182423 ps1adm ds0007

START tpsapstart PS1 3 20010307182423 ps1adm ds0007

STOP tpsapstart PS1 3 20010307182423 ps1adm ds0007

START locksysX PS1 20010307182423 ps1adm ds0007

STOP locksysX PS1 20010307182423 ps1adm ds0007

2 Troubleshooting

2010-06-22 CUSTOMER 1156

START locksys PS1 | 20010307182423 ps1adm ds0007

STOP locksys PS1 | 20010307182423 ps1adm ds0007

INFO event SAP_IMPORT_STOP triggered successfully

STOP put PS1 0008 20010307182423 ps1adm ds0007

ALOGltRelgt

This file is also written by tp It provides information about which actions were started by tp For

information about these actions see section Transport Phase Log Files below

ULOGltRelgt

This file contains all tp calls including the relevant call parameters which have been executed by the

installation program during the installation

Transport Phase Log Files

Additional detailed logs are also written for most steps in the ABAP system These are in subdirectory

tmp of the abap subdirectory of the enhancement package installation directory where you can also

monitor them with tail -f After the various steps of the phase have been completed tp moves the

individual logs to subdirectory log of the abap subdirectory of the EHPI directory

The names of transport phase logs must follow the naming convention SAPltTgtltIDgtltSAPSIDgt where

ltTgt is the transport step ltIDgt is a six (or sixteen) character string and ltSAPSIDgt is the name of your

SAP system

You can determine the relevant transport request from the name of the log file by replacing the

transport step ltTgt with a K omitting ltSAPSIDgt and the preceding period Example

SAPltTgtltIDgtltSAPSIDgt corresponds to SAPKltIDgt

The table below lists the most important steps together with their log names and specifies which

programs 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 DD OBJECTS (N) NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

tpmvntabs PltDATEgtltSAPSIDgt

PAltDATEgtltSAPSIDgt

PDltDATEgtltSAPSIDgt

PLltDATEgtltSAPSIDgt

tp

MAIN IMPORT (I) SAPIltSAPSIDgt R3trans

tpmvkernel (C) CltDATEgtltSAPSIDgt tp

TBATG CONVERSION OF MC OBJECTS (N) NltDATEgtltSAPSIDgt ABAP program (RDDGEN0L)

IMPORT OF SELFDEFINED OBJECTS (D) SAPDltSAPSIDgt ABAP program (RDDDIC1L)

2 Troubleshooting

1256 CUSTOMER 2010-06-22

VERSION UPDATE (V) SAPVltSAPSIDgt ABAP program (RDDVERSL)

EXECUTION OF REPORTS AFTER PUT (R) SAPRltSAPSIDgt ABAP program (RDDEXECL)

Once the logs are located in subdirectory log of the abap subdirectory of the EHPI directory you can

also display them in the SAP system

You can do this by executing program RDDPROTT with transaction SE38 RDDPROTT displays all

the logs for a specific transport request In the Transport Request field enter the name of the transport

request (for example SAPKltrelgtD01) and then choose Execute

A brief overview of all the logs existing for this transport request appears Double-click a line to display

a log for this step The logs are broken down into several levels Level 1 only displays the return code

for the step Check at least level 2 to display any error messages Double-click an error to see its long

text

After completing each tp-driven phase the installation program creates a summary of all individual

logs in this phase

The names of the summaries usually comprise the phase name (without underscores) and the

extension ELG (for example DDICltrelgtELG) The summary contains the names of the individual logs

any errors that occurred and the return codes If no errors have occurred you need to check these

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 occurred during

a specific phase of the installation From these files you can call up detailed log files that contain more

information When errors are detected during a phase a message appears and prompts you to repeat

that phase First check the ltPHASEgtELG log to find out why the step terminated In some cases you

can choose ignore in the installation program to continue with the enhancement package installation

and avoid repeating the failed phase You must always remove the cause of the error When you choose

ignore the installation program prompts you to enter a password if the errors are serious In this case

you must get approval from SAP Support to ignore the error Remove all errors to avoid the risk of

follow-on errors 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 the header

of each phase step

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

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

processed completely

2 Troubleshooting

2010-06-22 CUSTOMER 1356

If a return code is greater than or equal to 12 then tp or a program called by tp has terminated

2 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 both log directories enter the following commands

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

3 If a background step in the SAP system terminates you must analyze the job log in the SAP system

to determine the cause of the error

1 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

in the or after event field The job overview normally displays one canceled job and one

background job that completed normally

2 Double-click the canceled job to display the job log

3 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 SAP system may prevent you from logging on

In this case proceed as follows

1 To unlock the SAP system enter the following commands (here

lttransport_profilegt is the transport profile of the transport domain to which the

system is connected)

cd EHPIabapbin

exetp unlocksys ltSAPSIDgt pf=lttransport profilegt

exetp unlock_eu ltSAPSIDgt pf=lttransport profilegt

2 Log on to the SAP system and correct the error

3 To lock the SAP system again enter the following commands

cd EHPIabapbin

exetp locksys ltSAPSIDgt pf=lttransport profilegt

exetp lock_eu ltSAPSIDgt pf=lttransport profilegt

4 Once you have found and corrected the error repeat the phase by selecting repeat in the installation

program

The repeated phase is usually completed quickly since the transport control program tp

automatically starts from the point at which it terminated

2 Troubleshooting

1456 CUSTOMER 2010-06-22

24 Accelerating the Runtime of Certain Phases

Procedure

Phases Running ABAP Programs

These phases use the SAP system to operate If you improve the performance of the SAP system this

can speed up these phases

Only valid for Oracle |

Phases TABSPC_PREP and CNV_LIST

You experience excessive run times for the preparation phases TABSPC_PREP and CNV_LIST Although

you have applied the actions recommended in SAP Note 871455 the runtimes of the phases have not

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 |

Phase ACT_UPG

The ACT_UPG phase uses parallel processes

Since phase ACT_UPG calls up the ABAP Dictionary mass activator program it takes longer for SAP

systems with a lot of modifications or customer objects and if you have included a lot of add-ons and

Support Packages

SHADOW_IMPORT Phases

These phases take longer if you have included a lot of Support Packages

Phase PARCONV_UPG

In this phase tables are converted to the target release structure The PARCONV_UPG phase uses the

number of parallel background processes you specified and three tp processes

The runtime of this phase may be longer for the following reasons

Very large tables have to be converted The tables that are converted are listed in the installation

analysis file which also displays the conversion time for each table

If tables get a new index on the target release or an index needs to be regenerated these tables are

listed in the installation analysis file under DDLs The time needed to create the index depends on

the size of the table

In case of other DDL statements the runtime of ALTER TABLE or ADD FIELD statements with fields

that contain default values depends on the size of the table

2 Troubleshooting

2010-06-22 CUSTOMER 1556

25 Correcting Errors in the HIAV_CHK Phase

The HIAV_CHK phase checks if the instance profile name adheres to the SAP naming conventions If the

instance profile name does not contain DVEBMGS the phase stops with an error message

Procedure

Make sure that the instance profile name follows the SAP naming convention and repeat the phase

26 Correcting Entries Made in the INITPUT Phase

The enhancement package installation program determines various system parameters in the

INITPUT phase If there is the need to change a parameter proceed as described below

Procedure

1 Stop the enhancement package installation program by choosing Installation Stop Installation

from the main menu of the installation GUI

2 Choose ABAP Start With Options from the menu

3 Enter the command set stdpar

4 After you have changed the parameters restart the installation

27 Correcting Errors in the DBCHK Phase

This phase determines the database version and the release of the SAP system

To do this the installation program runs the transport control program tp which logs on to the

database and reads the necessary information from there

Any problems in this phase are usually due to a failed database connection

Prerequisites

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

Procedure

1 Check the SLOGltrelgt file in subdirectory log of the abap subdirectory of the EHPI directory

Any 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 Transport

Management System (TMS)

For more information see the TMS online documentation

To display the documentation choose Information in transaction STMS or the following path in the

SAP Library [page 5]

2 Troubleshooting

1656 CUSTOMER 2010-06-22

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability

Software Life Cycle Management Software Logistics Change and Transport System ndash Overview Transport

Management System

28 Correcting Errors in the BATCHCHK Phase

This phase tests whether the background server can access the installation directory To do this the

background job RDDIT008 is started on the specified background server This job writes a test log in

subdirectory tmp of the abap subdirectory of the installation directory

Procedure

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

If the background job cannot be started this is generally due to a problem with the name of

the background server

1 Check whether the host specified in phase INITPUT is included in the list with a running

background service

To do this perform a test call of function module TH_SERVER_LIST in transaction SE37

To display the list double-click the table parameter LIST after executing the function

module

2 Depending on the problem you either have to change the network configuration or

change the entries made in the INITPUT phase

If the job terminates call transaction SM21 to check the system log of the SAP system

If the job is successful but the installation program cannot find the log make sure of the

following

1 The file system of the installation directory must be mounted on the background server

2 The value of the SAP profile parameter DIR_PUT must match the installation directory

2 To repeat the phase choose repeat

29 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 file

2 Activate these objects using transaction SE11

The inactive nametab is then empty

3 Continue the installation with repeat

2 Troubleshooting

2010-06-22 CUSTOMER 1756

210 Troubleshooting in the DBCLONE Phase

In the DBCLONE phase SAPehpi starts a number of background jobs to create copies of the tables required

for operating the shadow system Depending on your system and your hardware this operation can

take several hours These background jobs are executed on the background server that is configured

with the BATCH HOST parameter The number of jobs is determined by the parameter MAX BATCH

PROCESSES It cannot be higher than nine or the number of background processes configured on the

background server

Only valid for IBM DB2 for i5OSIBM DB2 for zOSMaxDBMS SQL ServerOracle |

Each table is copied with a single insert statement Therefore the administrator has to take care that

the undo-logs can grow accordinglyEnd of IBM DB2 for i5OSIBM DB2 for zOSMaxDBMS SQL ServerOracle |

Only valid for IBM DB2 for Linux and UNIX and Windows |

The data is copied in 300 MB packetsEnd of IBM DB2 for Linux and UNIX and Windows |

Each cloning job writes a log file called DBCLONEltNUMBERgtltSIDgt At the end of the phase all errors

found in these log files are collected in the DBCLONEELG file The information in the DBCLONEELG file

is rather sparse Therefore you also have to check the corresponding log files to find detailed

information about the error

CAUTION

The following sections describe some advanced options for the database cloning procedure Use

these options only if explicitly asked by SAP Support

Procedure

Excluding a Table from the Standard Copy Process

In some cases it might be easier to clone a specific table using some database-specific tools To prevent

the DBCLONE phase from copying a specific table proceed as follows

CAUTION

Do not use this procedure just to avoid copying big tables Misuse can lead to data loss and errors

in the enhancement package installation procedure

1 Stop the enhancement package installation program before the DBCLONE phase

2 Execute the following SQL command using database tools

UPDATE ldquoPUTTB_SHDrdquo SET ldquoCLONSTATErdquo = lsquoXrsquo WHERE ldquoTABNAMErdquo = lsquoltName of the tablegt

3 Copy the affected table with database tools

4 Continue with the enhancement package installation and run the DBCLONE phase to copy the rest

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

Reinitializing the Copy Procedure

The copy procedure is initialized in the RUN_RSDBSCPY_INIT phase long before the DBCLONE phase Thus

the enhancement package installation program is able to estimate the required additional space in the

database as early as possible

To reinitialize the copy procedure before the DBCLONE phase call transaction SE37 and execute the

ABAP function module INIT_CONTREQ with default parameters

Copying a Single Table

In some cases it might be required to copy a single table for example to debug the cloning process to

find out the error

Proceed as follows

1 Start the ABAP report RSUPG_CLONE_TABLES

2 Specify the following parameters

Parameter Value

LOGFILE ltLog file namegtThe log file is written to the directory ltinstallation directorygtabaptmp

ORTAB ltName of the table to be copiedgt

CPTAB ltName of the target tablegtOnly valid for IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle |

Normally ltName of the table to be copiedgt+~End of IBM DB2 for Linux and UNIX and WindowsIBM DB2 for zOSMaxDBMS SQL ServerOracle |

EXE Set to lsquoXrsquo if the table should really be copied Set to lsquo lsquo if you only like to see the generated statements lsquo lsquo does only make sense in combination with the SHOWSQL parameter

SHOWSQL Set to lsquoXrsquo if you want to see the generated statements

TABTYPE Set to lsquoNrsquo if only the table structure should be copied Set to lsquo1rsquo to copy the content as well

TABSMAP Leave the default value

211 Correcting Errors in the START_SHDI_FIRST Phase

Procedure

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

212 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 problems

occur during the execution of the background job you receive an error message

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

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

name of the job or report

Procedure

1 Log on to the SAP system as user DDIC

2 Call transaction SM37 and restrict the start time and start date of the background job as much as

possible

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 Support

If the background job was started there are two possible situations

The job was terminated

Check whether the error can be reproduced by selecting repeat in the installation program

If the error occurs again contact SAP Support In this case proceed as described in Providing

SAP Support with Information [page 31]

The job was completed but with error messages

In certain situations you can ignore these error messages In this case the installation

program does not require a password if you choose ignore If you are not sure how to

proceed contact SAP Support

213 Cleaning Up Terminated Conversions in the DB Conversion Phases

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

Restart logs of DB conversions found

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

Procedure for ldquoRestart Logs of DB Conversions Foundrdquo

To 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 appears

3 Double-click a table name to see its details

2 Troubleshooting

2056 CUSTOMER 2010-06-22

4 Check the meaning and status of the table

1 Find out whether the table is still needed Sometimes the tables are test tables that are no

longer needed

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

If the table is no longer needed choose Unlock table in the detailed display This prevents the

conversion from being continued automatically The table itself does not return to a consistent

state Any data that is still in the temporary table is lost during the next conversion In some

cases however the table was already corrected without the reset log being deleted The

function Unlock table is harmless in this case

3 You can determine the state of the table with Check Database object and Check Runtime

object

4 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 your SAP

consultant or SAP Support for help in saving this data

5 Determine the cause of the error

If you find out that the table is still needed choose Object log Look for error messages that explain

why the conversions were terminated You could encounter the following problems here

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)

The log does not contain an error message 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 the approximate time the conversion was terminated and to look for the cause

of the error

If the log clearly gives a reason for the error you must correct it

6 Continue the conversion to the end

In the detailed display choose Continue adjustment Since you do not know how long this takes choose

processing type Background

The situation can be as follows

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 in the

object log

The conversion terminates again A log now exists Repeat the analysis from step 5 (Determine

the cause of the error)

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

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

Procedure for ldquoOutstanding DB conversions foundrdquo

To clean up terminated conversions indicated by the message Outstanding DB conversions found

proceed as follows

CAUTION

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

found

1 Determine the objects that are affected

1 Start the database utility transaction (transaction SE14) and choose DB Requests Mass

Processing

2 Choose All requests

The worklist of the conversion program appears This worklist was generated by developments

or modifications in your SAP system but has not yet been processed

3 Choose DB requests Created with import

The worklist that was not processed correctly during the last installation appears

2 Check the meaning and status of the requests

In contrast to the procedure for the message Restart logs of DB conversions found this

procedure can also include requests for indexes views and matchcode objects The requests that

are found are not always terminated They might not even have been started

1 Ask the last person who changed the object if the request should still be processed

2 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 program

3 Process the outstanding requests

You can select the requests from the list of mass processing requests and schedule a job for execution

with the function Schedule selections

1 Go to the detailed display of the object by double-clicking it in the list of requests created by

the import

2 Schedule the request or continue it Since you do not know how long this takes choose

214 Correcting Errors in the TRBATCHK_XT Phase

The tp program uses table TRBAT to communicate with the SAP ABAP system If this table contains

entries they could be the remains of an import or export that either terminated or is still running

The installation program already made this check in the preparation roadmap steps

ProcedureClean up table TRBAT For information about this see Evaluating the Results of the Preparation Roadmap

Steps in the Installation Guide under the following messages

2 Troubleshooting

2256 CUSTOMER 2010-06-22

Unresolved 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

215 Correcting Errors in the ACT_UPG Phase

Depending on the results of the ADJUSTCHK phase you may be asked in the ACT_UPG phase to adjust

your modifications to SAP objects so that they correspond to the latest SAP standard version of the

objects If your SAP system has been modified error messages with return code 8 might occur during

the ACT_UPG phase

The errors are listed in the ACTLOGELG log file It shows the same return code for all requests no matter

in which request the errors occurred Check the error messages in the log file Errors occurring several

times for different objects can have the same cause In this case only the object that causes the original

error must be corrected and the activation must be restarted For example a missing data element leads

to error messages for all objects using it

The shadow instance is automatically unlocked to correct the errors and locked again afterwards

Procedure

1 Log on to the shadow instance as a user other than DDIC

If you have not yet created users on the shadow instance do so now as described in Making Entries

for the Downtime Roadmap Step in the Enhancement Package Installation 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 serious inconsistencies

Result

Once you have corrected all the errors you can proceed with the enhancement package installation

where it terminated in the ACT_UPG phases by selecting repeat in the installation program

If you choose ignore severe errors all error messages with return code 8 are ignored

2 Troubleshooting

2010-06-22 CUSTOMER 2356

216 Correcting Conversion Errors in the PARCONV Phase

This procedure enables you to correct problems that occur in the PARCONV_UPG phase The errors can

roughly be divided into two classes

Technical problems on the database

You can recognize these in the system log (transaction SM21) where they are marked with SQL-

ERROR followed by an abbreviation with an error number The problem is often caused by a lack of

space

Logical errors in the object definition

These could also appear in the form of SQL errors Some of them however are already detected

by the system before a command can be given to the database This type of error frequently occurs

if you decide to revert to the SAP standard when you use the modification adjustment functions

in transaction SPDD (ACT_UPG phase)

EXAMPLE

A field was added to an SAP table This field was also used in an index or view In the

ACT_UPG phase however you decided to return to the standard definition of the table (using

transaction SPDD) and this additional field was removed The index or view definition is now

incorrect since the relevant table field is missing If the index definition is not corrected and

the ACT_UPG phase was completed with ignore errors occur when the objects are created

Procedure

1 Analyze the PARCONVELG log

2 Remove the cause of the error

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

extend the database

Correct the objects To do this you can use transaction SE11 In the above example you could

for instance remove the deleted field from the index or view definition or reinsert the deleted

field into the table In addition check whether the objects that are not contained in the

standard system and that are now incorrect can be deleted completely

3 Repeat the PARCONV_UPG phase

For more information about alternative procedures see SAP Note 177680

217 Correcting Errors in the XPRAS Phase

If errors occur in the XPRAS_UPG phase during the execution of XPRA reports the installation program

stops and refers to the XPRASUPGELG log which contains error messages with the following header

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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 the

reports were being executed In addition to the actual error lines a separate line indicates the names

of the reports that generated the preceding error messages

You can display a detailed help text for each of these error messages in the SAP system These texts

usually contain all the information you need to correct the error

Procedure

Finding Help Texts for Error Messages

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

NOTE

The file name that appears in the header of XPRASUPGELG is important for finding the help

text The file name always has the following format

SAPRltIDgtltSAPSIDgt

ltIDgt can be any string of six characters

The name of the relevant transport request can be derived from the two names Replace the

R with a K and delete the period and all characters that follow it

You now have SAPKltIDgt as the name of the transport request

2 Log on to the SAP system

3 Call transaction SE09

4 Choose Requesttask Display individually and enter the name of the transport request SAPKltIDgt

5 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 are visible as of the second

level To display a help text position the cursor on the error message and choose Long text

Correcting Errors

1 Follow the instructions in the help text precisely The help text helps you correct the error

If you are asked to implement an SAP Note proceed as follows

1 Unlock the SAP system using the following command

SAPehpi tp unlock ltSAPSIDgt

2 Implement the SAP Note manually with a user other than DDIC

You cannot use Note Assistant

3 Lock the SAP system using the following command

SAPehpi tp lock ltSAPSIDgt

2 When you have corrected all the errors repeat the installation phase with the installation program

3 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

2 Troubleshooting

2010-06-22 CUSTOMER 2556

log on to the SAP system Call transaction SE38 and display the documentation for the report that

is named in the error log

4 You can also choose Accept non-severe errors and repeat phase XPRAS_UPG

The installation program repeats the phase and accepts all error messages with the return code

8 The errors must be removed after the installation

You require a password for ignore all errors The installation program then continues with the next

phase without executing the following XPRAs Before you can choose ignore you must have

approval from SAP Support

Correcting Errors After the Enhancement Package Installation

If possible correct errors immediately However you can correct some errors that occur during the

execution of XPRA reports after you have completed the installation This option makes sense for

example when special measures in the SAP application areas are necessary to correct the errors and

the corresponding specialists are not available right now To do this you must suppress the execution

of the corresponding report before you repeat the installation phase After the installation correct the

error and run the report manually using transaction SE38

For technical instructions on skipping an XPRA report see SAP Note 122597

CAUTION

Only skip an XPRA report if you are sure you can execute it later (for example if an SAP Note

tells you that this is allowed)

If you cannot execute an XPRA report later and still want to skip it contact SAP Support

Special Error Situations

The error Name xyz has already been used e065(fdt_core) can occur in method

FDT_AFTER_IMPORT

To solve the problem proceed as follows

1 Continue the installation with option Accept non-severe errors and repeat phase XPRAS_UPG

2 Apply SAP Note 1301695

3 Restart the after import processing for method FDT_AFTER_IMPORT using report

FDT_TRANS_Q_RESTART for S tables T tables and C tables

The following short dump occurs

Runtime Errors COMPUTE_INT_PLUS_OVERFLOW

Exception CX_SY_ARITHMETIC_OVERFLOW

Date and Time []

Check whether the dump is the same as described in SAP Note 1243486 and if so proceed as described

there If the dump is different contact SAP Support

2 Troubleshooting

2656 CUSTOMER 2010-06-22

218 Correcting Errors in the VALCHK_INI Phase

An error can occur when you have incorrectly reset the enhancement package installation For

example you have not used the Back button on the GUI or the Reset Installation command from the menu

bar Instead you have aborted SAPehpi and deleted the installation directory This results in an

inconsistent system state and a failure in phase VALCHK_INI when you start the installation program

again

If you were in one of the preparation roadmap steps when you tried to reset the installation proceed

as described below If you had already reached the Preprocessing roadmap step then contact SAP Support

Procedure

1 Change to the ltinstallation directorygtabapbin directory

2 Enter the following command

SAPehpi reset prepare

3 Delete the installation directory

4 Extract the SAP Enhancement Package Installer archive and start the installation program again

219 Running SAPehpi Process After the Installation

If you run the installation using a local installation GUI it might occur that an SAPehpi process is still

running after the installation has finished and you have closed the GUI with the OK button You can

end this process manually

220 Restarting the Installation GUI

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

Procedure

1 Stop the GUI process with operating system means

2 Start the installation program as described in Starting the Installation Program and Starting the Installation

GUI in the installation guide

221 Preparing the Restart of the Installation After a System Failure

If the system fails (due to a power failure for example) the installation program tp and R3trans can

no longer perform certain cleanup actions Before you restart the installation after a system failure

you must make sure that you meet the requirements for restarting the system successfully

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

1 Start the SAP system

2 Log on to the SAP system as user DDIC and call transaction SM31 to delete all the entries from table

TRBAT

3 Call transaction SM37 to delete all the released background jobs related to the processing of a phase

with the exception of RDDIMPDP

4 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 jobs

5 Call transaction SM50 to cancel any background jobs that have already been restarted

6 Move all the logs contained in subdirectory tmp of the abap subdirectory of the EHPI directory to

the log subdirectory

NOTE

Enter the following commands to copy a log to a new location These commands make sure

that if there are identical names the logs from the abaptmp subdirectory are added to the

logs in the log subdirectory and no logs are overwritten

cd EHPIabaptmp

cat ltlog namegt gtgt logltlog namegt

rm ltlog namegt

7 Restart the installation program as described in Restarting the Installation Program in the Installation

Guide

222 Correcting Problems when Processing ABAP Steps

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

ABAP Dictionary activation (A)

Distribution of ABAP Dictionary objects (S)

Table conversion (N)

Matchcode activation (M)

Import of application objects (D)

Update of version management (U)

Execution of XPRAs (R)

The TRBAT table forms the interface between the transport control program tp and the SAP system

To trigger an ABAP step tp writes control information to this table

The 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 DDIC

2 Call transaction SM37 and check whether the background job RDDIMPDP has been scheduled

2 Troubleshooting

2856 CUSTOMER 2010-06-22

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

3 Check when RDDIMPDP last ran and whether it ran without errors

4 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 request

While the ABAP Dictionary objects are being distributed (S) and the tables converted (N) table

TRBAT may contain only one HEADER entry since these steps are not carried out by transport

request

5 Call transactions SM37 and SM50 to check whether RDDIMPDP has already started the background

job that processes the ABAP step

For more information about the transport control program tp and the communication between tp

and the SAP system see the SAP Library [page 5] at

Software Life Cycle Management Software Logistics Change and Transport System ndash Overview Transport Tools

Transport Control Program tp

223 Correcting Problems when Starting the SAP System

There are several reasons why you might not be able to start the SAP system during the enhancement

package installation

tp the transport control program automatically restarts the SAP system several times during the

individual phases If the startup attempt fails and the next step requires processing within the SAP

system (such as a table conversion) then tp waits for this step to end without result

The command for the SAP system start and stop procedure has changed in SAP Web Application

Server 610 Up until the ENVCHK phase the SAP system is started and stopped with the old

commands After the KX_SWITCH_1 phase the SAP system is started and stopped with the new

commands

Procedure

Procedure for Processes Not Ended

1 Check the SLOG log (SLOGltrelgt) to see whether the SAP system is supposed to be started or stopped

at this point Starting at the end of the log search upwards for the latest entry marked

tpsapstop or tpsapstart

2 If the SAP system is supposed to be started according to the SLOG log but you cannot log on as user

DDIC enter the following command to stop any SAP processes that are running

stopsap r3

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

following command

ps ndashfu ltsapsidgtadm

2 Troubleshooting

2010-06-22 CUSTOMER 2956

The output should show no jobs It should only display database processes SAPehpi tp and some

shells

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

startsap r3

If you cannot start the SAP system manually then this is usually due to changes in the SAP profile in

the MODPROF_TRANS MODPROF_BAS and MODPROFP_UPG phases or due to a switch of the SAP programs in

the KX_SWITCH_1 phase In this case check the consistency of the SAP profiles with the program

sappfpar

Enter the following command

sappfpar check pf=ltDIR_PROFILEgtltinstance profilegt

(instance profile = ltSAPSIDgt_DVEBGMSltinstance numbergt_lthost namegt)

224 Correcting Problems with Starting the Shadow Instance

Procedure

If you have problems with starting the shadow instance see SAP Note 525677

225 Correcting Problems when Copying SAP Programs

In the KX_SWITCH phase the SAP programs in directory usrsapltSAPSIDgtSYSexerun are

switched

Do not start the SAP system during this period otherwise the installation program cannot overwrite

the old files

Procedure

1 Analyze the log of the copy process called CltDATEgtltSAPSIDgt

It is located in subdirectory log of the abap subdirectory of the EHPI directory

2 Repeat the phase or copy the program manually from subdirectory exe of the abap subdirectory

of the EHPI directory to the directory usrsapltSAPSIDgtSYSexerun

226 Use of Kernel and Instance Numbers During the Installation Process

During the enhancement package installation the shadow system uses the kernel from subdirectory

exe of the abap subdirectory of the enhancement package installation directory If you did not provide

a newer kernel in the download directory the installation program takes the kernel from the original

system If a newer kernel version is available in the download directory the installation program

unpacks it to the exe subdirectory and applies it to the original system in the downtime roadmap step

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Regarding the instance numbers the installation program uses different instance numbers for the

original system and the shadow system Normally the switches between instance numbers and kernels

require no user action If however in case of an error you need to log on to the shadow instance or to

exchange the kernel you must know which version to use

In the ABAP system the kernel version and instance numbers are used as follows

The kernel of the original system is used until the phase KW_SWITCH_1 in the Downtime roadmap

step The latest kernel from the exe subdirectory is used for the shadow system and if it is newer

then the original kernel also for the original system after the KW_SWITCH_1 phase

During downtime the instance number of the shadow system is temporarily used for the original

system It is switched back to the original instance number at the end of downtime

227 Providing SAP Support with Information

If none of the measures described in Troubleshooting [page 7] solves your problem contact SAP Support

To enable us to help you as quickly and efficiently as possible follow the procedure given here

Procedure

If you encounter problems that are specific to the enhancement package installation create an error

message in SAP Support Portal (httpservicesapcomsupport) and assign it to component BC-

EHP-INS Answer the following questions and put these answers in your customer message

1 For which SAP component do you want to install an enhancement package

2 If a trouble ticket exists attach it to the message together with the log archive

(SAPehpi_troubleticket_logssar) If there is no trouble ticket include the following

information in your message

What is the release of your SAP system

Which operating system version are you using

In which installation program phase does the error occur

This information is listed at the end of the SAPehpilog file located in the installation directory

3 Did you have problems with the SAP system before the enhancement package installation

NOTE

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

SAP system

If you are certain that the problem is not an installation-specific one but a product-specific one assign

your error message to the appropriate product-specific component

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

This part of the document contains additional information about the various administrative tasks that

you can or must perform before and during the enhancement package installation

Reducing Downtime [page 34]

Manual Selection of Parameters [page 35]

Database Archiving Parameter [page 36]

Background Process and Tool Parameters [page 37]

Running the Shadow Instance Remotely [page 38]

Shadow Instance Parameters [page 39]

SGEN Execution Modes [page 39]

Changing the DDIC Password [page 40]

Incremental Table Conversion [page 40]

Determining Versions [page 42]

Isolating the Central Instance [page 43]

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

Only valid for MaxDB |

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

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

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

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

Changing the Oracle Database Recovery Mode [page 48]End of Oracle |

Releasing and Confirming Open Repairs and Requests [page 49]

Using the Phase List for the Enhancement Package Installation [page 50]

3 Administration

2010-06-22 CUSTOMER 3356

31 Reducing Downtime

Procedure

Hardware

Fast hardware is key to speeding up the installation process With faster hardware the overall runtime

decreases and therefore the downtime as well

Some phases benefit from a faster CPU and additional memory Other phases require fast disk IO

CPU

Several phases run parallel processes However since the number of parallel processes is usually

not larger than eight more CPUs may thus not be exploited fully Four CPUs with 800 MHz are

faster than eight CPUs with 400 MHz for example

RAM

Additional memory for the database and the SAP kernel can improve speed especially for phases

that use the SAP system such as the activation phase or the XPRAS phase

Disk IO

During the main import phases (SHADOW_IMPORT TABIM) a fast disk IO is the key to reducing the

installation runtime

Backup

You need to be able to restore the installation to the point when downtime began You can do this

using your usual backup and archiving model You also need to make a backup of your database after

the installation has finished

You can reduce the downtime significantly if you use a fast backup mechanism such as a RAID-based

mechanism or a hardware-based mirror mechanism

Configuration

You can configure the installation by modifying the number of processes used

Number of background processes

This is the key parameter for running ABAP reports in parallel Increasing this parameter speeds

up phases like ACT_UPG PARDIST_SHD PARCONV_UPG and XPRAS_UPG A value larger than 8 does not

usually decrease the runtime

Number of R3trans processes

This parameter affects the number of R3trans processes that tp starts during phases

SHADOW_IMPORT and TABIM A value larger than 8 does not usually decrease the runtime

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

3 Administration

3456 CUSTOMER 2010-06-22

Clients

The number of clients has a significant influence on the runtime During phases SHADOW_IMPORT and

TABIM the data import for some client-specific tables needs to be cascaded into the different clients

The import time therefore increases with the number of clients

The duration of the XPRA phase especially the duration of the after-import methods also depends on

the number of clients

If you no longer need certain clients you should delete them before you start the installation program

because the free space calculation depends on the number of clients

Archiving

In some cases it is useful to archive some of the content of large tables If tables are converted during

the installation the conversion time depends on the size of the table If you can decrease the size of a

table that needs to be converted the downtime is reduced The tables converted during the installation

are summarized in the analysis report RSUPGSUM

The duration of the phase XPRAS_UPG also depends on the size of large tables

Modifications

If you have modified some tables in your system you may need to convert them if you choose to return

to the SAP standard

This may mean that you need to remove some fields or reduce a field length You may want to consider

keeping your modification to avoid such a conversion

Errors

During a test installation errors might occur These errors increase the runtime and downtime of the

installation significantly

During the tests find out if necessary with the help of SAP Support how to prepare the SAP system

so that these errors do not occur again For example if the process fails in phase PARCONV_UPG because

the tablespaces or containers are too small increase the free space by the amount of space you need to

run the phase

32 Manual Selection of Parameters

When you choose preconfiguration mode manual selection you can manually set the parameters to tailor

the installation to your specific needs In the following you can find a description of the parameters

and their influence on the runtime of the installation

3 Administration

2010-06-22 CUSTOMER 3556

321 Database Archiving ParameterOnly 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 to the

database This determines whether the database system can recover lost dataEnd of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle |

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

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

If the archiving mode is on you 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 archiving

So the phase you choose simply determines when the downtime of the ABAP enhancement

package installation starts

End of IBM DB2 for zOS |

The enhancement package installation program prompts you in the Configuration roadmap step to select

when you want to deactivate archiving

The following options are available

Archiving is activated during the entire enhancement package installation

Archiving is deactivated before the start of the downtime (recommended option)

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 SAP

system in production mode as long as possible The archiving strategies that are marked as

ldquopossiblerdquo are only useful in certain cases In the following only the ldquorecommendedrdquo archiving

strategies are described

At the selected time you are then prompted to deactivate archiving

3 Administration

3656 CUSTOMER 2010-06-22

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 installing

the enhancement package in a Multiple Components in One Database System (MCOD) which

means that multiple SAP systems are installed in your database you are not prompted about

archiving Archiving is automatically activated during the entire installation

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

322 Background Process and Tool Parameters

Host name of the background server

There is usually a background service available on the central instance You can check this with

transaction SM51

However in larger systems the background service may be elsewhere to improve load distribution

In this case enter the host name and the name of the relevant application server

In addition make sure that the EHPI directory is mounted on the host with the background service

and that the background server can process background jobs of class C

The server you select must be available for background operations round the clock Check the

active operation modes with transaction SM63 to find out if it satisfies this requirement

Number of parallel processes used by R3trans during production operation (MAXIMUM UPTIME

PROCESSES)

This is the number of background and activator processes used by R3trans that can run in the

system during production operation We recommend a value of 1 which is the default value If

you have enough main memory you can use up to four processes

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 We

recommend three processes for machines with 512 MB (and greater) main memory 3 is also the

default value Up to eight parallel import processes are possible for multiprocessor hosts with

sufficient main memory

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

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

The enhancement package installation program must wait for this length of time at certain

points during the installation so that all the instances are synchronized If the time entered

is too short time intervals might occur in which users can make unchecked changes

Memory-optimized activation

3 Administration

2010-06-22 CUSTOMER 3756

The memory-optimized mode allows to run the activation of ABAP dictionary objects with reduced

memory consumption but a longer runtime This is the default for 32 bit systems

Phase for disabling archive mode

323 Running the Shadow Instance Remotely

If you are unable to operate the shadow instance on the same host as the original system you can

determine another host for the shadow instance in this phase

If you have chosen preconfiguration mode manual selection you are asked in step Configuration if you want

to 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

ProcedureOnly valid for MaxDB |

In addition to the procedure below see SAP Note 1444798End of MaxDB |

1 Select an application server in the system landscape where a dialog instance is installed

The application server must have the same operating system as the central instance If your system

landscape is heterogeneous see SAP Note 430318 for more information

2 Enter the name of the server

3 Enter the operating system of the server

4 Mount the enhancement package installation directory

5 Install a temporary license for the shadow instance

1 To do this use saplicense -get on the other (remote) application server to get the hardware

key For more information see SAP Note 94998

2 Use saplicense -temp to install a license on the application server

6 Continue with the installation program

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 to manually

start the instance in the START_SHDI_FIRST phase and manually stop it in the

STOP_SHDI_LAST phase

End of IBM DB2 for Linux and UNIX and WindowsMaxDBOracle |

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

After you have stopped the shadow instance sometimes the sapstartsrv keeps running You

need to stop it with the following command

sapcontrol -nr ltSHDSIDgt -prot NI_HTTP -function StopService

324 Shadow Instance Parameters

If you install the shadow instance locally using the enhancement package installation program you

have to enter an instance number that has not yet been used in your system landscape

For more information about choosing the instance number for the shadow instance see SAP Note

29972

NOTE

The shadow instance cannot be run on a remote application server

Decide whether you want to operate the shadow instance on a different host For more information

see Running the Shadow Instance Remotely [page 38]End of IBM DB2 for Linux and UNIX and WindowsMaxDBMS SQL ServerOracle |

325 SGEN Execution Modes

If you selected Manual selection of parameters during the Configuration roadmap step you need to decide if

you want to start load generation during or after the enhancement package installation

You can select one of the following SGEN execution modes

Do not start SGEN during the enhancement package installation

If you plan to apply a high number of relevant changes to your system after the enhancement

package installation in the form of a transport or a Support Package we recommend that you

generate the ABAP loads manually after the enhancement package installation

For more information about starting the load generation manually see Generating Loads in the

Enhancement Package Installation Guide

Fill table GENSETC with relevant loads but do not run SGEN

3 Administration

2010-06-22 CUSTOMER 3956

generate the ABAP loads manually after the enhancement package installation However you can

fill table GENSETC already during the enhancement package installation

Fill table GENSETC and run SGEN with low resource consumption

You can trigger the load generation to run automatically during the downtime

With this option the installation program uses one process to generate the loads during the

downtime and one process to generate the loads after the downtime

Fill table GENSETC and run SGEN with high resource consumption

downtime and the maximum number of processes that are available for SGEN to generate the

loads after the downtime

33 Changing the DDIC Password

In the PROFREAD phase you enter the DDIC password It is not usually necessary to change the password

of the user DDIC later After the installation of the shadow system the password of user DDIC in client

000 is the same as on the original system

However if you want to change the password after the PROFREAD phase you have to change it in the

system as well as in the SAPehpi parameter The passwords in the original system and in the shadow

system have to be identical with the passwords known by SAPehpi In the following you will find out

how you can change the SAPehpi parameter

Procedure1 Stop the enhancement package installation program by choosing Installation Stop Installation

3 To make the new password of user DDIC known to the installation program enter the commands

set DDICpwd (original system)

set shdDDICpwd (shadow system)

4 Restart the installation

34 Incremental Table Conversion

The structure of some of the tables in your database changes when you install an enhancement package

In some cases you need to convert these tables This involves completely restructuring them and

converting each individual data record These conversions are usually made during the downtime

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

The incremental conversion function enables many of these tables to be converted before the

downtime The data is converted during production operation of the system

This approach has the following benefits

Reduced downtime during the enhancement package installation

Simple return to the SAP standard for modified tables

Prerequisites

The enhancement package installation program only determines the candidates for transaction ICNV

after the target structure of the tables has been defined The candidates are determined in the

ICNVREQ phase The installation program checks whether the system contains tables for which an

incremental conversion is an advantage These include tables that need to be converted and that contain

large volumes of data and therefore would increase the downtime significantly during a conversion

The enhancement package installation program also enables you to use transaction ICNV for tables

that have been modified by Support Packages add-ons or customer developments

If the above applies the installation program prompts you to start the incremental conversion

Use of the incremental conversion function is optional If you do not want to use incremental

conversion the tables are converted during downtime

Features

Incremental conversion is performed using transaction ICNV This transaction offers the following

functions

Displays the tables determined by the enhancement package installation program (candidates for

incremental conversion)

Decides which candidates should be converted incrementally

Starts the conversion

Monitors the conversion

Estimates the runtime of the conversion

For up-to-date information see SAP Note 490788 For more information call transaction ICNV and

choose F1 or Information

Note the following

Transaction ICNV makes modifications to the database tables that you want to convert during the

preparation roadmap steps You cannot reset these modifications by resetting the enhancement

If you use incremental table conversion do not start an SAP archiving program for these tables at

the same time since this can lead to performance bottlenecks Therefore archive as much data as

possible before you start the conversion

After the incremental conversion starts you cannot change any more ABAP Dictionary definitions

for the relevant tables until the enhancement package installation is complete

3 Administration

2010-06-22 CUSTOMER 4156

This means that you cannot change delete or add field definitions Transaction SE11 is locked for

these tables

Pay special attention to the resource usage of your database management system to detect

bottlenecks early on Incremental conversion requires double the space in the relevant database

memory area for each table affected during the conversion The continuous transfer of data results

in more transactions being performed Therefore also monitor the space available for the rollback

information

To determine the table size of the tables you want to convert with ICNV see SAP Notes 352081 and

362542

Provide additional free space for these tables during the enhancement package installationEnd of MaxDB |

Do not begin the downtime before at least 95 of the total data has been converted The

enhancement package installation program checks this at the beginning of downtime If this

percentage has not been reached the installation program displays an appropriate message

This gives you the advantage of reducing critical downtime To monitor the progress of the

conversion you can call transaction ICNV

You can start downtime even if the 95 minimum has not been reached However the remaining

data is transferred entirely during downtime If this process is not finished before the

PARCONV_UPG phase the downtime increases depending on the remaining conversion set

Incremental conversion requires a sufficient number of background work processes Ideally there

should be one process for each table that needs to be converted If you cannot have one process

for each table because there are too many of them you can still convert them since transaction

ICNV automatically distributes the tables to the available background processes However the

incremental conversion then takes longer to complete and the time for beginning downtime is

pushed back

35 Determining Versions

Procedure

Determining the Operating System Version

At the UNIX level enter the following command

uname -a

Determining the Database Version for DB2 for Linux UNIX and Windows

If the database instance is running enter the following command as user db2ltsidgt

db2level

End of IBM DB2 for Linux and UNIX and Windows |

3 Administration

4256 CUSTOMER 2010-06-22

Determining the Database Version for SAP MaxDB

Enter the following operating system command

dbmcli -u ltCONTROLUSERgtltCONTROLUSER PASSWORDgt -d ltDBNAMEgt show version

End of MaxDB |

Determining the Database Version for Oracle

Enter the following SQL statement

SELECT BANNER FROM V$VERSION

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

Determining the SAP Kernel Version

To 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 Monitoring

Server

2 Select a server and choose Release Notes

Determining the Date of R3trans

Call R3trans with the following command

R3trans ndashV

The program displays the date and the version number

Determining the Version of tp

Call tp with the following command

tp ndashV

The last line displays the highest patch level

36 Isolating the Central Instance

You need to isolate the central instance so that only the installation program can work with the system

during downtime This means that you can use the central instance exclusively for the installation

The installation program asks you to isolate the central instance when downtime begins

During downtime all users must have logged off the system You can use transaction SM02 to inform

the users who are logged on to the system

Procedure

1 Stop and delete saposcol as user root

cd usrsapltSAPSIDgtSYSexerun

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

2 The SAProuter in directory usrsapltSAPSIDgtSYSexerun must not be active while the new

SAP kernel is being imported You have the following options

Stop the SAProuter now and restart it after the enhancement package installation

If you need the SAProuter during the enhancement package installation you can rename it

as follows

mv saprouter saprouterbusy

Delete saprouterbusy after you have started up the new SAProuter

To display more information about the SAProuter

Enter saprouter at the operating system level

A list of all the parameters appears

See the SAP Library [page 5] at

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability

ABAP Technology ClientServer Technology

3 Make sure that no CRON job is scheduled that affects the SAP system such as starting and stopping

the SAP system saving the database or similar actions

This could impair the full control of the installation program over the SAP system

4 Only valid for AIX |

Check the restrictions for cpu fsize and core for user ltsapsidgtadm

Enter the command lsuser as user root

The parameters must have the following values

cpu=-1

fsize=4194302

core=100000

If not use the chuser command to change them (enter for example chuser cpu=-1

ltsapsidgtadm)

These changes only take effect for user ltsapsidgtadm when you have logged on again as

ltsapsidgtadm

Then start up the SAP system with stopsap and startsapEnd of AIX |

5 Make sure that no change of operation mode is defined on the central instance during the

enhancement package installation

If this is the case in normal operation call transaction SM63 either to choose a single operation

mode for all time spans or to delete all the assignments

3 Administration

4456 CUSTOMER 2010-06-22

6 Clean up all outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps in

the Enhancement Package Installation 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 state

9 Back up the EHPI directory now If a hardware problem occurs during downtime you may need

to reset the installation to the state it had when the SAP system was isolated So that the installation

program has the correct control information the installation directory must have the same state

as at the beginning of the MODPROF_TRANS phase

10 If the central instance and the database server are on the same host you can lock the database

against remote access Contact the database administrator

CAUTION

Make sure that no transport requests are imported into the system during downtime

Otherwise you may lose data For example by manually importing requests for the automatic

adjustment you may lose all your modifications to the standard SAP system

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

Extend existing tablespaces and create new tablespaces as requested by the installation program

To create or extend tablespaces you should use the DB2 Command Line Processor Template

DB6TBSXTCLP generated by the installation program (see the CHECKSLOG file)

Alternatively you can use the DB2 DB6COCKPIT

With DB2 Version 8 Fixpak 9 (822) or higher you can alter existing DMS tablespaces to Autoextend DMS

tablespaces instead of extending the tablespace manually You can do this using the command db2

alter tablespaces lttbspnamegt autoresize yes maxsize none With release 822 or higher new

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

means that the database does not need to trigger a rebalancing process

For more information see the SAP online documentation on database administration for DB2 for Linux

UNIX and Windows

Prerequisites

For performance reasons you must consider the following restrictions when you create the new

tablespaces (in the order they are listed)

3 Administration

2010-06-22 CUSTOMER 4556

Different containers of a tablespace must be located on different (physical) disks

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 values

2 Create the new tablespaces as prompted by the installation program This applies to the following

tablespaces in an enhancement package installation

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 releaseEnd of IBM DB2 for Linux and UNIX and Windows |

38 Extending Free Space in the SAP MaxDB Database

Procedure

To extend your database use the database tools to add new data volumes For a precise description see

SAP Note 34690End of MaxDB |

39 Extending Free Space in the Oracle Database

Extend and create tablespaces as requested by the installation program

CAUTION

If you use tablespaces where the AUTOEXTEND feature is turned on the installation program

free space check includes this in its calculation However you may still have to create the new

tablespaces

NOTE

Avoid fragmenting the database too strongly

Be generous when you extend existing tablespaces

Choose a low degree of fragmentation when you create tablespaces

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

For performance reasons you must take the following restrictions into consideration when creating

the new tablespaces

Index tablespaces and data tablespaces that belong together must not be on the same disk and

must not be in the same sapdata directory

PSAPESltRELgtD and PSAPELltRELgtD should not be on the same disk

RECOMMENDATION

We recommend the following combination

Disk 1 PSAPESltRelgtD and PSAPELltRelgtI

Disk 2 PSAPELltRelgtD and PSAPESltRelgtI

Only valid for AIX |

If the AIX user parameter fsize (= maximum file size) is set to the default value of 1 GB for user

oraltsapsidgt error messages appear if you create tablespaces greater than 1 GB Where necessary

increase the value of fsize Note that the parameter fsize is increased by the same amount for

user ltsapsidgtadm Otherwise ltsapsidgtadm cannot start up the database after large tablespaces

have been createdEnd of AIX |

Procedure

To extend and create tablespaces use program EHPIabapexebrspace as user oraltsapsidgt You can

use a command line template for BRSPACE generated by the installation program (see file

CHECKSLOG) For more information see the SAP online documentation on the BRSPACE program

BRSPACE proposes other values for the extension than those specified in the list You can overwrite these

values however you must meet the minimum requirements of the list

Proceed as follows

2 Create the new tablespaces as prompted by the installation program and with the AUTOEXTEND

feature turned on This applies to the following tablespaces during the enhancement package

installation

PSAPESltRelgtD PSAPltSAPSIDgtltRelgt

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

For the tablespace PSAPESltRelgtD create a data file with at least 2 GB otherwise the import of the

substitution set terminates

If you have to create a tablespace in more than two fragments add (n - 2) 100 MB to the total

size of the tablespace where n is the number of fragments

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

Reboot your AIX system to activate the new values

End of AIX |

End of Oracle |

310 Changing the DB2 for Linux UNIX and Windows 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

RECOMMENDATION

If the last full backup was a long time ago and the number of archives collected up to that point

is large 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 |

311 Changing the SAP MaxDB Database Recovery Mode

Procedure

At the start of downtime

The installation program automatically deactivates archiving

At the end of downtime

Archiving can only be reactivated by making a full backup in operating mode ADMIN

That is why the enhancement package installation can be continued only after you have made a

backup of the database if archiving is deactivatedEnd of MaxDB |

312 Changing the Oracle Database Recovery Mode

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

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

archiving

RECOMMENDATION

If the last complete database backup was a long time ago and the number of archives collected up

to that point is large we recommend that you make a complete database backup before you

deactivate archiving

Procedure

On the database server deactivate archiving as follows

1 Log on as user oraltdbsidgt

2 Start program BRSPACE using the following command

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

In the same way as when you deactivate archiving you can reactivate it as user oraltsapsidgt with

program BRSPACE using the following command

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

NOTE

You can call BRSPACE for information about the current status of redo log archiving using the

following command

brspace -c force -f dbshow -c dbstate

End of Oracle |

313 Releasing and Confirming Open Repairs and Requests

Before you start the enhancement package installation you must release and confirm all the open

repairs and requests that conflict with the SAP delivery The installation program determines a list of

these repairs and requests If you ignore open repairs you could lose modifications

Procedure

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

owners in CHECKSLOG

NOTE

If you cannot log on with a specific user ID you can change the owner of the repair in

transaction SE09 as follows

1 In the list of open repairs position the cursor on the repair

2 Choose Change owner

To be able to change an owner in transaction SE09 you need project authorization for the

Workbench Organizer (S_CTS_PROJEC)

3 Administration

2010-06-22 CUSTOMER 4956

3 Choose Requesttask Find requests

4 For Request type only select Repair

5 For Request status select everything except Released

6 Choose Execute

A list of all open repairs for the selected user appears

7 Position the cursor on the request that you want to release

8 Choose Release

9 Release the request to which the repair is assigned

314 Using the ABAP Phase List for the Enhancement Package Installation

In the Extraction roadmap step the installation program creates a phase list that is specific for your

enhancement package installation The phase list contains all ABAP phases of the installation in the

right order It consists of the following parts

The Phase List Table of Contents contains a list of all the phases with links to the corresponding

description in the Phase List part

The Phase List part contains a table with all phases and their description

The table contains the following columns

Phase

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

background

Installation Program Actions

Gives a brief explanation of the tool actions Constraints are printed in bold

Duration

Indicates the percentage of the total runtime of the installation program required for this

phase The runtime depends on the following criteria

Amount of customer data

Number of SAP components implemented

Quantity and type of modifications and customer developments involved

Number of clients

Number of included packages

Log Files

Lists the log files that are generated by the installation program for each phase

User Actions

If there is no entry in this column the installation program does not require an operator at

this point Otherwise the installation program prompts you to make the entries described

3 Administration

5056 CUSTOMER 2010-06-22

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

Comment Meaning

(var) The runtime of this phase depends on your data The percentage duration of these phases can be different during your installation

(log) Not all logs can be included in the Log Files column For more information see Installation Logs [page 11]

3 Administration

2010-06-22 CUSTOMER 5156

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 Accessing DBA_SEGMENTS

Oracle-specific

762426 Long runtimes in TABSPC_PREP CNV_LIST DYNSPCADD

Oracle-specific

525677 Problems when starting the shadow instance

General enhancement package installation

177680 Correcting conversion problems in the PARCONV_UPG phase

122597 Ignore errors in the XPRAS_UPG phase General enhancement package installation

29972 Instance numbers in a distributed system

1301695 BRFplus AI Activation Name xyz has already been used

1243486 Dump COMPUTE_INT_PLUS_OVERFLOW during background cleanup

34690 Add Devspace under SAP DB SAP MaxDB

SAP MaxDB-specific

490788 ICNV in the upgrade to SAP Web AS 620 and higher

ICNV

1444798 SAP upgradeupdate Remote shadow instance on MaxDB

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Typographic Conventions

Example Description

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

ExampleExample

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 the documentation

httpwwwsapcom Textual cross-references to an internet address

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

123456 Hyperlink to an SAP Note for example SAP Note 123456

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

Cross-references to other documentation or published works

Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program 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 names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

5456 CUSTOMER 2010-06-22

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

wwwsapcom

No 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 be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

No 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 be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software 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 z10 z9 iSeries pSeries xSeries zSeries eServer zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent 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 Systems Incorporated 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 registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts 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 implemented by NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product 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 not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe 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 or altered in any way

2010-06-22 CUSTOMER 5556

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

copy Copyright 2010 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 be changed without prior notice

Troubleshooting and Administration
- Table of Contents
- 1 Accessing Documentation
- 2 Troubleshooting
- - 21 Error Handling for ABAP
  - 22 Installation Logs
  - 23 Evaluating the ELG Log Files
  - 24 Accelerating the Runtime of Certain Phases
  - 25 Correcting Errors in the HIAV_CHK Phase
  - 26 Correcting Entries Made in the INITPUT Phase
  - 27 Correcting Errors in the DBCHK Phase
  - 28 Correcting Errors in the BATCHCHK Phase
  - 29 Correcting Errors in the INTCHK and INTCHK_SW Phases
  - 210 Troubleshooting in the DBCLONE Phase
  - 211 Correcting Errors in the START_SHDI_FIRST Phase
  - 212 Correcting Errors in the JOB Phases
  - 213 Cleaning Up Terminated Conversions in the DB Conversion Phases
  - 214 Correcting Errors in the TRBATCHK_XT Phase
  - 215 Correcting Errors in the ACT_UPG Phase
  - 216 Correcting Conversion Errors in the PARCONV Phase
  - 217 Correcting Errors in the XPRAS Phase
  - 218 Correcting Errors in the VALCHK_INI Phase
  - 219 Running SAPehpi Process After the Installation
  - 220 Restarting the Installation GUI
  - 221 Preparing the Restart of the Installation After a System Failure
  - 222 Correcting Problems when Processing ABAP Steps
  - 223 Correcting Problems when Starting the SAP System
  - 224 Correcting Problems with Starting the Shadow Instance
  - 225 Correcting Problems when Copying SAP Programs
  - 226 Use of Kernel and Instance Numbers During the Installation Process
  - 227 Providing SAP Support with Information
  - - 3 Administration
    - - 31 Reducing Downtime
      - 32 Manual Selection of Parameters
      - 321 Database Archiving Parameter
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes
        
        Copyright and trademarks

Document History

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

Version Date Description

10 2008-09-11 First version ndash no changes

11 2009-10-02 Information about trouble ticket and changing DDIC password added

12 2010-04-15 Information added about troubleshooting in phases DBCLONE and VALCHK_INI

Several minor changes

13 2010-06-22 Section Enhancement Package Installation Directory moved to SAP Enhancement Package Installation Guide

256 CUSTOMER 2010-06-22

Table of Contents

Phases 20

Process 30

2010-06-22 CUSTOMER 356

Database 45

Mode 48

Installation 50

456 CUSTOMER 2010-06-22

SAP Help Portal

Procedure

SAP Help Portal

2010-06-22 CUSTOMER 556

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Table of Contents

Phases 20

Process 30

2010-06-22 CUSTOMER 356

Database 45

Mode 48

Installation 50

456 CUSTOMER 2010-06-22

SAP Help Portal

Procedure

SAP Help Portal

2010-06-22 CUSTOMER 556

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Database 45

Mode 48

Installation 50

456 CUSTOMER 2010-06-22

SAP Help Portal

Procedure

SAP Help Portal

2010-06-22 CUSTOMER 556

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

SAP Help Portal

Procedure

SAP Help Portal

2010-06-22 CUSTOMER 556

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

2 Troubleshooting

NOTE

SAPehpiConsolelog

Logs

General problems

2 Troubleshooting

2010-06-22 CUSTOMER 756

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Tool Reaction

log file

The tool aborts

Error Analysis

Trouble Ticket

File dev_SAPehpi

2 Troubleshooting

856 CUSTOMER 2010-06-22

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Log Files

ELG Log Files

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

Detailed Log Files

directory

Background Jobs

CAUTION

2 Troubleshooting

2010-06-22 CUSTOMER 956

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

the terminated step

file

SAP System Log

2 Troubleshooting

1056 CUSTOMER 2010-06-22

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Features

SLOGltRelgt

each step

LIST put PS1 (33|

2 Troubleshooting

2010-06-22 CUSTOMER 1156

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

ALOGltRelgt

ULOGltRelgt

SAP system

tp

2 Troubleshooting

1256 CUSTOMER 2010-06-22

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

text

logs in this phase

summaries only

Procedure

of each phase step

2 Troubleshooting

2010-06-22 CUSTOMER 1356

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

ls -ltr EHPIabaplog

ls -ltr EHPIabaptmp

NOTE

cd EHPIabapbin

program

2 Troubleshooting

1456 CUSTOMER 2010-06-22

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Procedure

CAUTION

Phase ACT_UPG

Support Packages

Phase PARCONV_UPG

2 Troubleshooting

2010-06-22 CUSTOMER 1556

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Procedure

Prerequisites

Procedure

2 Troubleshooting

1656 CUSTOMER 2010-06-22

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Management System

Procedure

background service

module

following

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1756

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

background server

CAUTION

Procedure

CAUTION

of the tables

2 Troubleshooting

1856 CUSTOMER 2010-06-22

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

find out the error

Proceed as follows

Parameter Value

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 1956

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

NOTE

Procedure

possible

NOTE

Procedure

2 Troubleshooting

2056 CUSTOMER 2010-06-22

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

longer needed

object

of the error

object log

Support

2 Troubleshooting

2010-06-22 CUSTOMER 2156

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

proceed as follows

CAUTION

found

Processing

the import

2 Troubleshooting

2256 CUSTOMER 2010-06-22

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

the ACT_UPG phase

Procedure

CAUTION

Result

2 Troubleshooting

2010-06-22 CUSTOMER 2356

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

space

EXAMPLE

Procedure

extend the database

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

2 Troubleshooting

2456 CUSTOMER 2010-06-22

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

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

Procedure

NOTE

Correcting Errors

2 Troubleshooting

2010-06-22 CUSTOMER 2556

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

CAUTION

FDT_AFTER_IMPORT

Date and Time []

2 Troubleshooting

2656 CUSTOMER 2010-06-22

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

again

Procedure

2 Troubleshooting

2010-06-22 CUSTOMER 2756

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Procedure

TRBAT

NOTE

cd EHPIabaptmp

rm ltlog namegt

Guide

Procedure

2 Troubleshooting

2856 CUSTOMER 2010-06-22

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

request

commands

Procedure

stopsap r3

following command

2 Troubleshooting

2010-06-22 CUSTOMER 2956

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

shells

startsap r3

sappfpar

Procedure

switched

the old files

Procedure

2 Troubleshooting

3056 CUSTOMER 2010-06-22

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Procedure

NOTE

SAP system

2 Troubleshooting

2010-06-22 CUSTOMER 3156

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

3 Administration

2010-06-22 CUSTOMER 3356

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Procedure

Hardware

CPU

RAM

Disk IO

Backup

Configuration

3 Administration

3456 CUSTOMER 2010-06-22

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Clients

Archiving

Modifications

to the SAP standard

Errors

run the phase

3 Administration

2010-06-22 CUSTOMER 3556

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

CAUTION

operation

NOTE

3 Administration

3656 CUSTOMER 2010-06-22

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

CAUTION

transaction SM51

PROCESSES)

CAUTION

3 Administration

2010-06-22 CUSTOMER 3756

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

NOTE

CAUTION

3 Administration

3856 CUSTOMER 2010-06-22

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

NOTE

29972

NOTE

3 Administration

2010-06-22 CUSTOMER 3956

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

(phase PARCONV_UPG)

3 Administration

4056 CUSTOMER 2010-06-22

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Prerequisites

Features

functions

Note the following

3 Administration

2010-06-22 CUSTOMER 4156

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

these tables

information

362542

pushed back

Procedure

uname -a

db2level

3 Administration

4256 CUSTOMER 2010-06-22

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

End of MaxDB |

Server

R3trans ndashV

tp ndashV

Procedure

3 Administration

2010-06-22 CUSTOMER 4356

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

saposcol ndashk

saposcol ndashd

Collectorgt leave

rm saposcol

as follows

cpu=-1

fsize=4194302

core=100000

ltsapsidgtadm)

ltsapsidgtadm

3 Administration

4456 CUSTOMER 2010-06-22

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

process appears

CAUTION

RECOMMENDATION

UNIX and Windows

Prerequisites

3 Administration

2010-06-22 CUSTOMER 4556

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

on the same disk

Procedure

CAUTION

tablespaces

NOTE

3 Administration

4656 CUSTOMER 2010-06-22

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Prerequisites

the new tablespaces

RECOMMENDATION

Procedure

Proceed as follows

installation

PSAPESltRelgtI

PSAPELltRelgtD

PSAPELltRelgtI

CAUTION

3 Administration

2010-06-22 CUSTOMER 4756

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

CAUTION

End of AIX |

End of Oracle |

RECOMMENDATION

Procedure

3 Administration

4856 CUSTOMER 2010-06-22

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Prerequisites

archiving

RECOMMENDATION

Procedure

NOTE

following command

End of Oracle |

Procedure

owners in CHECKSLOG

NOTE

3 Administration

2010-06-22 CUSTOMER 4956

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

6 Choose Execute

8 Choose Release

Phase

background

Duration

Number of clients

Log Files

User Actions

3 Administration

5056 CUSTOMER 2010-06-22

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Comment Meaning

3 Administration

2010-06-22 CUSTOMER 5156

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

4 Related SAP Notes

Oracle-specific

SAP MaxDB-specific

ICNV

MaxDB

4 Related SAP Notes

2010-06-22 CUSTOMER 5356

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Example Description

ExampleExample

5456 CUSTOMER 2010-06-22

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

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

wwwsapcom

2010-06-22 CUSTOMER 5556

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

- Table of Contents
- 2 Troubleshooting
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        4 Related SAP Notes

Date post:	28-Nov-2015
Category:	Documents
Upload:	srinivas-rentala
View:	19 times
Download:	2 times

011000358700000065622009 e

Documents