SAP Transport Troubleshooting guide

Below is my list of tasks to check when troubleshooting SAP transport hang issues.

Problem Keyword: Transport hangs troubleshooting and clears a transport list. Transport is stuck.

Basic transport troubleshooting.

1. Verify that there are no errors in the system log.
2. Execute transaction STMS ---> Select Import Overview-->Select SID
3. From menu > Go To > System Log
4. Correct if no issues in the log.

Known Issue - WARNING: \\SERVER\sapmnt\SIDtrans\tmp\SID.LOB is already in use(22720), I'm waiting 2 sec (20100322091720). My name: pid 10128 onSERVER (SIDadm)

Solution - Backup and delete the file '\\SERVER\sapmnt\SIDtrans\tmp\SID.LOB'. Add the transport again and perform import.

Known issue - Cannot find \\SERVER\sapmnt\SIDtrans\log\SLOGXX02.SID

Solution - Make sure that the 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 persists.

Known issue - Problems with job RDDIMPDP

Solution - Execute SE38 > Run program RDDNEWPP > Choose Normal priority. This will schedule a 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 the customer.

Clear the transport list and redo the transport

1. Execute transaction STMS
2. Import overview -> Goto -> Import monitor >'Monitor' -> right click on transport -> delete entry
3. Redo transport action. Proceed to the next step if not solved.
4. Clear the transport tables
5. Make sure that there are no stuck transports in your transport tables.
6. 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 the OS level.

1. Kill tp.exe OS process
2. Login to SAP server
3. Kill any TP.exe processes at the OS level.
4. Try again to add and import your request
5. Redo the transport action
6. Save transport resources.

It is SAP's recommendation that imports be done asynchronously rather than synchronously. By doing this you will be conserving System Resources.

In doing the import > Execution tab > Select 'Asynchronously' > Confirm import

The below is unlikely but could also apply.

1. Make sure that transport parameters are okay.
2. Add the following parameter to your transport profile '/system_pf=/usr/sap//SYS/profile/DEFAULT.PFL'
3. 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:
4. rdisp/mshost =?rdisp/msserv = sapms?SAPSYSTEM = 00 (this is the system number)
5. Add system_pf parameter 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

Please connect and?follow?me for the next upcoming informative articles.

Cheers :)