Process and Tool Parameters

You can maintain process and tool parameters to configure the update process additionally. Several processes have parameter values for uptime and downtime. The values for downtime are active during the Downtime roadmap step of the update procedure. The values for uptime are active during the Checks and Preprocessing roadmap steps. Note that high values for processes during the uptime can have an impact on production operation.

Host name of the background server

There is usually a background service available on the primary application server instance. You can check it with transaction SM51.

However, in larger systems, the background service can 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 update 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 has to be available for background operations round the clock. Check the active operation modes with transaction SM63 to find out if it satisfies this requirement.
ABAP PROCESSES (UPTIME) and ABAP PROCESSES (DOWNTIME)

Number of parallel background processes and activator processes, also number of batch processes scheduled on the app server.

The specifications have an impact on the JOB and RUN phases that use parallelization, as well as the DBCLONE, ACT_UPG, PARDIST*, and XPRA runtime phases.
We recommend a value that is high enough to enable parallel processing, but small enough so that the production system is not affected. Note also:
- For ABAP processes executed on the original system, the number of available processes on the original system limits the number of parallel jobs.
- For technical reasons, a maximum of 10 parallel processes are possible in the phase DBCLONE.
SQL PROCESSES (UPTIME) and SQL PROCESSES (DOWNTIME)
Number of parallel SQL processes used by
- tp to execute database statements in PARMVNT* and PARCONV* phases.
- SCEXEC, SQLRUNTASK, and SQLSELEXE phases
Note

Dynamic change of SQL processes in SQLRUNTASK phases
In some cases, it can be necessary to change the number of SQL processes (for example to reduce them) during the run of the SQLRUNTASK phases. You can do this using the SUM Utilities (Extended UI). Select SUM Parameters SUM Process Parameters SQL Processes. The change should be directly reflected in the number of running processes.
R3TRANS PROCESSES (UPTIME) and R3TRANS PROCESSES (DOWNTIME)

Number of parallel import processes used by tp and R3trans to import data into the database, mainly in phases DDIC_UPG, SHADOW_IMPORT*, and TABIM*.

Note that these processes can generate significant loads on the database.
R3LOAD PROCESSES

Number of R3load processes used by for the EU_IMPORT and EU_CLONE phases.
Memory-optimized activation

The memory-optimized mode allows the activation of ABAP Dictionary objects with reduced memory consumption, but a longer runtime. This is the default for 32-bit systems.