Problem with import in STMS

[Former Member]

Hi all,

In one of our quality systems,the import of transports kind of goes to a hanged state.When we see RDDIMPDP, it says it has completed successfully, but inside we see the following log

Program RDDIMPDP is running in client 000

Header P: Acc. to TRBAT, job 13153501 is still running. Checking job status

Here it says from TRBAT, the job is still running.This entry remains for a long time.Only when we delete the entry in TRBAT with sm30,the transport imports happen normally.

This happens twice a day in a system.

Could somebody suggest on this.

Bharathwaj V

[Former Member]

Hi Bharathwaj,

Do following.

1. Configure RDDIMPDP jobs both in client 000 and business client as user DDIC (Login to client as DDIC, run RDDNEWPP in SE38, select High priority)

2. STMS -> Import Overview -> SID -> Menu Goto-> Import Monitor ->

Delete the entries related to those old transport request that are not

currently running. You can see the requests are in running status. To

delete right click and delete.

3. OS level using command "ps -ef | grep tp"

Kill these processes if any using the below command:

"kill -9 <pid>"

4. Check the contents of transport tables TRBAT & TRJOB via SE16.

Before starting a transport, these tables must be empty.Delete the entry using SM30/SM31.

regards,

kaushal

[Former Member]

Hi Kaushal,

1)RDDIMPDP is scheduled in both 000 and the client in which the problem is coming

2)We always delete that when an error comes,we make sure that there are no entries related to old transports still running when a new import is started.

3)Its a windows system and no other tp seemed to be running

4)We had cleared the tables TRBAT & TRJOB when ever we see that these entries dont go off automatically..

As all our efforts had failed ,we have rebooted the server.Presently we are not getting the error.Will keep u all posted in case this does not resolve or we find some other alternative.

Regards

Bharathwaj V

[Former Member]

hi

We did all that which was mentioned in my post and then restarted the SAP instance and then the error got resolved.

Regards

Bharathwaj v

[Former Member]

I seem to recall there being a file that was written to the trans directory during import (TPLOCK?) that would prevent transports. If you stop/restart SAP, it will drop that file, but you should be able to delete it manually if it is in that directory in error.

[Former Member]

Hi,

There's a lot factor that can make the transport stuck. It could be during that time the BGD workprocessor was full. You also can try by upgrade the TP and R3trans.

Thanks and Regards

**Point rewards is much appreciated

[Former Member]

Hi Ahmad,

No yar.All the WP were free and fine and upgrading R3trans and Tp also did not work.Any other option?

Bharathwaj V

[former_member204746]

open a case with SAP. you did everything that should have been done.