cancel
Showing results for 
Search instead for 
Did you mean: 

TP causes message in SLOG0706.SMP in log directory - SPAM Hung

Former Member
0 Kudos

Hi

I started the import of a queue of support packs in SPAM to the SMP system (Basis 7.00 , SM 4.0)

After running for a few hours overnight there was a TCP/IP problem and at the 3rd last package the SPAM showed an error in the IMPORT_PROPER phase the reason being TP_INTERFACE_FAILURE.

I restarted the import (obviously not the right thing to do!) and shortly afterwards although SPAM is showing it is doing the MAIN IMPORT step, nothing is happening - as the SLOG0706.SMP has lots of the following entries since I restarted the SPAM transaction:

WARNING: /usr/sap/trans/tmp/SAPKKITL417.SMP is already in use (1070), I'm waiting 4 sec (20070209074827).

My name: pid 11357 on <hostname> (smp03)

Looking at the pid, I find it is the OS job TP running and complaining about the SAPKITL417 which was the 3rd last package in the queue (last one to import is SAPKITL419).

There are 2 files in the tmp transport directory related to it from last night-

SAPIITL417.SMP *STMF SMPOFR 3083687 Feb 08 23:22

SAPKKITL417.SMP *STMF SMPOFR 314 Feb 08 23:20

The log directory has the following file since the SPAM was restarted:

Browse : /sapmnt/trans/log/P070209.SMP

ETP199X######################################

ETP172 MOVE OF NAMETABS

ETP101 transport order : "ALL"

ETP102 system : "SMP"

ETP108 tp path : "tp"

ETP109 version and release : "370.00.09" "700"

ETP198

ETP399XMove Nametabs started in batch mode.

ETP399 processing modeflag 'A'

ETP301 -


ETP364 Begin: Act. of Shadow-Nametabs ("2007/02/09 06:54:07")

ETP301 -


ETP301 -


ETP338XActivation of Shadownametabs

ETP301 -


ETP301 -


ETP365 "0" Shadow-Nametabs activated

ETP362 "0" Shadow-Nametab activations failed

3 ETP362 "0" Shadow-Nametab activations failed

2 ETP364 Begin: Act. of Shadow-Nametabs ("2007/02/09 06:54:07")

2 ETP366 End: Act. of Shadow-Nametabs ("2007/02/09 06:54:07")

In SM12 there are 2 lock entries from when the import started yesterday

000 POWEM 08.02.2007 E PAT01 #################### 1 0

000 POWEM 08.02.2007 E CWBNTHEAD 9999999999#### 0 1

In PAT01 there are entries for each package in the queue and the reason field has TP_INTERFACE_FAILURE

Table: PAT01

PATCH SEQUENCE STEPNAME

SAPKA70009 003 IMPORT_PROPER

SAPKA70010 010 IMPORT_PROPER

SAPKB70009 001 IMPORT_PROPER

SAPKB70010 002 IMPORT_PROPER

SAPKIPYJ79 004 IMPORT_PROPER

SAPKIPYJ7A 011 IMPORT_PROPER

SAPKITL417 006 IMPORT_PROPER

SAPKITL418 009 IMPORT_PROPER

SAPKITL419 015 IMPORT_PROPER

SAPKNA7006 007 IMPORT_PROPER

SAPKNA7007 013 IMPORT_PROPER

SAPKU50006 008 IMPORT_PROPER

SAPKU50007 014 IMPORT_PROPER

SAPKW70009 005 IMPORT_PROPER

SAPKW70010 012 IMPORT_PROPER

e.g.

PATCH SAPKITL417

SEQUENCE 6

STEPNAME IMPORT_PROPER

STEPCOND ?

RET CODE

MESSAGE

REASON TP_INTERFACE_FAILURE

SCENARIO S

VALID CONJ 1

What should I do to fix this?

thanks

Michael

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

We are currently struck with the same error message and SPAM is hung. The message in SLOG bieng" WARNING:
rpmsap8\sapmnt\trans\tmp\SAPKKITL414.SM1 is already in use (1200), I'm waiting 2 sec (20070222184527). My name: pid 7556 on rpmsap8 (sm1adm)

".

But I am not able to rename the file currently SAPKKITL414.SM1. It says file is already being used by other program.

Please Advice at the earliest!

Antarpreet

Former Member
0 Kudos

It is interesting that the user is reported as SM1ADM rather than the work process user profile SM1nn, which indicates you either have a session logged on to the server with profile SM1ADM that has the lock - perhaps from a WRKLNK command or TP from command line?

Try doing WRKUSRJOB SM1ADM.

Former Member
0 Kudos

Problem solved-

solution is to rename the file in /usr/sap/trans/tmp that is causing the SPAM import to hang -

this was

SAPKKITL417.SMP

After you do this, the import continues again and the "waiting for x sec" messages no longer appear in the SLOG0706.SMP log file.

Former Member
0 Kudos

Hi Michael,

This may be due to sql problem, plese refer note 3023 further reference.

Cheers,

Shyam