SAP Note 24800 - Export sticks with the status OPEN (>= 2.1G)

Symptom:

The transport request hangs up when releasing a transport request from the correction system in the SAP System (transactions SE01 or SE09 as of Release 3) with the status OPEN.

Cause and prerequisites

The transport is not set up correctly on operating system level.

Solution

This note is valid only as of Release 2.1G. For releases before 2.1G please read note 12954.
Various things can cause this problem. Therefore, a systematic procedure is proposed to localize and eliminate the error. If you discover an error during a step, then correct this error and repeat the transport release before searching for further errors.

1. The tp is started by the system with a "silent" option. This causes everything that tp would normally output on the screen to be written to a certain file. This file is called "dev_tp" and can be found in the respective work directory for the tp call. In this case, this directory is the "work" directory of the application server on which the release was attempted. Check whether this file ("/usr/sap//D*/work/dev_tp") exists and whether the user adm has write authorization for it. If the file does not exist, make sure that the user adm has write authorization for the directory.

2. Parameters of the SAP system determine the connection between a) the executable directory particularly for tp on the operating system level and the system AND b) the transport directory and the system.

3. Normally, the standard values (defaults) are correct. If no "dev_tp" file is created, then check the following two SAP system paratmeters (at best on each application server): a) "exe/tp" must point to a tp that truly exists (according to the standard installation, the default /usr/sap//SYS/exe/run/tp is correct; b) "DIR TRANS" must point to the correctly installed transport directory (here, too, we recommend the default transport directory /usr/sap/trans/). You can display all the SAP system parameters with report RSPARAM in the SAP system.
NOTE: Parameter 'transport/exe_tp' -- which is actually used by the SAP system to start the export -- is constructed from the two parameters 'exe/tp' and 'DIR_TRANS.'

4. As a futher test, as adm change to the working directory of the application server (see above) and call tp manually. Use the complete value of the parameter 'transport/exe_tp' with the following values added: 'export silent U1', for example:
'/usr/sap/C11/SYS/exe/run/tp pf=/usr/sap/trans/bin/TPPARAM export C11K904711 silent U1'.

5. Look at the contents of "dev_tp." tp can store all the different error messages here, which it would be impossible to list here. The messages themselves should provide hints on how the error can be corrected.

6. Examine the contents of the log file in which tp displays the general progress of its commands. You can find this file in the subdirectory "log" of your transport directory. The name can be set (parameter name = "syslog") in the file TPPARAM, which can be found in the "bin" subdirectory. The recommended TPPARAM entry "syslog = SLOG$(syear)$(yweek).$(system)" results in the name SLOG(YY)(WW).(SID), where (YY) is to be replaced by the two-digit year specification, (WW) by the calendar week and (SID) by the name of the source system (for example SLOG9533.C11). The last lines of the file $(transdir)/log/SLOG$(syear)$(yweek).$(system) can contain error messages for the export that was just attempted.
The possible error messages are too diverse to list.

7. Examine whether there is an export log for the transport request. The export log can be found in the "log" subdirectory of the transport directory. The name results from the name of the transport request as follows:
Transport: K<6> (for example C11K904711 )
Log : E<6>. (for example C11E904711.C11)

8. Search the contents of the export log for errors and for the return code.

Additional key words

R3sltratp