Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

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

      1. 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

      1. 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 Cardenas

Former Member
Not what you were looking for? View more on this topic or Ask a question