Skip to Content
author's profile photo Former Member
Former Member

Error in phase : Import_Proper , TP_STEP_FAILURE,Return code : 0008

When i was applying the patch SAPKA7011 Iam getting the following error.kindly help to resolve the issue.Plz reply ASAP

-


Error Description

The import was stopped, since an error occurred during the phase

IMPORT_PROPER, which the Support Package Manager is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Support Package -> Import queue from the initial

screen of the Support Package Manager.

The following details help you to analyze the problem:

- Error in phase: IMPORT_PROPER

- Reason for error: TP_STEP_FAILURE

- Return code: 0008

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

0008

Notes on phase IMPORT_PROPER

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):

Notes on phase IMPORT_PROPER

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):

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 07:06 PM

    Did you repeat <b>Support Package -> Import queue</b> step? And do you still get the error?

    regards,

    tamilboy

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 10:05 PM

    HI Vinay,

    Please go back to stms and repeat/restart that patch again. It should be good to go. Before that, I would recomend to check db02 tcode and see if there are any tabespaces are full. Over 90 & used space, not recomended.

    Thanks,

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.