XPRAS_UPG phase terminated
Hi all,
I am doing CU&UC "Combined Upgrade & Unicode Conversion", during Upgrade "XPRASUPG_" phase terminates, when checking in SM37, can see that RDDEXECL report was terminated, I executed the report manually in SE38 with success, and repeated the phase again, unfortunately with same result.
EXPRASUPG LOG
root@kvxi010 /usr/sap/put/log # view XPRASUPG.ELG
"XPRASUPG.ELG" [Read only] 51 lines, 2208 characters
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG1.X82
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08270700")
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.
"XPRASUPG.ELG" [Read only] 51 lines, 2208 characters
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG1.X82
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08270700")
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 other 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.
1AEPU320 See job log"RDDEXECL""08270700""X82"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
Is there someone who can help me.
Thanks for help in advance
hello,
pls check that there are enough batch workprocesses
available. In transactino SM37 you can see the joblogs
of the failed jobs.
hope this helps.
kind regards,
andraes
Similar Messages
-
Urgently Upgrade Stop In XPRAS_UPG Phase
Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
<b>Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:</b>
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
Remaining change request found in buffer TVD.
Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
<b>XPRASUPG.ECO and R3up.ECO</b>
the problem is with the <b>RDDEXECL</b> JOB. Which is in the status <b>CANCELED</b>
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
<b>Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
</b>
The conversion of some code pages is not supported.
<b>What happened? </b>
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
<b> 'CX_SY_CODEPAGE_CONVERTER_INIT'</b>, was neither
caught nor passed along using a RAISING clause, in the procedure <b>"READ_TEXTLINES" "(FORM)"</b>.
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
<b>We saw this note:</b>
<b>122597</b> Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
<b>676135</b> Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
<b>This are the logs:</b>
<b>XPRASUPG.ECO</b>
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
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 other 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.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
<b>R3up.ECO:</b>
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree CardenasHi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas -
Hi
we are at Downtime Road map step with MAIN_NEWBAS/XPRAS_UPG phase of ECC6.0 Including EHP4 SR1, where we have noticed its running since 16hours without any log entry in Upgrade Directory but can see there is a background Process Running.
Please advise
Phase XPRAS_UPG:
Deleting file E:\usr\sap\UPS\upg\abap\log\PHASES.LOG
Deleting file E:\usr\sap\UPS\upg\abap\log\TOOLOUT.LOG
Deleting file E:\usr\sap\UPS\upg\abap\log\IMPDP.LOG
Copying file E:\usr\sap\UPS\upg\abap\buffer\XPRASUPG.BUF to E:\usr\sap\UPS\upg\abap\buffer\UPS
SAPup> Starting subprocess tp.exe with id 5876 at 20091005151956
EXECUTING E:\usr\sap\UPS\SYS\exe\run\tp.exe pf=E:\usr\sap\UPS\upg\abap\bin\XPRASUPG.TPP put UPS
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Environment: Path=C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;E:\usr\sap\UPS\SYS\exe\run
Environment: auth_shadow_upgrade=0
Environment: dbs_mss_schema=ups
This is E:\usr\sap\UPS\SYS\exe\run\tp.exe version 372.04.40 (release 701)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)Hi Sunny,
I cannot see any log created since XPRAS phase started, Latest log was created 16hours before in Upgrade directory.
Below is the phase log which started on 05 oct 15.19 and the latest is 05 oct 16.44.
1 ETQ201 Entering upgrade-phase "XPRAS_UPG" ("20091005151953")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_mss_schema=ups
4 ETQ399 auth_shadow_upgrade=0
4 ETQ380 computing toolpath for request "TP_DEFAULT"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_SYS"
4 ETQ383 translates to path "E:\usr\sap\UPS\SYS\exe\run"
4 ETQ399 Set environment for standard connect:
4 ETQ399 ENV: dbs_mss_schema=ups
4 ETQ399 ENV: auth_shadow_upgrade=0
4 ETQ399 Set RFC variables for standard connect:
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Set tool parameters for standard connect:
4 ETQ399 default TPPARAM: DEFAULT.TPP
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_NEWBAS/XPRAS_UPG'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'XPRASUPG.BUF'
2 ETQ399 Arg[1] = 'XPRASUPG.TPP'
2 ETQ399 Arg[2] = 'XPRASUPG.TP0'
2 ETQ399 Arg[3] = 'XPRASUPG.ELG'
2 ETQ399 Arg[4] = 'AFTXPRAS.BUF'
Please advice..
regards
Anilsai -
Upgrade in hangs in XPRAS_UPG phase
We are experimenting an hang situation during the upgrade from 46C sandbox system to ECC6 Sr3, latest patches.
The upgrade is in phase XPRAS_UPG, and in Sap we see the job RDDEXECL running from very long time (more than 1 days); in SM50 we see the several programmes (SAPLSTXG and others) working with sequential read, update or delete actions on the table STXL.
But neither the job log is updated or the logs into the put directory on the filesystem.
Before the upgrade we applied the note 558197 (that one for the script dba_ind_column,....), and we enlarged the shared_pool_size and shared_pool_reserved_size as described into the upgrade guide.
We run also the del_priv_ind script as suggested by Prepare.
We try also to stop and restart the upgrade, but nothing change; it continue to stay in hangs on the STXL table in phase XPRAS_UPG.
The latest row of the SAPR700ZG1.SID is :
"Post-import method 'AFTER_IMP_FORM' started for FORM 'L' ....."
Is the first time we see this situation during an upgrade.
Any suggestion ?Hi,
Is this your first test upgrade in the Landscape? How many records the table has?
Is not uncommon that XPRAS_UPG takes a long time, in one system I won´t forget the downtime took 72 hours running ! and most of this time was during XPRAS_UPG so if this is taking so long and it is working it will be better to let it finish and analize the upgrade report. Normaly when some processes are running the log files are not updated because they don´t trace all work done by the processes. Have you analize if Hard disks are working more than normal during this phase? if so then let if finish and you will be able to see why it took so long.
Good luck -
Error in XPRAS_UPG Phase for report RSR_VARIANT_XPRA
Upgrade from 4.6C to SAP ERP 2005 SR2 with all support packs
During execution of background job for RSR_VARIANT_XPRA, TP terminates with exit code "12" and halts the upgrade process.
On manual execution report throws error message Program class RSR_RECHERCHE does not exist. The TRKORR number for this is SAPR700XP4.
Any help on this will be really appreciated. I have tried to set the lock value to 2 /7 but same result.
Regards
Rohit ChowdharyHi,
We've faced the same problem during upgrade to ECC6.0.
Since i've read your message (I couldn't find out which was the program), debugging RSR_VARIANT_XPRA i've found there's a missing entry in table RSSGTPCLAT. If you included it the phase runs again.
The fields are:
PROGCLASS: RSR_RECHERCHE
CLIDEP: (blank)
GENFLAG: X
SUBC : 1
TEMPLATE : RSRDUMMY
TITLE :
Hope this help you.
Regards. -
Error in XPRAS_UPG phase on SCPR_FLDV_TAB
Hi,
Has anyone experienced this error before when upgrading to ECC 6.0?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZDA.FR1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "00273700")
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.
etc.etc.
When I then go to SM37 to look at the job log i find an ABAP syntax error message that generated a short dump:
Runtime error SYNTAX_ERROR
Datum en tijd 16.11.2007 00:24:27
Korte tekst
Syntaxfehler im Programm "%_CSCPR ".
Wat is er gebeurd?
Error in the ABAP Application Program
The current ABAP program "SAPLSCPRPR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Im Programm "%_CSCPR " ist im Include "%_CSCPR " in Zeile 17
der folgende Syntaxfehler aufgetreten:
"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined i"
"n the Dictionary control structure introduced with "CLASS" . . . . . ."
| Autor und letzter Änderer des Includes sind:
Autor "SAP "
| Letzter Änderer "SAP "
So for some reason this type SCPR_FLDV_TAB is defined in two places and SAPup won't allow me to ignore it.
I have opened a message with SAP on this problem as well, but this system is due to go live on Monday so any help that would speed up the resolution process will be very much appreciated.
Kind Regards,
SanderHi ,
Please refer to note 122597 and 816057 i request you to check the job logs in sm37 as well.
Regards,
iqbal -
SAINT in Import proper phase terminated
Hi, we have done a system copy from PRO. to TEST system (Win, Oracle). Now we have to apply Support Packs to TEST system, but the SAINT is locked in IMPORT_PROPER, it is same in PRO System as well Locked in IMPORT_PROPER.
It says that BPERP05 not in buffer.
Any suggestion welcome to clear the SAINT.
Thanks
VikramWhat SP are you applying?... Whats the error on the logs?....
No enough info.
Read the "Rules of Engagement"
Regards
Juan -
Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative
Hi Gurus,
am upgrading from ecc 6.0 to ehp5 on dual stack system OS:Windows 2003 DB:oracle 10.2.0.2
i got below error in the MAIN_NEWBAS/XPRAS_UPG phase
XPRASUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-500AGINCPRXRPM.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14152200")
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 other 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.
1AEPU320 See job log"RDDEXECL""14152200""IJE"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server admin0001 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
Dump at ST22:
Error analysis
The following syntax error was found in the program
CL_DPR_TASK_O=================CP :
"Formal parameter "IV_PLANSTART" does not exist."
please help me solve
Thanks,
VenkatHi Sunny,
here is dump details..
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_DPR_TASK_O=================CP
Application Component PPM-PRO-STR
Date and Time 06.12.2011 16:34:41
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transaction ID...... "04FA1FE12F6DF16DB7E400145E69764F"
EPP Whole Context ID.... 34454438393637453445443839363745
EPP Connection ID....... 34454442374143323445444237414332
EPP Caller Counter...... 1
Program............. "CL_DPR_STATUS_CHANGE_OBSERVER=CP"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_DPR_TASK_O=================CP " in include
"CL_DPR_TASK_O=================CM021 " in
line 74:
"Formal parameter "IV_PLANSTART" does not exist."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program
CL_DPR_TASK_O=================CP :
"Formal parameter "IV_PLANSTART" does not exist."
Information on where terminated
Termination occurred in the ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" -
in "SET_HANDLER".
The main program was "R_DPR_PROJECT_ROLES_XPRA ".
In the source code you have the termination point in line 12
of the (Include) program "CL_DPR_STATUS_CHANGE_OBSERVER=CM00A".
The program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Thanks in advance
Venkat -
How to change the phase by 90 deg of a sine wave
Hi
Does any one know how to change the phase of a sine wave by 90 degrees.
MalHi Malkoba,
Thank you for your post.
Having looked at your VI I can say that you have created the correct inputs to the 'Sine Waveform.vi'.
However the dial you had created had no affect as it was not wired into it the 'Sine Waveform.vi' on the block diagram.To fix the problem I have wired the 'Phase' dial into the 'phase' terminal of the waveform generator. This now changes the phase of the sine wave during runtime.
The dial also now has a digital display (numeric box below it)- this can be used to read the dial's value, or feed in specific values into the control.
Please find a modified version of your VI below.
Regards,
Field Sales Engineer | National Instruments | UK & Ireland
Attachments:
NI_phase shift sine.vi 31 KB -
Solution Man. 4.0 upg Hangs/running very slowly at XPRAS_UPG
hi all,
I started my solution manger upgration 14th of march ,today is 24th march ,past 3 days the upgradation is in XPRAS_UPG phase and I also followed as per the SAP note 558197(12 Hours back)
In the console window I can see some transport is going on ,which is as
Resetting conversion errors ...
Reset done - starting tp ...
running C:\usr\sap\S01\SYS\exe\run\tp.exe pf=c:\usr\sap\put\bin\XPRASUPG.TPP put S01
Please guide me
thanks & regards
George
Edited by: George Varghese on Mar 24, 2008 9:43 AMHello George,
> I can find one backgroung job is running and where only SAPMS38L program is active and acceing only one table D010INC
That is a very important detail
Can you please take a look at the oracle sessions, if the session is maybe blocked or reading?
Login to client 000 => ST04 => Detailed Analysis => Oracle Sessions
Search for the session that is accessing the table D010INC and take a look at the wait event.
If the wait event is "db file sequential read" or "db file scattered read" .. please make a double click on the session and execute the "explain plan" and post the result here..
As you have told us, that your upgrade is taking a very long time.. i have seen such a situation, if the oracle parameter "_B_TREE_BITMAP_PLANS" was not set to false.
Regards
Stefan -
XPRAS_UPG error. Do ABAPers fix these?
Experts,
The XPRAS_UPG phase is failing, because the program SAPLSDHI has syntax error in with SHLP_DESCR_TAB_T type missing or not defined. I checked all the underlying data types that define SHLP_DESCR_TAB_T and all are OK. What could possibly be the cause? Did anyone come across a similar situation? BTW, I am upgrading from 4.0B to ECC 6.0.
Do ABAPers enter the scene in this phase to fix errors?
Thanks in advance. Points will be gratefully awarded.
Edited by: NW on May 19, 2008 8:49 AMHi Raj,
for problems during XPRASS_UPG or any other phase refer to the upgrade manual according to the source and target release
this will give you notes that contains solution to general errors such as this
Thanks and Regards
Abdul Hadi -
Upgrade From 46B to ECC6 SR3 - XPRAS_UPG errors
Hello,
I ugrade a system from 46B to ECC6 SR3.
Windows 2003 SP1 32bits / MSSQL 2000 SP4.
During the XPRAS_UPG phase, i have an error in the post-import method RS_SHIP_AFTER_IMPORT for the transport SAPK700ZH1.
The log is the RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxx were synchronized
Incorrect input for activating transported shadow IPacks
Job cancelled after system exception ERROR_MESSAGE
Have you already encountered this problem?
Thanks,
AlexandreThe problem is solved.
It was due to an empty entry in table rsbasidoc.
Alex -
XPRAS_UPG Error Messages
Dear All,
While performing an upgrade from 4.6c to ECC6.0. I have received 10 errors in the XPRAS_UPG Phases.
As per the upgrade guide I following to find the name of the error messages
as SAPK700ZG2 and checked the error message in SE09.
Transport Logs:
5 SAPK700ZG2 Rel. 700 AFTER_IMP objects: SOBJ/PDWS
5 DV2 DV2 - HPUX System
Import 12/17/2007 19:55:20 (0) Successfully Completed
5 Method Execution 12/17/2007 21:28:56 (8) Ended with errors
12/17/2007 20:43:05 (8) Ended with errors
12/17/2007 21:28:56 (8) Ended with errors
4 Import steps not specific to transport request
When I clicked on the long text for the above error message it gives the general help.
Execution of programs after import (XPRA)
Transport request : SAPK700ZG2
System : DV2
tp path : /usr/sap/DV2/SYS/exe/run/tp
Version and release: 372.03.35 700
Execution of programs after import (XPRA)
End date and time : 20071217212856
Ended with return code: ===> 8 <===
Can anyone help to solve this issue.
I am enclosing the error file XPRASUPG.ELG:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700ZG2.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEOL555 Object type '"BUS20370"' could not be generated
Long text:
Cause
The object type could not be activated.
What to do
Select the function 'Check' in the object type and correct the error
found. Then try to activate the object type again.
2EEOL555 Object type '"BUS20350"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20300"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20310"' could not be generated
Long text: see above
2EEOL555 Object type '"BUS20360"' could not be generated
Long text: see above
2EEPU133 Errors occurred during post-handling "SWO_OBJTYPE_AFTER_IMPORT" for "SOBJ" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly
before this message. First read these error messages and the respective
long texts. You will find further information there on correcting the
errors.
If this information is not sufficient, look for error notes in the
SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-DWB-TOO-BOB" ("Business Object Builder")
Long text:
Cause
During the upgrade or import of a transport request, errors occurred in
the component
the component
&V#& (&V#&).
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INFICA.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPRGPGD07.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INISUT.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007ININSURANC.DV2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-60007INFICAX.DV2
so on.
The error message doesn't give enough information neither the upgrade guide. Can anyone help me to overcome this error.
Thanks & Regards
SenthilThe basic problem here is that the affected SWO1 objects depend on an Enhancement Spot containing a type group which is in-active and therefore not available for generation from SWO1.
You have to activate the type group concerned.
The following process should achieve activation of the SWO1 objects:
1. TCODE: SE18
Display PLM_AUDIT_LIST_ITEM in enhancement spot.
Activate this object.
2. TCODE SE80
Package: PLM_AUDIT
Find the PLM_BUS203* function groups and activate them. (same as generating from SWO1)
You might want to try step 2 first, and only activate the object in step 1 if Step 2 fails.
Hope this helps others who will prefer to fix rather than ignore this error.
Best Regards
Andre Rainsford-Alberts -
Hi;
We are trying to uprade from 4.6C to EHP4 SR1. When we are in XPRAS_UPG
phase, upgrade gives the errors below:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-603DWINEAAPPL.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397CThe subobject value table "TCACS_APPLDEF" contains invalid key
fields
2EENR893INumber range object "CRD_AS_ID" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text:
Cause
During the upgrade, import post-processing &V#& was performed for
object &V#& &V#&. Errors were reported.
System Response
The upgrade is interrupted.
What to do
You will find the error messages for post-processing &V#& directly before this message. First read these error messages and the
respective
long texts. You will find further information there on correcting
the
errors.
If this information is not sufficient, look for error notes in the SAPNet - R/3 Front End. Keywords you can use for the search are
the name of post-processing &V#& or
the message numbers of the preceding error messages. The message
number
appears in the header of the long text display.
If you enter a problem message for the error, enter the following
information:
the name of post-processing &V#&
the message numbers of the preceding error messages
the components in which the error occurred
2EEPU136 The errors affect the following components:
Long text:
Cause
During the upgrade or import of a transport request, errors
occurred
which affect particular components of the SAP System.
The following messages list the components in which the errors
occurred.
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text:
Cause
During the upgrade or import of a transport request, errors
occurred in
the component
&V#& (&V#&).
System Response
The upgrade or import of the transport request is interrupted.
What to do
Read the preceding error messages and their long texts for more
information on correcting the errors.
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-604DWINEAAPPL.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397CThe subobject value table "TCACS_APPLDEF" contains invalid key
fields
2EENR893INumber range object "CRD_AS_ID" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR-604DWINSAPHR.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397HThe subobject value table "T591A" contains invalid key fields
2EENR893INumber range object "HR_ZA_LABR" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPR701WG3.FKQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2EENR397FThe subobject value table "TFK_NUMGR_IT" contains invalid key
fields
2EENR893INumber range object "FKKEXBL_IT" " "
2EENR397HThe subobject value table "T591A" contains invalid key fields
2EENR893INumber range object "HR_ZA_LABR" " "
2EEPU133 Errors occurred during post-handling "AFTER_IMP_NROB"
for "NROB" "L"
Long text: see above
2EEPU136 The errors affect the following components:
Long text: see above
2EEPU137 "BC-SRV-NUM" ("Number Range Management")
Long text: see above
1 ETP111 exit code : "8"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED
ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132
above <<<
Best regards
NoyanHello Noyan,
Please refer to note '1484591 - NK: Error message NR 397 after import'
and check whether it helps you.
Please apply the note 1484591 manually
as it is not possible to use SNOTE during upgrade.
Make sure the Req. Corr. Instructions from note
'1467470 - NR: Check of subobject value table'
are also implemented if not done yet.
In order to apply the note manually (as SNOTE is blocked due to the
upgrade), you need to unlock the system:
1. In order to unlock the system, you must execute these commands:
/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/
abap/bin/DEFAULT.TPP unlocksys <SID>
/usr/sap/<SID>/SYS/exe/run/tp pf=<EHPI directory>/
abap/bin/DEFAULT.TPP unlock_eu <SID>
2. Now you should be able to logon into the system with a user
different from DDIC.
3. Apply the note's changes manually. Please take into account the
note's prerequisites' corrections from note 1467470 have to be
applied also.
4. Lock the system with the following commands:
tp locksys <SAPSID> pf=<transport profile>
tp lock_eu <SAPSID> pf=<transport profile>
5. Repeat the failing phase.
Regards,
Paul -
Hello
We are trying to upgrade to 3.5 (from 3.1) & currently facing error in XPRAS_UPG phase
DEtails are as below
*************XPRA ERRORS and RETURN CODE in SAPRIBIFU1.EBD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10120701")
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 other 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.
1AEPU320 See job log"RDDEXECL""10120701""EBD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPRIBIFUZ.EBD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10120801")
Long text: see above
1AEPU320 See job log"RDDEXECL""10120801""EBD"
1 ETP111 exit code : "12"
has anyone faced the similar problem?
Thx
PraveenHello all:
The solution is to implement note 844007 manually. Since the upgrade is in progress, you need to use the commands:
tp unlocksys <SAPSID>
tp unlock_eu <SAPSID>
first before implementing the note.
Please all of you assign 10 points as this is going above and beyond the OSS customer message process.
Best Regards -
Ron
PS - The customer should be advised to upgrade to SAP NetWeaver 2004s instead, as you have a fully working 3.5 system "under the covers" but have huge potential for use of many, many more advanced and next generation features. In other words, you can run 2004s BI like it's a 3.5 system, and can "phase in" the use of new features in 2004s when you are ready without another upgrade!
Best Regards -
Ron Silberstein
SAP
Maybe you are looking for
-
What Cable Do I Need To Connect My MacBook With a Cinema Display?
Hi, I have got a 23" old HD Cinema Display. It is the one with the transparent plastic around the outside. I have a 13" MacBook, Oct 2008 then discontinued, the one that looks like a MacBook Pro, and I would like to connect the laptop to the display.
-
How to get total number of products for the site?
Hi, I want to know the total number of products available for the site. i checked in the dcs_product table, it shows 40849 unique products. is this the total number of products count which are used in the site? I have another table in CATA schema dcs
-
How to veto a JComboBox selection change in ItemListener
I have a JComboBox whose current value is tied to some data cached in my application. I want to be able to examine the selection in an ItemListener attached to the JComboBox, and if the value is different than what I have cached, I want to ask the us
-
Visited sites don't change color
I have latest version. Default should be to change hyperlink color after visiting. This is not occurring in Firefox. Why?
-
Method insertViewRowAt( ) in ViewRowSetImpl
Hi, I am inserting a new row in the view object as -- view.insertRow(newRow); This is working fine in 9.0.4. But after migration to 10.1.3, its giving oracle.jbo.AttrValException: JBO-27014 exception. In stacktrace, it is shown that the method insert