Update Logs
The Software Update Manager logs all actions in log files to monitor the update. You can access the log files using the Log option on the user interface. Unless otherwise specified below, the log files are stored in the log subdirectory of the abap subdirectory of the SUM directory. If you encounter any errors, you can analyze them to help you find a solution.
SAPup.log
The Software Update Manager records all actions on the ABAP system in the log file SAPup.log. These log files provide you with a general overview of the status of the update. They contain information about all phases performed up to this point, the number of reruns, runtimes, final status, and so on. SAPup.log is updated by the Software Update Manager only.
Log Files Written by tp
SLOG<Rel>
The ABAP program tp lists all its steps in log file SLOG<rel>. 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 <update directory>/abap/log/SLOG<rel>
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:
|
START |
put |
PS1 |
20010307182423 |
ps1adm |
ds0007 |
|
| INFO: event SAP_IMPORT_START triggered successfully | ||||||
|
START |
SET STOPMARK |
PS1 |
20010307182423 |
ps1adm |
ds0007 |
|
|
INFO: Buffer saved as /usr/sap/<sid>/upg_ps1/buffer/PS1SAV. |
||||||
|
STOP |
SET STOPMARK |
PS1 |
20010307182423 |
ps1adm |
ds0007 |
|
|
LIST |
put |
PS1 |
(3{3| |
|||
|
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 |
|
START |
tpsapstart |
PS1 |
3 |
20010307182423 |
ps1adm |
ds0007 |
|
STOP |
tpsapstart |
PS1 |
3 |
20010307182423 |
ps1adm |
ds0007 |
|
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 |
ALOG<Rel>
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.
ULOG<YY_Q>
In ULOG<YY_Q>, “YY” is the year, and “Q” is the quarter.
This file contains all tp calls, including the relevant call parameters, which have been executed by the Software Update Manager during the update.
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 update 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 update directory.
The names of transport phase logs have to follow the naming convention SAP<T><ID>.<SID>, where <T> is the transport step, <ID> is any six (or sixteen) character string, and <SID> 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 <T> with a K, omitting <SID> and the preceding period. For example, SAP<T><ID>.<SID> corresponds to SAPK<ID>.
The table below lists the most important steps together with their log names, and specifies which programs execute the steps:
|
Step |
Log Name |
Program Executing the Step |
|---|---|---|
|
SHADOW_IMPORT |
SAPK??????.<SID> |
R3trans |
|
DD IMPORT (H) |
SAPH??????.<SID> |
R3trans |
|
DD ACTIVATION (A) |
SAPA??????.<SID> |
ABAP program (RDDMASGL) |
|
DISTRIBUTION OF DD OBJECTS (S) |
DS<DATE>.<SID> |
ABAP program (RDDDIS0L) |
|
TBATG CONVERSION OF DD OBJECTS (N) |
N<DATE>.<SID> |
ABAP program (RDDGEN0L) |
|
tpmvntabs |
P<DATE>.<SID> PA<DATE>.<SID> PD<DATE>.<SID> PL<DATE>.<SID> |
tp |
|
MAIN IMPORT (I) |
SAPI??????.<SID> |
R3trans |
|
tpmvkernel (c) |
C<DATE>.<SID> |
tp |
|
TBATG CONVERSION OF MC OBJECTS (N) |
N<DATE>.<SID> |
ABAP program (RDDGEN0L) |
|
IMPORT OF SELFDEFINED OBJECTS (N) |
SAPD??????.<SID> |
ABAP program (RDDIC1L) |
|
VERSION UPDATE (V) |
SAPV??????.<SID> |
ABAP program (RDDVERSL) |
|
EXECUTION OF REPORTS AFTER PUT (R) |
SAPR??????.<SID> |
ABAP program (RDDEXECL) |
Once the logs are located in subdirectory log of the abap subdirectory of the update 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, SAPK<rel>D01) 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 Software Update Manager 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, DDIC<rel>.ELG). 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.