TMS queue not working

[Former Member]

Yesterday while importing a transport into one of our test systems the server restarted unexpectedly. When I restarted SAP and logged bck in it looks like the transport was still running but it had completed. I deleted the status in the transport monitor to clear this. The code has gone into the system so the transport did complete as it also says in the transport log but there isn't a green tick. If I try to run another transport in it just locks up and doesn't do it.

I've tried redistributing the transport config and restarting SAP but nothing works. Its a 46c system. Any idea's?????????????????

[Former Member]

Chris, try this...

1. Kill any TP processes at the OS level, if you do not have an import

actively running.

2. Using transaction stms-> Import overview -> Goto -> Import monitor

execute :

'Monitor' -> 'Delete old entries'

3. While being logged in as DDIC in client 000, run report RDDNEWPP in

trx se38. You will also need to do this for all client that you

transport to or from.

4. Check and delete (using trx SE14) any entries found in the following

tables:

TPSTAT

TRJOB

TRBAT

If the Import Monitor or table TPSTAT does NOT contain

entries any more, you can delete the entries of tables TMSTLOCKR and

TMSTLOCKP.

Derek

[Former Member]

Derek, that hasn't worked, it did sound promising though.

The transport executes then gets to the stage where it says 'tp buffer prepared OK'

and doesn't get any further. We then have to force the transport to end.

As well as not being able to import transports into the test system we cannot release transports from the dev system either.

Any more ideas?

[Former Member]

Hi Chris,

Check the TMS configuration once, if you delete entry's in TRBAT,TRJOB tables it should work.

Regards,

Hari.

[Former Member]

Chris, check the tp system log, you probably either 1 - dont have background processes or 2 - your tp BTC jobs are not running. Check the RDD* jobs are running.

Other one is the tp you are trying to import has a lock at the OS, you'll find it in the tp system log. If it is a lock, rename the lock file and re-import.

Derek

[Former Member]

Chris,

I hope you have made sure that the tbles TPSTAT, TRJOB, TRBAT are empty. Also please make sure there is no .LOB file in \trans\tmp. If that exist make sure you delete it and freshly schedule RDDIMPDP job and then try transporting

Cheers!

Bidwan

[Former Member]

Verbatim Bidwan

[Former Member]

Derek, should I have deleted the entries in the tables in the transport domian controler or the system that isn't working? As in our domain controler is the production system and the problems have been in the test system.

Message was edited by:

Chris Soden

[Former Member]

On the system that the transport is failing on.

[Former Member]

System in which the transport is failing in....

[Former Member]

Tried everything and nothing so far. Not sure where this lock entry at OS should be though and you do mean the log in \usr\sap\trans\log don't you??

[Former Member]

Hi Chris,

Check the lock entryin /trans/log , if you delete entry's in TRBAT,TRJOB tables it should work, check in the Domain Contraller as well. It's need not be on the same system.

Regards,

Hari.