When releasing a transport it stays constantly in 'export' status

[Former Member]

Hi

We've recently done a refresh of our BI QA system. Now, whenever we create a new transport in the DEV environment, when we try to release it the status stays as 'Export' and says 'In process: Requires update'. If you refresh then the timestamp updates but it never comes out of this export status. Also the transport never appears in the QA queue/buffer (you can manually add it however using 'extras->other requests->add').

We can see tp processes hanging on the UNIX server. We have killed these and checked tables TRBAT and TRJOB - these are empty. There were however entries in TPSTAT, so we also deleted these. We also ran 'tp getprots <SID> pf=<profile>'. We have done this tidy up process several times and ONCE the transport actually appeared in the QA queue - but not other times. Always, the status stays in 'export'.

I have also ran RDDNEWPP in client 000 to reschedule RDDIMPDP - not helped.

We have removed the QA system from the domain controller and added back in. We have checked all the parameters match up between DEV and QA (CTC is set to 0). There is nothing in the tp log until we issue a tp getprots command manually.

SAP would probably advise us to upgrade tp (we are on version This is tp version 372.04.36 (release 700, unicode enabled) patch 165) - but before we have to resort to this, does anyone else have any ideas?

Thanks

Ross

[Former Member · Accepted solution]

Ross,

Have a look at following notes:

Point 4:

[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=556941]

[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=71353]

Hope this helps.

Manoj

[Former Member]

HI

Seven Steps When you get stuck with Truck ICON.

1. Kill any TP processes at the OS level, if you do not have an import actively running. Then in STMS -> Import Queue -> Import Monitor -> Delete the entries related to this transport request. You can see the requests are in running status. To delete right click and delete.

2. 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 in accordance of note 11677 Kindly goto SE38, use RDDNEWPP to schedule RDDIMPDP on client 000 and other client with DDIC user(refer note 71353 and 11677).

3. Check and delete any entries found in the following tables:

TMSTLOCKR

TMSTLOCKP

TPSTAT

TRJOB

TRBAT

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

5. In transaction Al11, Directory: /usr/sap/trans/tmp, check for semaphore with file extension .LOC/.LOB, try to rename or move this files to another directory. Refer to note: 12746.

6. If the Import Monitor or table TPSTAT does not contain entries any more, you can delete the entries of tables TMSTLOCKR and TMSTLOCKP.

7. Update your R3trans and your tp to latest available.

Then restart the import.

Also delete entry from usr/sap/trans/tmp

Regards

Uday

[Former Member]

Thanks both for the detailed responses... I have tried all these now but unfortunately it hasn't helped. I will look at upgrading tp/R3trans now and see if that helps...

[Former Member]

Did a tp and R3trans upgrade to the latest version - still not helped. Have raised an OSS message with SAP.

[Former Member]

.

[Former Member]

Hi

Have you done POST INstallation Activities for Tranport Organizer (SE06) as part of Post Refresh Activity?

Also, Can you please check the transport jobs in SM37. May be checking the STMS configuration connection check is worth understanding the problem.......

Hope this helps...

[Former Member]

Not sure why Manoj's answer is blank; I got an email and it was:

Message: Hi,

Hope your configuration is ok including transport routes. Please check attached note while you are waiting for the reply from SAP.

https://service.sap.com/sap/support/notes/71353

Manoj

Manoj, please see earlier posts - I have already looked at 71353!!

Configuration and transport routes all look fine; connection/tp checks etc work okay.

[Former Member]

Hi Sree

SE06 was indeed ran as per post copy tasks. The odd thing is we have done several refreshes all at the same time following the same documentation and have not had this problem anywhere else...!!

I have already checked the SM37 jobs (RDDIMPDP as mentioned by Uday), all looks fine, I have rescheduled/reran etc.

STMS checks of routes/tp/config etc etc all work fine.

Ross

[Former Member]

Fixed it! My colleague spotted that the transport route diagram looked a bit wrong, especially compared to our ECC landscape. So I tidied it up and explicitly set client numbers (as some had changed since system refresh and thought this may be an issue), distributed, tided up (killed old tp processes and cleared TPSTAT) and tried a new transport release - worked!!!

Cheers

Ross