AIX 46C tp is waiting for nonexistent SLOGxxyy.PP1.LOC

[martin_E]

When the tp executable is run, its waiting on the SLOG file in /usr/sap/trans/tmp. There is no other tp process running on

this or other servers in the landscape. There is nothing written to the SLOG file, and there is nothing else using the SLOG

file (see below). I have already run an slibclean to clean up file buffers etc.

I have checked the system against OSS Notes 12746, 71353, 26966, 449270, and related messages, but have not been able

to resolve the problem. Note that there is nothing in the TRBAT and TRJOB tables.

Why does tp think the SLOG1010.PP1.LOC is in use and what can I change to get the tp command to run correctly ?

server01> cd /usr/sap/trans/bin
server01> tp import DP1K909710 PP1
This is tp version 305.13.24 (release 46D) for ANY database
/usr/sap/trans/tmp/SLOG1010.PP1.LOC is already in use (1), I'm waiting 5 sec (20100312134616). My name: pid 56622 on zuxdc24 (pp1adm)
/usr/sap/trans/tmp/SLOG1010.PP1.LOC is already in use (2), I'm waiting 5 sec (20100312134621). My name: pid 56622 on zuxdc24 (pp1adm)
....
server01> fuser /usr/sap/trans/tmp/SLOG1010.PP1.LOC
/usr/sap/trans/tmp/SLOG1010.PP1.LOC:
zuxdc24:pp1adm 77> cd ../tmp
zuxdc24:pp1adm 78> ls -la
total 16
drwxrwxrwx   2 3210     sapsys          512 Mar 12 13:35 .
drwxrwxr-x  21 3262     sapsys         3072 Mar 11 12:08 ..
-rw-rw-rw-   1 3210     sapsys            0 Mar 11 12:06 PP1.LOB
-rw-rw-rw-   1 3210     sapsys            0 Mar 11 16:22 SLOG1010.PP1.LOC
server01>

Thanks in advance

Martin

[Former Member]

Hi,

The issue would also have been resolved by just clearing files from the tmp directory. There is no need to delete the TMS for this kind of issue.

If your issue is solved then close the thread by marking answered.

Regards,

Sharath

[martin_E]

Hi Sharath,

When the problem first occurred, the /usr/sap/trans/tmp directory was empty - I put the *LOB and *LOC files in the directory, in an attempt to get the tp process to recognise they were there and not in use.

I know it doesn't make sense, but I was getting desperate - we had a major release into production to do for the weekend, and this transport was one of the required .changes.

thanks for your help.

[martin_E]

For what its worth, I've corrected the effect of the problem by reinstalling the TMS.

I deleted the other two systems from the domain controller (I made sure I retained the existing Transport layers and Transport Routes).

I created a 3 system landscape, then went into the Transport Routes part of STMS and restored the previous configuration.