Error while importing support package SAPKB70016

[Former Member]

Hi all,

While importing the Support Package SAPKB70016, Support Package Manager throws an error.

- Error in phase: IMPORT_PROPER

- Reason for error: TP_STEP_FAILURE

- Return code: 0008

- Error message: OCS Package SAPKB70016, tp step "I", return code

0008

[Former Member · Accepted solution]

1) For the problem TP_BUFFER_INCONSISTENCY.

In PAT01, PAT03 and PAT10 tables

delete the entries with status ='?'.

This will Reset SPAM.

2) For the problem TP_STEP_FAILURE.

a) Delete the Japaniese language entries from table RSMPTEXTS

You can identify the records in SE11 using

PROGRNAME = BTFR_COPY and BTFR_COPY_TRALA

LANGUAGE = J

b) Run reports: SAPRSEUF (NO Parameter Required), SAPRSEUG (with param 'X')

c) Open RSMPTEXTS in display mode in SE11, Then Select

Utilities -> Database objects -> Database utility -> Activate and adjust the database.

After that Extras->force conversion

Now start importing SAPKB70016 from the beginning.

[Former Member · Accepted solution]

Hello Srinivasan

The message has been resolved but I want to clerify that your answer not belongs to actual problem!

The inconsistencies arised during the import problem which could be due to any dependency not followup

Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP

Please followup the above notes to see the pre-requsites and recommendation for the

SAPKB70016 level 16.

Regards

[Former Member]

Hello,

please read the detailed log messages in SAP, or the SLOG, ULOG, ALOG files

in /usr/sap/trans/log directory for more detailes.Any way you may just try the import again. That will cause no harm, and may

succeed.

manually reset &H3D the buffer using the following steps,In Se37,Use the function module OCS_RESET_QUEUE -> Single Test

with the parameters IV_TOOL&H3D3DSAINT, IV_FORCE&H3D3DX Deleted all the files from \usr\sap\trans\tmp.Please make sure that &H3D there is no TP process or R3trans process running in the system at Operating system level. If any process exist, Please kill the process. Scheduled the program RDDIMPDP using Report RDDNEWPP in se38.Then restart the import again and the problem will solve.Hope this will help in solving your problem.

BR,

kk

[Former Member]

Still the issue is not resolved.

I have deleted the transport queue in STMS now i am getting this error.

The following details help you to analyze the problem:

- Error in phase: DDIC_IMPORT

- Reason for error: TP_BUFFER_INCONSISTENCY

- Return code: 0008

[Former Member]

Hi ,

This clearly says there is inconsistency in BUFFER .So please check your buffer once .Please attach logs from tmp where it will tell you exactly where the error is?

Thanks..

Mohit

[Former Member]

Hi,

the buffer is not cleared yet.

At o/s level check the buffer

>tp showbuffer <sid>

then if you will see the request there you can delete that from buffer by command

tp delfrombuffer <request> <sapsid>

Regards

Ashok Dalai

[Former Member]

In this phase repository objects and table entries are imported. This

phase can terminate due to the following reasons:

o TP_INTERFACE_FAILURE: The tp interface could not be called.

o TP_FAILURE: The program tp could not be executed. For more

information on this, see the SLOG or ALOG log file.

o TP_STEP_FAILURE: A tp step could not be executed. To find the cause

of the error, see the appropriate log, such as the import log.

If the cancelation message contains a tp step 6, N or S, the step in

question is independent of the transport request. You can find these

logs under the node Import steps not specific to transport request

in the log overview.

Alternatively, you can find these logs in the following files in the

log directory of your transport directory (usually:

/usr/sap/trans/log):

- tp Step 6: P<YY><MM><DD>.<SID>

- tp Step N: N<YY><MM><DD>.<SID>

- tp Step S: DS<YY><MM><DD>.<SID>

You can display these files using the report RSPUTPRT or by calling

transaction AL11.

A prerequisite of the Support Package Manager is that the Change and

Transport System (CTS) is configured correctly. For more detailed

information, read the online documentation available from Help -> SAP

Library -> mySAP Technology Components -> SAP Web Application Server ->

Change and Transport System ."

[Former Member]

I could find the log relevant to tp step 6: P <YY> <MM> <DD> . <SID>

Still its of no use. It showing exit code as 0.

Please find the extract of the log below

1 ETP199X######################################

1 ETP172 MOVE OF NAMETABS

1 ETP101 transport order : "ALL"

1 ETP102 system : "ID6"

1 ETP108 tp path : "tp"

1 ETP109 version and release : "372.04.57" "700"

1 ETP198

3 ETP399XMove Nametabs started in batch mode.

2 ETP399 processing modeflag 'A'

2 ETP301

2 ETP364 Begin: Act. of Shadow-Nametabs ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP338XActivation of Shadownametabs

2 ETP301

2 ETP301

3 ETP365 "0" Shadow-Nametabs activated

3 ETP362 "0" Shadow-Nametab activations failed

2 ETP364 Begin: Act. of Shadow-Nametabs ("2009/08/27 20:34:02")

2 ETP366 End: Act. of Shadow-Nametabs ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP399 processing modeflag 'W'

2 ETP301

2 ETP347XActivation of Shadownametabs (delete) with DDL

2 ETP301

2 ETP301

2 ETP301

3 ETP368 "0" Shadow-Nametabs deleted, DDL executed

3 ETP369 "0" Shadow-Nametab deletions failed

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP370 End: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP399 processing modeflag 'X'

2 ETP301

2 ETP347XActivation of Shadownametabs (delete) with DDL

2 ETP301

2 ETP301

2 ETP301

3 ETP368 "0" Shadow-Nametabs deleted, DDL executed

3 ETP369 "0" Shadow-Nametab deletions failed

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP370 End: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP399 processing modeflag 'Y'

2 ETP301

2 ETP347XActivation of Shadownametabs (delete) with DDL

2 ETP301

2 ETP301

2 ETP301

3 ETP368 "0" Shadow-Nametabs deleted, DDL executed

3 ETP369 "0" Shadow-Nametab deletions failed

2 ETP367 Begin: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP370 End: Act. of Shadow-Nametabs (delete) with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP301

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP399 processing modeflag 'F'

2 ETP301

2 ETP330XActivation of Shadownametabs with DDL

2 ETP301

2 ETP301

3 ETP361 "0" Shadow-Nametabs activated, DDL executed

3 ETP362 "0" Shadow-Nametab activations failed

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP301

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP301

2 ETP399 processing modeflag 'V'

2 ETP301

2 ETP330XActivation of Shadownametabs with DDL

2 ETP301

2 ETP301

3 ETP361 "0" Shadow-Nametabs activated, DDL executed

3 ETP362 "0" Shadow-Nametab activations failed

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/08/27 20:34:02")

2 ETP301

1 ETP172 MOVE OF NAMETABS

1 ETP110 end date and time : "20090827203402"

1 ETP111 exit code : "0"

1 ETP199 ######################################

Edited by: Caritor SAP on Aug 27, 2009 8:51 PM

[Former Member]

TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.

If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.

You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):

tp step 6: P<YY><MM><DD>.<SID>

tp step N: N<YY><MM><DD>.<SID>

tp step S: DS<YY><MM><DD>.<SID>

To display these files, run report RSPUTPRT or call transaction AL11.

Complete info [http://help.sap.com/saphelp_nw04/helpdata/en/7e/c6c2ad98a711d2b429006094b9ea64/content.htm]