Hi All,
We are doing the EHP4 upgrade in our landscape (MAXDB and Linux environment), things are fine so far and in the MAIN_NEWBAS/XPRAS (Downtime) phase were negative and thats stopped our proceeding with further phases.
In the XPRAUPG.ELG states that
The job RDDEXECL got failed and that causing the issue XPRA Error and return code is SAPR-701DWINBASIS.FSO
1AETR012XProgram terminated (job: "RDDEXECL", no.: "06091000") Long text: Cause Program "&V#&", which was started in the background, was terminated abnormally. System Response The system created a job log for the terminated program. What to do Proceed as follows: Log onto the system in which the program was executed. The system is specified at the beginning of the transport log. Then call transaction SM37 to display the job log. Enter "&V#&" as job name and "DDIC" as user name. Restrict the starting date to the starting date specified in the transport log. For the o
ther selection criteria, select only jobs with the status "cancelled". Then press <LS>Execute. A list of the jobs satisfying the selection criteria is displayed. You can display the log by pressing <LS>Job log. If the list contains several jobs, you can select the job with the ID " &V#&" with <LS>Display -> <LS>Job details or define further details for the selection criteria in the initial screen of transaction SM37. If the ABAP processor reports cancellation, double-clicking on the corresponding message in the job log branches to the display of the corresponding short dump
In SM21 it states that there is a runtime error
Short dump --> Syntax error in the program
In ST22
Syntax error in program SAPLSEDA
Error in the ABAP application program
The current ABAP program "CL_ENH_TOOL_FUGR============CP had to be terminated
because it has come across the statement that unfortunately cannot be exceuted
The following syntax error occured in program SAPLSEDA in include LSEDAU137
" IN
LINE 34
statement before ENHANCEMENT ...." was not concluded (period missing) "
the include program has last created and changed by SAP
Action taken
I tried to accept non severe errors and went through but still its not accepting it and also retried the phase certain times but no luck.
Anyone has come acrros this issue earlier? If so please do suggest me
Looking forward for your suggestions and replies
Thanks and Regards
Vijay
Hi,
Check SAP note 1462364.
Thanks
Sunny
Hi,
Thanks Sunny for the suggestions,
I have implemented this note before the upgrade as per SAP suggestions in the Extraction Roadmap itself and also implemented the pre manual implements as well
But still no luck so far,
Raised OSS message as well - lets see what they are going to suggest us
Regards
Vijay
Hi All,
The Issue got resolved
Solution : For some reason it was pointing to the old kernel and hence we have done the kernel upgrade to 701 followed by the system restart solved this issue
SAP support provided the solution ![]()
Regards
Vijay
Hi Vijay,
I faced same issue, how to solve this error. Because now in Downtime phase, how will restart the system, if we restart the server what about upgrade almost dead end reached at upgrade. I will affect or not pls explain.
Problem is solved.... thanks for all...