Transport not working and failing

[former_member313733]

We have transport system setup between Dev and QA. It was working without problem so far and now we are seeing issues with Transport not making it to QA from DEV. Programmers were able to release the Transport but in SE01 transaction it is showing error below for that transport

-

---

"Export 05.02.2008 18:46:56 In process: Requires update"

-

---

I looked into the tp system log (STMS-GoTo - tp System Log) for the Dev and QA and I see entries like this below

DEV tp system log

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (520), I'm waiting 5 sec (20080205184229). My name: pid 3092522 on ssapddb

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (530), I'm waiting 5 sec (20080205184257). My name: pid 3092522 on ssapddb

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (540), I'm waiting 3 sec (20080205184337). My name: pid 3092522 on ssapddb

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (550), I'm waiting 2 sec (20080205184405). My name: pid 3092522 on ssapddb

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (560), I'm waiting 2 sec (20080205184439). My name: pid 3092522 on ssapddb

-

---

QA tp system log

WARNING: /usr/sap/trans/SRD/tmp/SRITMP.LOB is already in use (14230), I'm waiting 3 sec (20080205185941). My name: pid 3129482 on ss

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (14230), I'm waiting 4 sec (20080205185943). My name: pid 2347208 on ssapt

WARNING: /usr/sap/trans/SRD/tmp/SRITMP.LOB is already in use (14240), I'm waiting 5 sec (20080205190010). My name: pid 3129482 on ss

WARNING: /usr/sap/trans/SRD/tmp/SRI.LOB is already in use (14240), I'm waiting 5 sec (20080205190018). My name: pid 2347208 on ssapt

WARNING: /usr/sap/trans/SRD/tmp/SRITMP.LOB is already in use (14250), I'm waiting 4 sec (20080205190041). My name: pid 3129482 on ss

Have anyone experienced this issue before. Can someone pl help. Thanks

Regards

Gabriel

[Former Member]

Hi Gabrie,

A very common issue. First check if any import is still running in QA system. If not then do the following:

1. Kill all running TP processes at the OS level.

2. Delete all od TP log files in /usr/sap/trans/tmp. Look for the files that end with a <sid>.

3. In STMS go to import logs and delete any entires.

After that retry the import.

Regards.

Ruchit.

[former_member313733]

Hi Ruchit, thanks for your response. I did delete the files this morning and it started working. Did a couple of test and it transported ok. I am going to wait and watch it for a while. Had requested the users to do some testing also. Thanks again.

Regards

Gabriel

[Former Member]

Hi Gabrie,

i am getting the problem as u got, how did u solve ur porblem?

(the issue is Export 07.02.2008 12:24:02 In process: Requires update)

kindly let me know step be step answer to solve this issue..

thanks,

seshu.

[former_member313733]

Hi Seshu, looks like the transport writes the status to a file (<SID>.LOB ) in the tmp directory (/usr/sap/trans/<SID>/tmp) and after the transport is complete it will remove the entry from the file (this file size is 0 when transport is complete). I noticed that some process did not complete and the file was not empty. So I renamed the file and also killed the process. Then it started working. Thanks

Regards

Gabriel

[Former Member]

Hello Gabrie,

You are correct. However few additions. Whenever a transport gets imported there are several sub steps involved. The main import,generation,coversion runs etc. For each of these logs are written during the time of import in /usr/sap/trans/tmp directory. Once the steps are over the files get purged from this directory and eventually the entire log for import gets stored in /usr/sap/trans/logs.

Regards.

Ruchit.