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

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
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
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:
XPRASUPG.ECO and R3up.ECO
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 u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 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.
676135 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?
This are the logs:
XPRASUPG.ECO
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 <<<
R3up.ECO:
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 Cardenas

Hi 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

XPRAS_UPG Phase

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

Trying to open old iPhoto library on osx 10.9.5 with iPhoto 9.5.1. iPhoto says I must upgrade but upgrade eventually hangs. Tried to rebuild/repair database but it always says you have to upgrade database first and eventually hangs

Trying to open old iPhoto library on osx 10.9.5 with iPhoto 9.5.1. iPhoto says I must upgrade but upgrade eventually hangs. Tried to rebuild/repair database but it always says you have to upgrade database first and eventually hangs

What version was the old library made with?
What is the exact message? when it hangs does it crash or do you have to force quit?
LN

OBIEE 11.1.1.6.2 BP1 - Upgrade Assistant hangs

Hi
On a new obiee 11.1.1.6.2 BP1-installation i tried running the upgrade assistant to upgrade my obiee 10g repository/catalog. On a 11.1.1.6.0 testsystem this worked without problem.
On the new system the upgrade assistant hangs in step 3 after configuring the source files and clicking next.
Did someone discover any similar behaviour or has a solution to that problem?
Thank you

we have figured out the problem. It was due to the issue outlined in Oracle Doc Id 1410233.1. the upgrade agent may fail if the IP address is not set. When manually set the Listen addresses for the Admin and Managed servers in the WebLogic Console, and the Listen addresses for CoreApplication in EM, everything worked. ua.bat could not proceed until IP address manually specified in WebLogic console and EM as per Oracle Doc ID 1410233.1.

11.5.10.2 to 12.1.1 upgrade workers hang

I am performing the 11.5.10.2 to 12.1.1 upgrade. My DB version is 10.2.0.4
I have the process down to 46000 workers (on the main 6678700 patch merged with two other small ones) however as the process goes along workers seem to hang randomly and I have to use adctrl to restart the worker. The status still shows as Running when it hangs, the alertSID.log, adpatch.log, adworkxxx.log and the log file that adworkxxx.log specifies for that step none show any errors and seems to be running properly.
I can restart the worker than hasn't changed in awhile and it will deffer that worker and move on and later process that same file that it was normally without issue.
I left it running overnight to see if perhaps I wasn't waiting long enough and they never moved, restarted them and on thier way.
Is there anywhere else I can check to see what is causing the workers to hang? Having to babysit the entire process is a pain but I am mostly concerned that something is not configured properly.
Edit: It seems that most of the time is is the .ldt & .lct files that hang.
Thanks for the input.
Edited by: Toolman21 on Jan 20, 2011 10:42 AM

App & DB server
2 xeon 5160 processors, 8Gb of ram, plenty of disk space, running RHEL 5.5
App has SSO and portal midt on it. Portal tier is not running. (no services clustered)
DB single instance.
Ram, buffers and swap show to have free space on both servers (as per free command).
Issue didn't happen with any of the small patches I applied as pre-req for main patch.
I ran
select file_name, bytes/1024/1024 current_size_MB, increment_by*8192/1024/1024 autoextend_size_MB, maxbytes/1024/1024 max_size_MB
from dba_data_files
where bytes>(maxbytes*0.90)
and autoextensible = 'YES'
or bytes/1024/1024+increment_by*8192/1024/1024>maxbytes/1024/1024*0.9
and autoextensible = 'YES';
and the only datafiles that come back as being full are part of tablespaces that have multiple files and still have autoextend free space left in subsequent files.
At one point towards the beginning of the patch I did hit a tablespace full error which was indicated by one of the log files, I added a datafile and it hasn't complained about tablespace since and the new file has not extended anywhere near the maxsize defined.

Upgrade to ECC 6.04 PHASE: MAIN_SHDIMP/SHADOW_IMPORT_INC were negative

Hello!
We are busy upgrading from ERP 2004 to ECC 604 SR1.
Error:
Checks after phase MAIN_SHDIMP/SHADOW_IMPORT_INC were negative!
Last error code set: Unresolved requests in buffer TST Check logfiles
'SHDALLIMP.ELG' and '/binaries/sap/TST/upg/abap/log/SAPup.ECO'
tp and r3trance updated to new versions.
Error in file SHDALLIMP.ELG
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-60403INCCEE.TST
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
1 ETP111 exit code           : "8"
Error in file SAPK-60403INCCEE.TST
3 ETW674Xstart import of "R3TRTABU/ATL/AT086" ...
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
4 ETW000   0 entries from /ATL/AT086 (%) deleted.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
4 ETW000   0 entries from /ATL/AT086 (%) deleted.
4 ETW000 "E071~"-LOCKFLAGs 000002 - 000136 updated ('3', 135 entries).
4 ETW000 date&time: 16.05.2011 - 17:08:33
3 ETW676 end import of "R3TRTABU/ATL/AT086" (warnings).
4 ETW000 "E071~"-LOCKFLAGs 002009 - 002009 updated ('1', 1 entries).
4 ETW690 COMMIT "17460" "35048"
Error in file SAPup.ECO
Phase SHADOW_IMPORT_INC:
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 13063 at 20110516170633
ENV: DIR_LIBRARY=/binaries/sap/TST/upg/abap/exenew
ENV: JAVA_HOME=/usr/j2se
ENV: LD_LIBRARY_PATH=/binaries/sap/TST/upg/abap/exenew:/binaries/sap/TST/upg/jvm/jre/lib/sparcv9/server:/binaries/sap/TST/upg/jvm/jre/lib/sparcv9:/binaries/sap/TST/upg/jvm/jre/../lib/sparcv9:/etc/emc/rsa/cst/lib:/usr/sap/TST/SYS/exe/run
ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/TST/102_64
ENV: ORACLE_PSRV=TST
ENV: ORACLE_SID=TST
ENV: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV: PATH=/binaries/sap/TST/upg/abap/exenew:/oracle/TST/102_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/opt/EMCpower/bin:/etc/emc/bin:/etc:/usr/ccs/bin:/usr/ucb
ENV: SAPSYSTEMNAME=TST
ENV: auth_shadow_upgrade=0
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPR3Q
ENV: dbs_ora_tnsname=TST
EXECUTING /binaries/sap/TST/upg/abap/exenew/tp (/binaries/sap/TST/upg/abap/exenew/tp) pf=/binaries/sap/TST/upg/abap/bin/SHDALLIMP.TPP put TST
This is /binaries/sap/TST/upg/abap/exenew/tp version 376.01.25 (release 701, unicode enabled)
ERROR: stopping on error 8 during SHADOW IMPORT
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.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
SWARNS: Highest tp internal severe warning was: 0151
tp finished with return code: 151
meaning:
Some warning regarding buffer entries
Process with ID 13063 terminated with status 151
Any idea for helpme,
thanks in advise.
Roman.

Hi,
Check SAP Note 1293059 - C-CEE 110_604: Add-On Support Packages. Your problem is documented in this note.
Thanks
Sunny

Upgrade to ECC 6.04 PHASE: MAIN_NEWBAS/PARCONV_UPG ERROR

Hi
get error in Upgrade to ECC 6.04 in downtime phase - MAIN_NEWBAS/PARCONV_UPG.
The screen says:
Checks after phase MAIN_NEWBAS/PARCONV_UPG were negative!
Last error code set: Conversion entries have been found in, see phase log for more detaile
In the SAPup.log says that:
CURRENTPHASE MAIN_NEWBAS/PARCONV_UPG
...started at 20110324123904
Using phase log file 'PARCONV.LOG'.
..finished at 20110324124157 with status ERROR CHECKING MODEFLAGS.
Error message set: 'Conversion entries have been found in, see phase log for more detaile'
...begin dialogue at 20110324124157
And in the PARACONV.ELG file says:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARALLEL ALTER TABLES MODEFLAG RESET: RSMFCONV and RETURN CODE in RSMFCONV.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARALLEL ALTER TABLES MODEFLAG RESET: RSMFCONV and RETURN CODE in RSMFCONV.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MVNTABS ERRORS: ddlntabs and RETURN CODE in PD990324.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CONVERSION ERRORS and RETURN CODE in NCONV00.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CONVERSION ERRORS and RETURN CODE in NCONV01.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CONVERSION ERRORS and RETURN CODE in NCONV02.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CONVERSION ERRORS and RETURN CODE in NCONV03.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MVNTABS ERRORS: delntabs and RETURN CODE in PL000324.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "0"
I look this log files ( RSMFCONV.DEV RSMFCONV.DEV PD990324.DEV NCONV00.DEV NCONV01.DEV NCONV02.DEV NCONV03.DEV PL000324.DEV ) but all of this, is exit code '0'
I don't know where is the error.
Any idea for helpme,
thanks in advise.
Sergio.
Edited by: Sergio Mazzeo on Mar 24, 2011 1:24 PM
The last lines of the PARACONV.LOG says that:
4 ETQ260 Starting batchjob "NTBUF_SYNC"
4 ETQ230 Starting RFC Login to: System = "DEV", GwHost = "LKMDEV", GwService = "sapgw00"
4 ETQ359 RFC Login to: System="DEV", Nr="00", GwHost="LKMDEV", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ233 Calling function module "subst_start_batchjob" by RFC
4 ETQ399 JOBNAME='NTBUF_SYNC', REPNAME='RSNTSYNC', VARNAME='', BATCHHOST='LKMDEV', IV_SCHEDEVER=' '
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20110324124156
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
3 ETQ399 log analyse: search for '.[WT ]' in '^N......\.DEV$'
1 ETQ399 Conversion entries found:
2 ETQ399 CONV ENTRY TBATG TABL/SCMB/TREEVIEW2                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLCMS_RE_OBJ_SPC                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLCNVCDMC_PROJHIER                 0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOB_COND_DIFF                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_AMT                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_BDT                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_DATE                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_DIFF                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_FMOD                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_LIST_COND                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOT_DATEPOS                    0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLGMBDGTLSTNUMBER                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLGMGRSPONSOREDOBJ                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLHRWEB_RULE_GROUP                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLT5RSOP_SCHEME                    0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_PRD_FSTAT                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_PRD_PRD_SET                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_RE_EX_BPRL                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_RE_EX_TYP                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCWB_CATT_HEADER                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCWB_ITEM_POOL                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTJBR_US_ACCT_T                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLVALT_SP_VAL_SEC                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLVDDD_HEADER_COL                  0CNVIE20110323DDIC
4 ETQ001 START time "No modeflag to check for"
1 ETQ206 Executing pre-phase DB specific actions.4 ETQ010 Date & Time: 20110324124157

The last lines of the file PARACONV.LOG says that:
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
3 ETQ399 log analyse: search for '^.[^WT ]' in '^N.......DEV$'
1 ETQ399 Conversion entries found:
2 ETQ399 CONV ENTRY TBATG TABL/SCMB/TREEVIEW2                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLCMS_RE_OBJ_SPC                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLCNVCDMC_PROJHIER                 0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOB_COND_DIFF                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_AMT                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_BDT                   0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_DATE                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_DIFF                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_COND_FMOD                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOC_LIST_COND                  0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLFICOT_DATEPOS                    0CNVIE20110322DDIC
2 ETQ399 CONV ENTRY TBATG TABLGMBDGTLSTNUMBER                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLGMGRSPONSOREDOBJ                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLHRWEB_RULE_GROUP                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLT5RSOP_SCHEME                    0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_PRD_FSTAT                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_PRD_PRD_SET                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_RE_EX_BPRL                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCMS_RE_EX_TYP                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCWB_CATT_HEADER                 0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTCWB_ITEM_POOL                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLTJBR_US_ACCT_T                   0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLVALT_SP_VAL_SEC                  0CNVIE20110323DDIC
2 ETQ399 CONV ENTRY TBATG TABLVDDD_HEADER_COL                  0CNVIE20110323DDIC
4 ETQ001 START time "No modeflag to check for"
1 ETQ206 Executing pre-phase DB specific actions.
4 ETQ010 Date & Time: 20110324124157
Can any helpme to this error. I don´t know what and where is the error. Not found this item in SAP Notes.
Thansk a lot.
Sergio.

BW Upgrade PREPARE stopped in JOB_RSUVSAVE Phase

Hi All,
We are trying upgrade from BW 3.1 Content to BI 7.0
Our OS is HP-UX 11.11 and DB - Oracle 10GR2
Now am in PREPARE phase, Its giving error Upgrade phase JOB_RSUVSAVE.
Below is the details of the RSUVSAVE.log file
1 ETQ201XEntering upgrade-phase "JOB_RSUVSAVE" ("20070907173858")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPBAQ
4 ETQ399 auth_shadow_upgrade=0
4 ETQ260 Starting batchjob "RSUVSAVE"
4 ETQ010 Date & Time: 20070907173858
4 ETQ260 Starting batchjob "RSUVSAVE"
4 ETQ230 Starting RFC Login to: System = "BAQ", GwHost = "bwapoqas", GwService = "sapgw01"
4 ETQ359 RFC Login to: System="BAQ", Nr="01", GwHost="bwapoqas", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20070907173904
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ242 Error code "-1" during analysis of logfiles matching "RSUVSAVE\.BAQ"
2EETQ262 Batchjob "RSUVSAVE" aborted
4 ETQ359 RFC Login to: System="BAQ", Nr="01", GwHost="bwapoqas", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2WETQ360 RFC of "subst_list_sys_logs" failed:
2WETQ361 code/exception : COULD_NOT_OPEN_FILE
4 ETQ359 RFC Login to: System="BAQ", Nr="01", GwHost="bwapoqas", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
1EETQ204 Upgrade phase "JOB_RSUVSAVE" aborted with severe errors ("20070907173904")
~
~
Pls giv some inputs to proceed
Thanks & Regards
Karthikeyan

Claiming no credit for this one - found elsewhere on SDN - Originally posted by Jason Spessert
SAPUpgrade _ PHASE- JOB_RSUVSAVE
For any others who get a similar error...
We had the same symptom, the upgrade from 4.7 to 6.0 was running PREPARE and the background job aborts as shown above saying it cannot write this log to a directory. Looking at the dump (ST22) or double-click in the job log it shows the directory:
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 1 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 4
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Repository Switch: Tool Report for Performing Cleanups
SY-MSGTY A SY-MSGID PU
SY-MSGNO 814
SY-MSGV1 D:usrsapput mpRSUVSAVE.EQ0
SY-MSGV2 No such file or directory SY-MSGV3
SY-MSGV4
It turned out - we were not running the upgrade from D: we had the put directory in F:. And during PREPARE we, as instructed, inserted the DIR_PUT=F:usrsapput into the default.pfl (instance profile).
The trick was that we needed to re-start the instance. While inserting DIR_PUT into the instance profile gets you past the initial PREPARE check, you need to restart the instance so the change takes effect.
We restarted and then resumed PREPARE and it passes the above error as it now writes to the F: directory.

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 Chowdhary

Hi,
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.

Sync looks hanging in download phase in C$ALL_SNAPSHOTS (last item)

The synchronizations are “hanged” for a long period on time in the download phase on the last 2 items:
PI_APP_PUB_PROPERTIES
C$ALL_SNAPSHOTS
The time is bigger if the number of clients synchronizing at the same time is bigger as well.
I have taken some detailed cycles and the Total Sync Time does not fit at all with the sum of the time used for all the items during upload plus download… this difference is very high!
Did anybody faced a similar problem?
Below some examples:
session_id = 1106
SYNC_SECS = 428
UPLOAD_SECS = 3
DOWNLOAD_SECS = 425
SUM( UPLOAD_ITEMS_SECS) = 2
SUM( DOWNLOAD_ITEMS_SECS) = 279
Where are the 147 seconds of diff used for?!!
session_id = 1135
SYNC_SECS = 664
UPLOAD_SECS = 5
DOWNLOAD_SECS = 659
SUM( UPLOAD_ITEMS_SECS) = 4
SUM( DOWNLOAD_ITEMS_SECS) = 407
Where are the 253 seconds of diff used for?!!
Thanks everybody in advance.
Tomeu

Hey Tomeu
Try the following:
On the new associated CMP$ table, insert about 5000 or 10000 bogus rows. Run stats and then delete the rows.
I will try to sum up what the problem is, it isn't actually related to Oracle Mobile but with the database engine itself. You have a table CMP$ size 0 rows, mobile server inerts N amount of rows. When the download is complete, there is a cleanup process that run individual update statements in a batch/cursor scenario. The update statements actually use ROWID to update each row... and you would think the explain plan at this point uses the pk index to get the row required for update, it actually does a Full Table Scan on the N number of rows. If stats are collected when there is some data in the table, it will for the update statement to use a better explain plan to perform the update.
Now, if MGP is timing out, then there are a couple of issue that are happening... the C$ALL_SNAPSHOT issue could and should cause a timeout issue of MGP. A correction to this would be to convert the table that is causing this issue to Queue based refresh. Another issue could just be the type of SQL query that you are running in that snapshot isn't effecient with MGP/Sync and may need to be altered to perform better. Use of query caching can help, I would attempt that before queue based refresh though. So in this order, your performance tuning technique should be this:
1. Check the SQL and see if it can't be tuned to get better results.
2. Enable Query Cache for the snapshot
3. Queue-based refresh.
Let me know if you have questions.
Greg

IOS 5.0.1 upgrade, devices hangs in shuffle mode

Hello, I have an original iPad and the newest iPod touch and ever since the iOS 5.0.1 upgrade, both devices hang after a while when playing either all songs or a playlist in shuffle mode. It gets to a point where the song playing doesnt match the song displayed then on the next song it hangs. At this point I have to close iTunes and start over. Sometimes it hangs after a few songs and sometimes after 30-40 minutes.
This has made shuffle mode unusable ( which is what I primarily use). It never did this prior to 5.0.1. Thoughts?

I did the back-up / restore option all from within iTunes. Still no problems so that appears to be the fix until Apple recognizes it and puts out a fix.

EhP4 SP5 upgrade stuck at PREP_INSTALL/SHDINST_CRE Phase

Hello Everyone,
I'm trying to upgrade EhP3 box to EhP4 SP5 and currently stuck at following phase:
Severe error(s) occured in phase PREP_INSTALL/SHDINST_CRE
Last error code set: Removing directory 'G:\EHPI\abap\TMP' failed: The process cannot access the file because it is being used by another process.
SAPehpi broke during phase SHDINST_CRE in module PREP_INSTALL / Installation
I've failed to delete this TMP folder manually, says its been used by another person or program. If I stop ehpi tool i'm able to delete it but after i re-run the Installation Phase using ehpi tool, it again gives me the same error as above.
Please suggest.
Thanks
Vamsi Atluri
Edited by: Atluri Vamsi on May 5, 2010 4:16 PM
Edited by: Atluri Vamsi on May 5, 2010 4:23 PM

file permissions
Try to check folder permissions , try to give permissions directly for user (if permission exist try to delete and give from new) I'm see some illogical behavior on windows servers.
Regards.

Getting a MBP 2007 to OS X 10.9, upgrade path hangs

I am trying to upgrade a MBP 2007 from a family member from Tiger (which it was still running) to 10.9 (which is possible). My planned upgradev route is:
Upgrade to 10.5 Leopard
Upgrade to latest 10.5.x Leopard (because I suspect the upgrade to 10.6 will run better when 10.5 is fully updated)
Run iTunes on the user account to update the iTunes database
Upgrade to 10.6 Snow Leopard
Upgrade to latest 10.6.x Snow Leopard
Run iTunes on the user account to update the iTunes database
Use the App store for further upgrades
I am stuck at step 2. I was able to upgrade to 10.5, then I ran Software Update and got three updates (iTunes, Photo Booth and 10.5.x Combo). The first two were successfully installed it seems, but the 10.5.x Combo hangs (after reboot) forever on 'Configuring Installation'. I need to force-shutdown the MBP and after reboot I am still at 10.5.0. And as th enewer iTunes has been installed, I cannot start it up and upgrade the user's library.
Are individual 10.5.1 etc. installs still available somewhere? I could try these.
Otherwise and in any case: Help?
Thanks

I did get that error message when I first tried to upgrade 10.4.11 with the 10.6 disk. I cannot reproduce because in the meantime, the system has been upgraded to 10.5.
I recall that I was also unable to boot directly from the 10.6 disk. It is a white disc, btw.
I've taken the plunge and am now installing 10.6 on top of 10.5.0 directly. Then I need to upgrade iTunes and hope the 10.4.11 iTunes Library version can be upgraded.
In the worst case, I have created a volume DMG from the original starup disk using TDM and another Mac.
Woops. I just see that I've accidentally started the upgrade from a wrong 10.6 disk, I've written 'MBA Only' on the envelope of that one and it is the one in the envelope labeled 'not for resale'. Hmm, now I understand why I could not boot from that one. It can only boot my (old) MBA. But using it as upgrade disk seems to work. Still keeping my fingers crossed.

After 10.5.2 upgrade, machine hangs on boot at grey apple/spinning dial

Leopard has been installed and running for 5 months on an external 160G iomega USB drive on my intel macbook pro.
Last night, I took the 10.5.2 upgrade, it downloaded and installed everything, then asked to "Restart", and during reboot, it did some stuff, then I think requested to restart again, and now it won't boot.
On boot the gray apple comes up, the little dashed dial spinner goes round and round, the disk light blinks like its booting for about 10 seconds, then it just stops.
If I take off the USB drive, I can boot my old Tiger system off the internal just fine. Just the Leopard install has been bricked.
This happened once when I had Tiger on an external firewire LACIE drives; I took an update, and the system would no longer boot.
Seems like Apple needs to do a better job testing upgrades with systems installed on external drives.. this is pretty depressing to loose everything just doing an upgrade.
Does anyone know what this is?
Is there any magic key sequence I can use to debug what's going wrong on boot?
I tried Shift-Apple-V to try to get a verbose boot going, but apparently the hang is too early in the boot process.

Greg Ercolano wrote:
Leopard has been installed and running for 5 months on an external 160G iomega USB drive on my intel macbook pro.
Last night, I took the 10.5.2 upgrade, it downloaded and installed everything, then asked to "Restart", and during reboot, it did some stuff, then I think requested to restart again, and now it won't boot.
On boot the gray apple comes up, the little dashed dial spinner goes round and round, the disk light blinks like its booting for about 10 seconds, then it just stops.
If I take off the USB drive, I can boot my old Tiger system off the internal just fine. Just the Leopard install has been bricked.
This happened once when I had Tiger on an external firewire LACIE drives; I took an update, and the system would no longer boot.
Seems like Apple needs to do a better job testing upgrades with systems installed on external drives.. this is pretty depressing to loose everything just doing an upgrade.
Does anyone know what this is?
Is there any magic key sequence I can use to debug what's going wrong on boot?
I tried Shift-Apple-V to try to get a verbose boot going, but apparently the hang is too early in the boot process.
You might use the terminal command:
dmesg
to see the boot process.
I have Leopard 10.5.2 with the latest security update running on three Macs, two MBPs and an old dual G5. No problems, so I cannot agree that has to do with an update. I believe it is due to 3rd pary apps, old drivers, etc.
I have never had a problem with any of the Apple software or updates. I conclude that the problems must be related to 3rd party apps, etc., and not to the actual Apple software, or else I would be experiencing the same problems, which I am not. And I don't believe in luck

Upgrade in hangs in XPRAS_UPG phase

Similar Messages

Maybe you are looking for