on 04-13-2010 7:44 PM
hii all i was strucked " XPRA_EXECUTION" phase while applying support patch
ECC6.0 and oracle database
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_BUFFER_INCONSISTENCY
- Return code: 0008
- Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.
SAPKE60051)
Notes on phase XPRA_EXECUTION
The XPRAs and after-import methods are executed in this phase. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The system was unable to call the tp
interface.
o TP_FAILURE: The system was unable to execute the tp program. For
more information, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: The system was unable to execute the XPRA_EXECUTIO
tp step. To see the cause of the error in the method execution log,
choose Goto -> Log -> Queue.
o CANNOT_READ_BUFFER: The tp program was unable to open the relevant
buffer file. For more information, see the SLOG log file.
o CANNOT_MODIFY_BUFFER: The tp program was unable to modify the
relevant buffer file. For more information, see the SLOG log file.
Hello,
>- Error message: Pkgs. in queue don"t exist in the tp buffer (e.g. SAPKE60051)
This error message is often literally true: for some reason the import buffer of the system was changed or cleared so that the entry for the support package no longer exists there. Can you check the buffer of your system via STMS or "tp showbuffer"? If the package is indeed gone from the buffer, you will have to open a support call at SAPA and ask them to reset the queue so that you can reapply it. At this point in SPAM you can no longer reset the queue yourself.
Good luck,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I assume your system has a valid license and is registered at SAP.
In that case go to http://service.sap.com/MESSAGE and log on with your support (S) user. You can then create the message and send it to SAP. If you haven't got an S user yet or that user is not authorized to create messages, then you must ask your SAP administrator.
Support messages are not chargeable, unless SAP judges that the request is a consulting issue, in which case they will inform you first and request approval. The type of action needed here is a standard support intervention, I could find no trace of SAP ever charging for this in similar situations at other customers.
Regards,
Mark
chexck ST22 and probably SM37 for more info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hai eric ,
thank u very much for ur quick reply
As u said i checked in ST22 i find this dump
but i applied in dev system with the same level of kernal 185 -- there it worked fine
is there any kernal problem ..???
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 14.04.2010 01:14:14
Short text
Process terminated by signal 0.
What happened?
Error in the SAP kernel.
The current ABAP "SAPLSCSMBK_BCDATA" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An R/3 System process was terminated by an operating system signal.
-
Possible reasons for this are:
1. Internal system error.
2. Process was terminated externally (by the system administrator).
-
Last error logged in SAP kernel
Component............ "Taskhandler"
Place................ "SAP-Server MEDGGNERPDB_MDP_30 on host MEDGGNERPDB (wp
12)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 10744"
"
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.