SPAM error while applying ABAP patch 13

[Former Member]

Hi all,

I was applying patches on neweaver system Windows oracle platform.

All patches till now successfully applied except patch 13 for ABAP and now situation is spam is running from alomost 24 Hrs and i have also tried to restart the same but all jobs RDD* jobs are running fine

except a job named <b>RDDEXECL</b> runs along with this particular patch import OCS_queue_import and both jobs runs for long long time.

I have never seen this job RDDEXECL before applying all patches , why this is appearing now and why patch is not proceeding further.

Can any body aware of this issue.

Best Regards

AjitR

[Former Member · Accepted solution]

Dear ajju,

RDDEXECL is the XPRA or Execution of user defined activities in the entire upgrade process. There is a specific log file for this which goes by the name

<SourceSID>R9<number>.<targetSID>

Please post the output of that file

Also, you will find the warnings or errors for this step in ALOG

Kindly post those too

Regards

Shantanu

[Former Member · Accepted solution]

SAPRA70013.MOB

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

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP101 transport order : "SAPKA70013"

1 ETP102 system : "MOB"

1 ETP108 tp path : "tp"

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

1 ETP198

2 EPU126XPost-import methods for change/transport request: "SAPKA70013"

4 EPU111 on the application server: "Cymobile"

2 EPU122XPost-import method "ENHS_AFTER_IMPORT" started for "ENHS" "L", date and time: "20071018203831"

1AETR012XProgram terminated (job: "RDDEXECL", no.: "20382300")

1AEPU320 See job log"RDDEXECL""20382300""MOB"

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP110 end date and time : "20071018214713"

1 ETP111 exit code : "12"

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

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

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP101 transport order : "SAPKA70013"

1 ETP102 system : "MOB"

1 ETP108 tp path : "tp"

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

1 ETP198

2 EPU126XPost-import methods for change/transport request: "SAPKA70013"

4 EPU111 on the application server: "Cymobile"

2 EPU122XPost-import method "ENHS_AFTER_IMPORT" started for "ENHS" "L", date and time: "20071018223851"

1AETR012XProgram terminated (job: "RDDEXECL", no.: "22385100")

1AEPU320 See job log"RDDEXECL""22385100""MOB"

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP110 end date and time : "20071018234551"

1 ETP111 exit code : "12"

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

Alog:

ALL MOB.ALL t 0000 20071017024723 DDIC Cymobile

SAPKA70013 MOB.ALL m 0000 20071017024735 SAPUSER DDIC Cymobile

SAPKA70013 MOB.ALL L 0004 20071017024759 SAPUSER DDIC Cymobile 20071017024742

SAPKA70013 MOB.ALL P 0004 20071017024816 SAPUSER DDIC Cymobile 20071017024805

ALL MOB.ALL t 0000 20071017025455 DDIC Cymobile

SAPKA70013 MOB.ALL m 0000 20071017025506 SAPUSER DDIC Cymobile

SAPKA70013 MOB.ALL L 0004 20071017025527 SAPUSER DDIC Cymobile 20071017025515

SAPKA70013 MOB.ALL P 0004 20071017025540 SAPUSER DDIC Cymobile 20071017025531

SAPKA70013 MOB.ALL H 0004 20071017025659 SAPUSER DDIC Cymobile 20071017025607

SAPKA70013 MOB.ALL A 0004 20071017025913 SAPUSER DDIC Cymobile

ALL MOB.ALL S 0000 20071017025927 DDIC Cymobile 20071017025917

ALL MOB.ALL 6 0000 20071017025952 DDIC Cymobile 20071017025917

SAPKA70013 MOB.ALL I 0004 20071017034147 SAPUSER DDIC Cymobile 20071017025917

ALL MOB.ALL t 0000 20071017083839 DDIC Cymobile

ALL MOB.ALL 6 0000 20071017084848 DDIC Cymobile 20071017083842

ALL MOB.ALL t 0000 20071017093945 DDIC Cymobile

ALL MOB.ALL 6 0000 20071017094050 DDIC Cymobile 20071017093946

ALL MOB.ALL t 0000 20071017215856 DDIC Cymobile

ALL MOB.ALL 6 0000 20071017221604 DDIC Cymobile 20071017215858

ALL MOB.ALL t 0000 20071018045219 DDIC Cymobile

ALL MOB.ALL 6 0000 20071018045857 DDIC Cymobile 20071018045220

ALL MOB.ALL n 0000 20071018065536 DDIC Cymobile 20071018045220

ALL MOB.ALL t 0000 20071018073844 DDIC Cymobile

ALL MOB.ALL 6 0000 20071018074057 DDIC Cymobile 20071018073846

ALL MOB.ALL n 0012 20071018075324 DDIC Cymobile 20071018073846

ALL MOB.ALL n 0012 20071018075353 DDIC Cymobile 20071018073846

ALL MOB.ALL t 0000 20071018203759 DDIC Cymobile

ALL MOB.ALL 6 0000 20071018203805 DDIC Cymobile 20071018203800

SAPKA70013 MOB.ALL R 0012 20071018214713 SAPUSER DDIC Cymobile

ALL MOB.ALL t 0000 20071018214841 DDIC Cymobile

SAPKA70013 MOB.ALL R 0012 20071018234551 SAPUSER DDIC Cymobile

ALL MOB.ALL t 0000 20071018234807 DDIC Cymobile

[Former Member · Accepted solution]

I am unable to find mentioned logs by you <SourceSID>R9<number>.<targetSID>

under /usr/sap/trans /log

[Former Member · Accepted solution]

Check in transport sub directory tmp

This is where these logs are saved first.

Then tp moves them if these jobs finish successfully (status F)

[Former Member · Accepted solution]

Right now i have stopped the process RDDEXECL and then ocs-import-queue process finished successfully , but when again i went to spam i get again import2 phase to run

this time i am runnign the same in dialog mode and now again <b>RDDEXEC</b>L job has started again and running in background

under usr/sap/trans/tmp latest updated log is only below

SAPRA70013.MOB

2 EPU126XPost-import methods for change/transport request: "SAPKA70013"

4 EPU111 on the application server: "Cymobile"

2 EPU122XPost-import method "ENHS_AFTER_IMPORT" started for "ENHS" "L", date and time: "20071019000546"

[Former Member · Accepted solution]

Shantanu,

particular log mentioned by you R9<number>.< does not exist for me under tmp directory , please let me know at earliest how to proceed further.

[Former Member · Accepted solution]

Ajju,

Can you check the entry in the TRJOB table from Se16 and see if there is anything related to this particular job?

[Former Member · Accepted solution]

Also, check wether there is enough space left in all the tablespaces in the DB

Regards

Shantanu

[Former Member · Accepted solution]

Se16 TRJOB details as below

FUNCTION JOBCOUNT

R 00054600

[Former Member · Accepted solution]

ajju,

The XPRA is used to start reports in the target system.

There seems to be some issue in starting one of the reports in the target system.

http://help.sap.com/saphelp_nw70/helpdata/en/84/29b0127a6011d3b505006094192fe3/frameset.htm

This is where you can find the log file info

http://help.sap.com/saphelp_nw70/helpdata/en/32/d08d3880b8e060e10000009b38f842/frameset.htm

see if this helps you

Regards

Shantanu

Message was edited by:

Shantanu Sardeshmukh

[Former Member · Accepted solution]

jobs logs are RDDEXECL

Job started

Step 001 started (program RDDEXECL, variant , user ID DDIC)

All DB buffers of application server Cymobile were synchronized

This action is not supported in system MOB

This action is not supported in system MOB

what else i can view as all rdd* jobs are runing fine , no log showing any imp info

[Former Member · Accepted solution]

These are the possible errors see if yousee any of these in the log files

XPRA_EXECUTION

This phase executes the XPRAs and after-import methods. It may terminate for the following reasons:

&#9675; TP_INTERFACE_FAILURE: The tp interface could not be called.

&#9675; TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.

&#9675; TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, read the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.

&#9675; CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, read the SLOG log file.

&#9675; CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.

Also see this link for further info

http://help.sap.com/saphelp_nw70/helpdata/en/32/d08d3880b8e060e10000009b38f842/frameset.htm

Regards

Shantanu

[Former Member · Accepted solution]

Can you also post the SLOG ?

[Former Member · Accepted solution]

Can you also post the SLOG ?

[Former Member · Accepted solution]

Slogs as below

ERROR SAPKA70013 MOB R 0012 20071018234551 SAPUSER DDIC Cymobile

STOP tp_getprots MOB R 20071018234553 DDIC Cymobile

STOP EXECUTION OF REPORTS MOB R 20071018234553 DDIC Cymobile

START EXECUTION OF REPORTS MOB R 20071018234808 DDIC Cymobile

START tp_getprots MOB R 20071018234809 DDIC Cymobile

ERROR SAPKA70013 MOB R 0012 20071018235959 SAPUSER DDIC Cymobile

STOP tp_getprots MOB R 20071019000009 DDIC Cymobile

STOP EXECUTION OF REPORTS MOB R 20071019000009 DDIC Cymobile

START EXECUTION OF REPORTS MOB R 20071019000342 DDIC Cymobile

START tp_getprots MOB R 20071019000342 DDIC Cymobile

[Former Member · Accepted solution]

what could be the reason , as non of the patches applied before this faced this kind of problem

should i take restart of entire system and see if it benefits

[Former Member · Accepted solution]

again i stopped background job RDDEXECL

and i got same error

The following details help you to analyze the problem:

- Error in phase: XPRA_EXECUTION

- Reason for error: TP_STEP_FAILURE

- Return code: 0012

- Error message: OCS Package SAPKA70013, tp step R, return code

0012

Is RDDEXECL job running in my system is normal thing , it should not run ?

why it is not getting finihsed , i guess something related to the same is the problem.

[Former Member · Accepted solution]

I just restarted job RDDEXECL now when patch aplication is stopped ,

and it finished within few seconds succesfully ,

but the same is again started when i did import queue from SPAM , but this time it is again not able to finish.

[Former Member · Accepted solution]

if i can execute job RDDEXECL successfully independently without any error ,

then why not job which start with patch application

below are 2 logs for same job

active job logs

Job started

Step 001 started (program RDDEXECL, variant , user ID DDIC)

All DB buffers of application server Cymobile were synchronized

This action is not supported in system MOB

finished job which repeat scheduled by me

Job started

Step 001 started (program RDDEXECL, variant , user ID DDIC)

All DB buffers of application server Cymobile were synchronized

Transport step R: Background job RDDEXECL ended correctly

Job finished

[Former Member · Accepted solution]

Dear Ajju,

"An error occurred executing an individual step. In this case the relevant line from the file ALOG is duplicated in the following eight columns (see Log File ALOG)."

You see the error messages in SLOG. Now try to search for the relevant error messages in the ALOG

Also, return code 12 means

Fatal errors have occurred, such as errors while reading or writing a file or unexpected errors within the database interface, in particular database problems.

I think you have an issue with the tablespace size or could be a corrupt block or could be anything

I think you need to do some database health checks

Regards

Shantanu

[Former Member · Accepted solution]

I will crosscheck evrything at database righ away

[Former Member · Accepted solution]

Let us know what you find

Regards

Shantanu

[Former Member · Accepted solution]

everything seems to be fine at Oracle level , no block corruption, no space problem

[Former Member · Accepted solution]

TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, read the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.

[Former Member · Accepted solution]

Log Overview for SAPKA70013

SAPKA70013 ABA Support Package 13 for 7.00

MOB System MOB

Generate Transport Information File 17.10.2007 02:55:06 (0) Successfully Completed

Import Request Piece List 17.10.2007 02:55:27 (4) Ended with Warning

Test Import 17.10.2007 02:55:40 (4) Ended with Warning

Import ABAP Dictionary Objects 17.10.2007 02:56:59 (4) Ended with Warning

ABAP Dictionary Activation 17.10.2007 02:59:13 (4) Ended with Warning

Import 17.10.2007 03:41:47 (4) Ended with Warning

Method Execution 19.10.2007 03:45:51 (12) Canceled

Import steps not specific to transport request

Execution of programs after import (XPRA)

Transport request : SAPKA70013

System : MOB

tp path : tp

Version and release: 370.00.01 700

Post-import methods for change/transport request: SAPKA70013

Post-import method ENHS_AFTER_IMPORT started for ENHS L, date and time: 20071019033926

Background job RDDEXECL did not end correctly

Execution of programs after import (XPRA)

End date and time : 20071019034551

Ended with return code: ===> 12 <===

[Former Member · Accepted solution]

ENHS means Enhancement Spots. These are points in the ABAP report (SAP Standards or otherwise) where a developer can add his part of the code to extract more out of that report.

Since we are talking of a Support pack, it is clearly an enhancement made to an SAP standard object.

I think the best way to deal with this is to generate an OSS message or look for notes specific to this problem as concerned to SP 13

Regards

Shantanu

[Former Member · Accepted solution]

Thanks Santanu for help , i have created OSS message with high priority and they adviced to restart database and start the same job manually before executing patch update from SPAM and this trick worked for me.

Thanks all once again .. points rewarded.

[Former Member · Accepted solution]

Hi Ajju,

I am having the Same problem can u please tell me what exactly you did to solve this problem step by step?

Please Reply As soon as possible.

Thanks in Advance,

Regards,

Rohit