SAP
transport hang. Transport Troubleshooting guide
1. Basic
transport troubleshooting. Verify that there are no errors in system log.
Execute transaction STMS
Select Import Overview
Select SID
From menu > Go To > System Log
Correct if no issues in log.
KNOWN
ISSUES :
1.
Known Issue 1 - WARNING: \\SERVER\sapmnt\SIDtrans\tmp\SID.LOB is already in use
(22720), I'm waiting 2 sec (20100322091720). My name:
pid 10128 on
SERVER (SIDadm)
Solution 1 -
Backup and delete the file '\\SERVER\sapmnt\SIDtrans\tmp\SID.LOB'. Add the
transport again and perform import.
2.
Known issue 2 - Cannot find \\SERVER\sapmnt\SIDtrans\log\SLOGXX02.SID
Solution 2 - Make sure that file exists. If not, copy
the most recent SLOG (example SLOGXX01) and rename it to SLOGXX02.SID. Check
again the system log if the issue persist.
3.
Known issue 3 - Problems with job RDDIMPDP
Solution 3 -
Execute SE38 > Run program RDDNEWPP > Choose Normal priority. This will
schedule new RDDIMPDP job that is responsible for pushing transport requests in
your system.
Disclaimer: The next steps are steps to clear the
transport list to make sure that transports push successfully. This should be
aligned with customer.
2.
Clear the transport list and redo the transport
Execute transaction STMS
Import overview -> Goto -> Import
monitor >
'Monitor' -> right click on transport ->
delete entry
Redo the transport action. Proceed to next
step if not solved.
3.
Clear the transport tables
Make sure that there are no stuck transports
in your transport tables.
Check and delete entries (using transaction
SM30) any entries found in the following tables:
TPSTAT
TRJOB
TRBAT
To do this
execute SM30
Enter 'TRBAT' in
Table/View.
Click on Display
Verify that NO transport number or HEADER exists.
If the Import
Monitor or table TPSTAT does not contain
entries any
more, you can delete the entries of tables TMSTLOCKR andTMSTLOCKP.
Redo the
transport action.
If this does not solve the problem. You have the option
to stop all transport from OS level.
4.
Kill tp.exe OS process
Login to SAP
server
Kill any TP.exe
processes at the OS level.
Try again to add
and import your request
Redo the
transport action
5.
Save transport resources.
It is SAP's
recommendation that imports be done asynchrounously rather than synchronously.
By doing this you will be conserving system Resources.
In doing the
import > Execution tab > Select 'Asynchrounously' > Confirm import
6.
Make sure that transport parameters are okay.
Add the following parameter to your transport
profile.
'/system_pf=/usr/sap//SYS/profile/DEFAULT.PFL'
This parameter simply tells sapevt where to look for
your DEFAULT.PFL. Check note 449270 for further information on this. Ensure you
have the other settings like:
rdisp/mshost =
rdisp/msserv = sapms
SAPSYSTEM = 00 (this is the system number)
Add system_pf paramter to transport tool via STMS. On
the left have
system_pf and on the right /usr/sap//SYS/profile/DEFAULT.PFL
After this, restart the system so that the new
parameter is taken into account by the system.
