"tp buffer prepared OK" Hangs on SPAM while applying basis support pack

[Former Member]

Hi,

I am trying to apply  BASIS patch to my ECC6.0 machine. oracle, windows 32 bit 

Current patch basis:  SAPKB70023, ABAP: SAPKA70023

Applying Patch BASIS  : SAPKB70024

But Im facing some issues  and  it gets hanged up at tp buffer prepared ok.

When i run  SPAM, After 2 minutes, the sys showme a message "tp buffer prepared OK", and dont end.

Cananyone help me to get out of this problem

Regards

Shafeeq

[Former Member · Accepted solution]

Dear ALL,

Thank you very much  for your answers and support,

I did  lot of things as suggested by you and finally i replace the kernel directory with new file same 700 version but latest downloaded from SMP.  and also i have pasted the new R3TRANS and TP in

/usr/sap/<SID>/DVEBMGS00/exe/  and this time it works and i have applied all the support packs

Successfully...!!!!

Thanks a million guys for your  quick support....!!!!

Regareds

Shafeeq

[Former Member]

Your problem has nothing to do with SAP NetWeaver Portal, maybe you should post to the correct space to begin with. or are much better suited for your discussion thread.

[Former Member]

Hi,

Check first your spam log.

Goto ® Log ® Queue in the initial screen of SPAM

Then check:

Check your transport system log STMS_IMPORT -> go to the import queue -> Menu "Go to" -> tp system log

STMS_IMPORT -> Goto -> tp System Log

Helpful link

http://scn.sap.com/community/netweaver-administrator/blog/2012/07/04/escaping-tough-moments-for-spam...

Kind Regards,

Johan

[former_member796061]

give the 777 permission to your buffer and try ....

[Former Member]

Shafeeq,

  You might get more help posting this question in other content areas. This forum is for SAP Portal  related topics and the knowledge base you require might not be  here.

-Kevin

[pavan_anjimeti]

Hi Shafeeq,

Have you checked import logs? Did you get any error messages?

Check below location logs:

\sapmnt\trans\log\SLOG<nnnnn>.<SID>

Regards,

Pavan

[Former Member]

Hi Pavan,

below are logs from   \sapmnt\trans\log\SLOG<nnnnn>.<SID>

ERROR: Connect to ECD failed (20130527160514, probably wrong environment).

ERROR: Connect to ECD failed (20130527162817, probably wrong environment).

START CMDIMPORT            ECD L      20130527175247              SHAFEEQ      sap-ec6-dev 20130527175247129  

STOP  CMDIMPORT            ECD L      20130527175304              SHAFEEQ      sap-ec6-dev 20130527175247129  

START DD IMPORT            ECD H      20130527175832              SHAFEEQ      sap-ec6-dev 20130527175831844  

STOP  DD IMPORT            ECD H      20130527180019              SHAFEEQ      sap-ec6-dev 20130527175831844  

START DD ACTIVATION        ECD A      20130527180022              SHAFEEQ      sap-ec6-dev                    

START tp_getprots          ECD J      20130527180023              SHAFEEQ      sap-ec6-dev                    

STOP  tp_getprots          ECD J      20130527180148              SHAFEEQ      sap-ec6-dev                    

STOP  DD ACTIVATION        ECD A      20130527180148              SHAFEEQ      sap-ec6-dev                    

START imp all              ECD        20130527180150              SHAFEEQ      sap-ec6-dev 20130527180150026  

INFO: event SAP_IMPORT_START triggered successfully

START DISTRIBUTION OF DD-O ECD S      20130527180152              SHAFEEQ      sap-ec6-dev 20130527180150026  

START tp_getprots          ECD S      20130527180152              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  tp_getprots          ECD S      20130527180247              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  DISTRIBUTION OF DD-O ECD S      20130527180247              SHAFEEQ      sap-ec6-dev 20130527180150026  

START TBATG CONVERSION OF  ECD N      20130527180247              SHAFEEQ      sap-ec6-dev 20130527180150026  

START tp_getprots          ECD N      20130527180247              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  tp_getprots          ECD N      20130527180302              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  TBATG CONVERSION OF  ECD N      20130527180302              SHAFEEQ      sap-ec6-dev 20130527180150026  

START MOVE NAMETABS        ECD 6      20130527180303              SHAFEEQ      sap-ec6-dev 20130527180150026  

START tp_getprots          ECD P      20130527180303              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  tp_getprots          ECD P      20130527180620              SHAFEEQ      sap-ec6-dev 20130527180150026  

STOP  MOVE NAMETABS        ECD 6      20130527180620              SHAFEEQ      sap-ec6-dev 20130527180150026  

START MAIN IMPORT          ECD I      20130527180621              SHAFEEQ      sap-ec6-dev 20130527180150026  

START imp all              ECD        20130527183638              SHAFEEQ      sap-ec6-dev 20130527183637563  

INFO: event SAP_IMPORT_START triggered successfully

INFO  TBATG CONVERSION OF  ECD N      not needed                  SHAFEEQ      sap-ec6-dev 20130527183637563  

START MOVE NAMETABS        ECD 6      20130527183640              SHAFEEQ      sap-ec6-dev 20130527183637563  

START tp_getprots          ECD P      20130527183640              SHAFEEQ      sap-ec6-dev 20130527183637563  

STOP  tp_getprots          ECD P      20130527183644              SHAFEEQ      sap-ec6-dev 20130527183637563  

STOP  MOVE NAMETABS        ECD 6      20130527183644              SHAFEEQ      sap-ec6-dev 20130527183637563  

START MAIN IMPORT          ECD I      20130527183644              SHAFEEQ      sap-ec6-dev 20130527183637563  

I have run SPAM from 000 client

( Import of queue for the :

Software Component: SAP_BASIS

SPAM status: (Error stop)

Import phase: IMPORT_OBJECT_LIST )

I have performed the steps below  also

stop SPAM .

Check TP or R3trans is active at OS level or not.

Check the latest SLOG file from \usr\sap\trans\log.

If no process for TP and R3trans and table TRJOB is empty then check content of table TRBAT if any entry exists delete it.

Then execute report (se38) RSTPTEST,

Ensure that all checks finishes fine (with a green sign)

Repeat SPAM

If still problem persists then do following

Stop SPAM.

Kill TP and R3trans.

On command prompt change your working directory to sap kernel folder

Now execute following

TP CLEANBUFFER SID pf= <Drive:\>\usr\sap\trans\bin\TP_DOMAIN_SID.PFL

I have performed the above steps as suggested some folks on forums

but again same issue it hangs at " tp buffer prepaid ok "

[former_member796061]

Please check the related logs like Slog 

STMS--->o to the import queue -> Menu "Go to" -> tp system log

Regards

Vijay

[Former Member]

HI Shafeeq,

Have you updated your tp executable to latest version? Try this first perhaps.

From another site.

The reason being program "RDDMASGL" running under User "DDIC" is not terminated.

Ensure to delete the entry from database. I deleted with the help of my ABAP friend via, debugging.

for your simplicity, here are the tables where you will have to delete the entry.

Database View: V_OP

Database Tables:TBTCO & TBTCP.

Delete the incorrect entry (with Job name - RDDMASGL, Status - Not Active) from these two tables.

The issue is resolved and the error "TP Buffer Prepared OK" flies away ----

Johan

[pavan_anjimeti]

Hi Shafeeq,

Have you tried with latest R3trans and TP tools? Please update these two files and then try again.

Did you configure STMS properly?

Your SP Upgrade stopped at IMPORT_OBJECT_LIST phase.

This phase imports the object lists for the Support Packages in the queue into the system. It may terminate for the following reasons:

TP_INTERFACE_FAILURE: The tp interface could not be called.

TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files(/usr/sap/trans/log).

COMMAND_FILE_IMPORT_FAILURE: The object list for one or more Support Packages could not be imported. You can find the source of error in the command file import log.

check TP System Logs.

Regards,

Pavan

[Former Member]

Hi Pavan,

As u suggested i will try with new TP and R3TRANS ,  one question before that

we are on Kernel 700 patch 333

Support packs are on 700 Release like SAPKA70023,SAPKB70023,SAPKE60079.

As our Support packs are on 700 Release , can we upgrade our kernel from 700 to 720 .

If we upgrade,  will it impact with the support packs as they are on 700 release .

I also assume  the same  TP Error

SPAM has stooped this time and got the error

TP_INTERFACE_FAILURE: The tp interface could not be called.

TP_FAILURE:

Could you please suggest shall i go and upgrade kernel to 720

Many Thanks...!!!

Regards

Shafeeq

[pavan_anjimeti]

Hi Shafeeq,

You can Upgrade kernel from 700 to 720 ,

Please check this SAP Note: https://service.sap.com/sap/support/notes/1636252

Backup the old kernel before doing Kernel upgrade.

Regards,

Pavan

[Former Member]

Have you checked for some errors?

Are there any issue with database space or file system space?