SAP BW upgrade problem in phase lang_select

Hello everybody,
during our upgrade from SAP BW 3.0B to 3.5 a problem occurred in the phase lang_select running PREPARE. Unfortunately we did not find any up-to-date SAP note on this, except in the note (212481), where the symptom is descried quite well, but the solution does not fit. By the way, the folder-names are already in upper-case (a different note told to do so). So I would be glad if anybody who does have any experience with upgrading from 3.0B could take a look at our problem as described below.
First of all our system information:
SAP Kernel 640 PL 115
OS: IBM AIX 5.2.0
DB: DB2 V8 FP 10
actual release of SAP BW: 3.0B
target release of SAP BW: 3.5 SR1
R3trans: 6.13 (release 640)
Tp: 340.16.12 (release 640)
Problem: PREPARE, phase lang_select
>> 08:56:19 PREPARE: START OF PHASE LANG_SELECT
working on /software/51030722/LANG1 ...
working on /software/51030722/LANG2 ...
working on /software/51030722/LANG3 ...
The following language(s) could not be updated yet:
- German for component PI_BASIS
- German for component SAP_ABA
- German for component SAP_BASIS
- German for component SAP_BW
- English for component PI_BASIS
- English for component SAP_ABA
- English for component SAP_BASIS
- English for component SAP_BW
Please mount another Language Disk for these language(s).
You need at least CDs which satisfy the vector "DE"
(standard languages) for all components.
It is not allowed to omit this update.
What we did until the message comes up:
- all by SAP recommended preparations on the OS, the DB and SAP BW 3.0B have been successfully implemented (as described in Component Upgrade Guide SAP BW 3.5 SR1)
- we copied all the data from CD/DVD into directories on the server
- we copied the fix FIX_WEBAS640SR1.SAR into /usr/sap/put/, which is required by PREPARE later on (SAP note 663240)
- start of PREPARE on the command-line (the directory /usr/sap/put/ is now filled with files and subdirectories are created)
- overwriting R3trans and Tp with the newest versions (as mentioned at the beginning)
- executing UaServer on the AIX, accessing the tool via web browser from a client
- in the applet we start PREPARE
- making entries for PREPARE
- lang_select
We did also examine the logs, here is what they say:
R3upchk.log
UPGRADEPHASE LANG_SELECT
...started at 20060308085619
Phase log file: 'LANGSEL.LOG'
Condition #if 1 >= 0
is evaluated as a TRUE expression, total status is TRUE, stack level 1
...begin dialogue at 20060308085623
Langsel.log
1 ETQ201XEntering upgrade-phase "LANG_SELECT" ("20060308085619")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '10', GwService = 'sapgw10'
4 ETQ399 Environment variables:
4 ETQ399 dbs_db6_schema=SAP1
4 ETQ399 auth_shadow_upgrade=0
4 ETQ380 computing toolpath for request "TP_LANG_SELECT"
4 ETQ381 request "TP_LANG_SELECT" means "create cofile in phase TP_LANG_SELECT"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETG880 Language data requested for "" (without standard languages "DE")
4 ETQ359 RFC Login to: System="1", Nr="10", GwHost="sap1", GwService="sapgw10"
4 ETQ232 RFC Login succeeded
cdtrace.log
2006/03/08 08:56:19 Searching for Data Carrier labeled LANGUAGE
 Adding path: /software/51030783
2006/03/08 08:56:19 Resolving directory structure below /software/51030783
 Adding path: /software/51030783/UM1
 Adding path: /software/51030783/UM2
2006/03/08 08:56:19 Directory structure below /software/51030783 resolved
2006/03/08 08:56:19 Working on /software/51030783 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM2 ... no matching label
 Adding path: /software/51030777
2006/03/08 08:56:19 Resolving directory structure below /software/51030777
 Adding path: /software/51030777/UPG1
 Adding path: /software/51030777/UPG2
 Adding path: /software/51030777/UPG3
2006/03/08 08:56:19 Directory structure below /software/51030777 resolved
2006/03/08 08:56:19 Working on /software/51030777 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG2 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG3 ... no matching label
 Adding path: /software/51030630
2006/03/08 08:56:19 Working on /software/51030630 ... no matching label
 Adding path: /software/51030722
2006/03/08 08:56:19 Resolving directory structure below /software/51030722
 Adding path: /software/51030722/LANG1
 Adding path: /software/51030722/LANG2
 Adding path: /software/51030722/LANG3
2006/03/08 08:56:19 Directory structure below /software/51030722 resolved
2006/03/08 08:56:19 Working on /software/51030722 ... no matching label
2006/03/08 08:56:19 Working on /software/51030722/LANG1 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG2 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG3 ... matches -> added to result list.
 Adding path: /software/51030769
2006/03/08 08:56:19 Resolving directory structure below /software/51030769
 Adding path: /software/51030769/K01
 Adding path: /software/51030769/K02
 Adding path: /software/51030769/K03
 Adding path: /software/51030769/K04
 Adding path: /software/51030769/K05
 Adding path: /software/51030769/K06
 Adding path: /software/51030769/K07
 Adding path: /software/51030769/K08
2006/03/08 08:56:19 Directory structure below /software/51030769 resolved
2006/03/08 08:56:19 Working on /software/51030769 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K01 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K02 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K03 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K04 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K05 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K06 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K07 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K08 ... no matching label
 Adding path: /software/51030865
2006/03/08 08:56:19 Working on /software/51030865 ... no matching label
Well, we actually do not know what the problem is. It seems to us that the program is not able to identify the language source files. The point is why did the source-paths for the other data work, as we copied the CD/DVD-data into folders? What is different with the language-CD?
Thanks a lot for your help,
Peter

I had the same problem but for upgrading SAP SOLUTION MANAGER 3.2 to 4.0 in the PREPARE PHASE "LANG_SELECT"
In the PEVALLAN.<SAPSID> ,I realized that the path for the required DVD I entered was too long !!
My real path was "C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CRM_LNG"
and the PEVALLAN FILE in the IV_LANGDIR parameter it was
""C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CR"
I've just shortened the path and it works now.
This surprised me because from the beginning of the PREPARE phase, I had no problems with that kind of thing.

Similar Messages

ECC 6.0 Upgrade - Problem in phase PARDIST_SHD

Upgrading from 4.6C to ECC 6.0 on Windows/SQL Server.
Phase PARDIST_SHD failed with the following error:
"Table change not possible. There is a DB trigger on the table."
This problem is documented in the note 825146 (Add Info on upgrading to NW04s) in section IV item number 7. The note points to note number 956198 for the fix, which is to delete the trigger defined on table MSSDEADLCK manually in the SQL Server query analyzer.
I have performed the steps outlined in note 956198 to delete the trigger, but when restarting the upgrade it keeps coming back with the same error. It seems that, even if I restart the upgrade with INIT option, the upgrade is not re-setting to the beginning of the phase, but continues to error out immediately upon restart. Originally the phase took about 45 minutes to complete before it aborted with the error. Each time I have restarted the phase it ends after only a few seconds.
Anyone have any thoughts? I'm real close to just starting the whole thing over, I've never run into anything like this before. I am using the latest SAPup.

SAP gave me the answer.
ATAB needed to be renamed the Operation library.

Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE

Hello Expert,
I have a problem when a try to execute the upgrade in the phase
DEPLOY_ONLINE,
<<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
Trouble Ticket Report
Upgrade to SAP NetWeaver'04s
SID................: J2E
Hostname...........: sapepd
Install directory..: d:/usr/sap/J2E
Upgrade directory..: D:\SAPEPD\saploc\jupgrade
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.4.2_11 Sun Microsystems Inc.
SAPJup version.....: 1.1.101
Source release.....: 630
Target release.....: 700
Current usages.....: EP;AS;DI
ABAP stack present.: false
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters
D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.
Return code condition success evaluated to false for process java.exe
for action ACTION_DEPLOY_LIST.
More information can be found in the log file
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might
be an OSS note providing a solution to this problem. Search for OSS
notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade
<<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
THE FILE: DEPLOY_ONLINE_DON_01.LOG
BEGIN DEPLOY_ONLINE_DON_01.LOG----
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
<!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
#1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#action#DEPLOY_SLOT#
#1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#connect#standard#
#1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
#1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
#1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
#1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
#1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk
jre
bin
java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
usr
sap
J2E
JC00
SDM
program
bin
SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG#
#1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.OUT#
#1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
#1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
#1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
#1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
#1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
#1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG for details.##
#1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
#1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
#1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
#1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
*************END DEPLOY_ONLINE_DON_01.LOG*******************
FILE ************** DEPLOY_SLOT_0__DON_01.LOG
BEGIN DEPLOY_SLOT_0__DON_01.LOG----
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:33 PM Info: Starting to save the repository
Jul 18, 2007 3:18:33 PM Info: Finished saving the repository
Jul 18, 2007 3:18:33 PM Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
Jul 18, 2007 3:18:33 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
Jul 18, 2007 3:18:33 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Info: Begin of log messages of the target system:
07/07/18 15:18:33 - ***********************************************************
07/07/18 15:18:34 - Start updating EAR file...
07/07/18 15:18:34 - start-up mode is lazy
07/07/18 15:18:34 - EAR file updated successfully for 172ms.
07/07/18 15:18:34 - Start deploying ...
07/07/18 15:18:34 - EAR file uploaded to server for 500ms.
07/07/18 15:18:36 - ERROR: Not deployed. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
 Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
 at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
 ... 10 more
 For detailed information see the log file of the Deploy Service.
07/07/18 15:18:36 - ***********************************************************
Jul 18, 2007 3:18:36 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:36 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 18, 2007 3:18:36 PM Info: Starting to save the repository
Jul 18, 2007 3:18:36 PM Info: Finished saving the repository
Jul 18, 2007 3:18:36 PM Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
Jul 18, 2007 3:18:36 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
Jul 18, 2007 3:18:36 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:36 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Begin of log messages of the target system:
07/07/18 15:18:36 - ***********************************************************
07/07/18 15:18:36 - Start updating EAR file...
07/07/18 15:18:36 - start-up mode is lazy
07/07/18 15:18:37 - EAR file updated successfully for 375ms.
07/07/18 15:18:37 - Start updating...
07/07/18 15:18:37 - EAR file uploaded to server for 422ms.
07/07/18 15:18:39 - Successfully updated. Update took 1641ms.
07/07/18 15:18:39 - Deploy Service status:
07/07/18 15:18:39 - Application : sap.com/tcwdtools
07/07/18 15:18:39 -
07/07/18 15:18:39 - sap.com/tcwdtools - WEBDYNPRO
07/07/18 15:18:39 - sap.com/tcwdtools monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:39 - ***********************************************************
Jul 18, 2007 3:18:39 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:39 PM Info: Starting to save the repository
Jul 18, 2007 3:18:40 PM Info: Finished saving the repository
Jul 18, 2007 3:18:40 PM Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
Jul 18, 2007 3:18:40 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
Jul 18, 2007 3:18:40 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Begin of log messages of the target system:
07/07/18 15:18:40 - ***********************************************************
07/07/18 15:18:40 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
07/07/18 15:18:40 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
Jul 18, 2007 3:18:40 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:40 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
Jul 18, 2007 3:18:40 PM Info: Starting to save the repository
Jul 18, 2007 3:18:41 PM Info: Finished saving the repository
Jul 18, 2007 3:18:41 PM Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
Jul 18, 2007 3:18:41 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
Jul 18, 2007 3:18:41 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:41 - ***********************************************************
07/07/18 15:18:41 - Start updating EAR file...
07/07/18 15:18:41 - start-up mode is lazy
07/07/18 15:18:42 - EAR file updated successfully for 1000ms.
07/07/18 15:18:42 - Start deploying ...
07/07/18 15:18:43 - EAR file uploaded to server for 891ms.
07/07/18 15:18:48 - Successfully deployed. Deployment took 5375ms.
07/07/18 15:18:48 - Application : sap.com/tc~workflowmodeler
07/07/18 15:18:48 -
07/07/18 15:18:48 - /Application/WorkflowModeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - com.sap.workflowmodeler.modeler - LOGGING CONFIGURATION
07/07/18 15:18:48 - workflowBean - EJB
07/07/18 15:18:48 - WorkflowConnection - EJB
07/07/18 15:18:48 - Modeler - WEB
07/07/18 15:18:48 - sap.com/tc~workflowmodeler monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:48 - ***********************************************************
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:49 PM Info: Starting to save the repository
Jul 18, 2007 3:18:49 PM Info: Finished saving the repository
Jul 18, 2007 3:18:49 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:49 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
Jul 18, 2007 3:18:49 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:49 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:49 - ***********************************************************
07/07/18 15:18:49 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
07/07/18 15:18:49 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:50 PM Info: Finished saving the repository
Jul 18, 2007 3:18:50 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:50 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
Jul 18, 2007 3:18:50 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:50 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Begin of log messages of the target system:
07/07/18 15:18:50 - ***********************************************************
07/07/18 15:18:50 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
07/07/18 15:18:50 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
Jul 18, 2007 3:18:50 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:50 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:51 PM Info: Finished saving the repository
Jul 18, 2007 3:18:51 PM Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
Jul 18, 2007 3:18:51 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
Jul 18, 2007 3:18:51 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:51 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Begin of log messages of the target system:
07/07/18 15:18:51 - ***********************************************************
07/07/18 15:18:51 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
07/07/18 15:18:52 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
Jul 18, 2007 3:18:52 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:52 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
Jul 18, 2007 3:18:52 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Failed deployment of SDAs:
development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
Please, look at error logs above for more information!
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 18, 2007 3:18:52 PM Error: -
At least one of the Deployments failed -
Jul 18, 2007 3:18:53 PM Info: Summarizing the deployment results:
Jul 18, 2007 3:18:53 PM Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
Jul 18, 2007 3:18:53 PM Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
Jul 18, 2007 3:18:53 PM Error: Processing error. Return code: 4
END DEPLOY_SLOT_0__DON_01.LOG----
I SAW the SDN forum and talk about the question
Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
but this one doesnu00B4t work
best regards
Luis Moreno

Hi
I resolved the issue by undeploying the TestSuiteUUIE component using SDM.
Thanks
Naresh P.

Problem with ECC 5.0 Upgrade in JOB_RASUVAR1 phase of PREPARE

I am upgrading 4.6B system (copy of production to build QA system) on Tru64 with 3TB Oracle DB. The JOB_RASUVAR1 phase of PREPARE in running for about 115 hours. This phase saves existing variants for future conversion. There is a job running at the SAP level which using a lot of CPU, but no active Oracle session for this job. The same job took less than an hour on development system (200GB DB). So far the response from SAP has been like "Unfortunatly there is no possibility to improve the performance of the reports RASUVAR1 and RASUVAR2 during the upgrade" because this phase does not happen during production downtime.
Did anyone else face similar problem?

Hi Kausik,
we recently upgrade our client systems from 4.6c to ECC 5.0, on unix environment. we too faced similar kind of problem, our job_rasuvar1 in prepare phase took almost 70hrs. after raising a msg with SAP, we were asked some correction in function module.."FASU_RS_VARIANT_CONTENTS"..check whether the following changes are already available..or not
the necessary change:
replace the line
PERFORM fill_tables_ps TABLES objects
with the line
PERFORM fill_tables_ps(saplsvar) TABLES objects "CHANGE
in function module FASU_RS_VARIANT_CONTENTS
2) To fix this issue I would recomment, that you stop the JOB_RASUVAR1.
Then please implement the corrections of note 712297. After this please
clear out all the entries in DB tables TASUVCAT, TASUVSVO and TASUVSVD.
You can do thie for example via transaction SE14.
Then implement the following modification to ABAP RASUVAR1:
FORM return_content USING taskname.
RECEIVE RESULTS FROM FUNCTION 'FASU_V_VARIANT_CONTENTS'
TABLES
valutab = gt_params
OBJECTS = gt_objects
EXCEPTIONS
syst_except = 1
communication_failure = 2
system_failure = 3
variant_non_existent = 4
variant_obsolete = 5
error = 6.
g_error = sy-subrc.
g_returned = 'X'.
data: l_count type i. "INSERT MOD
describe table gt_params lines l_count. "INSERT MOD
if l_count gt 20000. "INSERT MOD
g_error = 7. "INSERT MOD
endif. "INSERT MOD
ENDFORM. " return_content
After this you can restart the JOB_RASUVAR1 by just call report
please try with this & let me know. and 1 more thing, this phase again depends on database size (in our case, for 1.8TB it took 6hrs).
with regards,
Raj

Execution of Reports phase error during SAP EHP4 upgrade with EHPi

I started getting an error message in the "Execution of reports after put" phase
(within the Downtime phase) during the SAP EHP4 upgrade with Enhancement
Package Installer.
***** LIST OF ERRORS
AND RETURN CODES *****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPRB70104.OPQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "09064300") 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""09064300""OPQ" 1 ETP111 exit code : "12" >>> PLEASE READTHE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<< XPRAs are
application reports that run at the end of an upgrade.
Most XPRA reportshave 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
<<<
I tried to follow the instructions in note 1269960, but the enhancement spot
CLASSIFICATION_TOOL was already active. I activated it again and reran the phase
but got the same error. Also, I couldn't implement the note using SNOTE because it is
the middle of the upgrade process.
I also found the following long text in ST22
"Internal error during syntax check: ("//bas/710_REL/src/krn/gen/scsymb.c#11"
Processing had to be terminated because an internal error
occurred when generating the ABAP/4 program
"CL_CLS_BADI_CHARACTERIZATION==CP".
The internal system error cannot be fixed by ABAP means only."
I am on a 64 bit System with CentOS Linux. 8 GB RAM, 250 GB HD with 20 GB free space.
So far, I could not find any information on this. Any help would be greatly appreciated!
Thanks,
Victor

Hi Victor,
Go to SM37 and put in the username as DDIC and see the job log.
Also check Sm50 and see whether you have BTC processes available.
Last but not the least check your filesystem space usage too.
Gerard

Error while doing EHP4 upgrade in downtime phase

HI .
Iam facing the below error while doing the EHP4 upgrade , in downtime phase.
Checks after phase MAIN_SWITCH/STARTSAP_TRANS were negative!
Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 >
Connect to SAP gateway failed Connect_PM GWHOST=Hydhtc4526D, GWSERV=sapgw04, SYSNR=04 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.136.162.30:3304' not reached TIME Mon Jun 06 18:17:46 2011 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.136.162.30:3304 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER System start failed
Please help me in resolving this error.
Sanketh.

Hi,
Upgrade tool is trying to start the system but system is not coming up. Try to start system manually and see if system comes up or not. If not then check logs in work directory for why system is not coming up.
Thanks
Sunny

SAP ECC 6.0 Maintenance phase

Dear Experts,
We got notification from our EWA report that our SAP ERP 6.0 maintenance ended on 31.03.2013 as follows:
0.0.1 SAP Application Release: Maintenance Phases
SAP Product
SAP Product Version
End of Mainstream Maintenance
End of Extended Maintenance
SAP ERP
6.0
31.03.2013
31.03.2016
Your system P01 is running on SAP ERP 6.0. Mainstream maintenance for SAP ERP 6.0 ended on 31.03.2013.
Recommendation:
We recommend that you upgrade your system. For more information, see SAP Service Marketplace at service.sap.com/upgrade.
If you decide to continue using the current release, SAP offers extended maintenance for SAP ERP 6.0 from 01.04.2013 to 31.03.2016.
while SAP note 1648480 - Maintenance for SAP Business Suite 7 Software tells that the maintenance is extended to 2020, please also refer to link: SAP AU & NZ - SAP extends mainstream maintenance for SAP ERP 6.0 and Business Suite 7.0 until 2020
Please advise.
Regards,
Rudi

Dear Experts,
We got notification from our EWA report that our SAP ERP 6.0 maintenance ended on 31.03.2013 as follows:
0.0.1 SAP Application Release: Maintenance Phases
SAP Product
SAP Product Version
End of Mainstream Maintenance
End of Extended Maintenance
SAP ERP
6.0
31.03.2013
31.03.2016
Your system P01 is running on SAP ERP 6.0. Mainstream maintenance for SAP ERP 6.0 ended on 31.03.2013.
Recommendation:
We recommend that you upgrade your system. For more information, see SAP Service Marketplace at service.sap.com/upgrade.
If you decide to continue using the current release, SAP offers extended maintenance for SAP ERP 6.0 from 01.04.2013 to 31.03.2016.
while SAP note 1648480 - Maintenance for SAP Business Suite 7 Software tells that the maintenance is extended to 2020, please also refer to link: SAP AU & NZ - SAP extends mainstream maintenance for SAP ERP 6.0 and Business Suite 7.0 until 2020
Please advise.
Regards,
Rudi

ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
Thanks

Hi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

Sap Abap Upgrade

hi all
i am working on SAP ABAP Upgrade and facing problem with a data type RAW which is incompatible in
ECC6.0. Can anyone suggest a replacement for this data type.
Thanks a lot.

Hi,
You can use Char type if the data is in characteres or you can use HEX type if it contains numbers.

Can't find the created queries in SQVI after SAP GUI Upgrade

Hi all,
I have a problem when I update my SAP GUI (7.10 -> 7.20)
After the upgrade, I can't find anymore the queries in SQVI. The liste is totally emptied...
Could you help me to find them? Or plz, just tell me I deleted them T_T
Thanks in advence.

Hello Alexander,
Thank you for your reply, but the situation didn't change... it's really strange...
We used the same PC to logon with 720, I'm sure that the parameters of SAP GUI are good, everything works correctly except SQVI. No problem with LSMW or SCAT... The most important point, this problem appears on all PC with 720 upgrade! So, it's not a local problem...but we didn't touch anything on server...maybe it was just a coincidence, somebody did something on the server in the same time of SAP GUI Upgrade...
For now, we copied the lost queries from QUALITY (it's not the last version T_T but it's better than nothing!) And we still don't know where is the source of problem.
Anyway, thank you for your help.
Best regards,
Alu

Install problem with phase 27 - Install Java Engine

Hello All,
I am trying to install Netweaver CE71 EHP1 on a Windows 2008 server, but keep running into a problem on phase 27 of 39 the Install Java Engine.
Gives me the following error message in the dialog box:
An error occurred while processing option SAP NetWeaver CE Productive Edition > Installation Options > Standard System > Standard System( Last error reported by the step :Process call 'D:\usr\sap\DE2\J00\exe\jstart.exe pf=D:\usr\sap\DE2\SYS\profile\DE2_J00_EITMEDEV02 -file=D:\usr\sap\DE2\J00\exe\startup.properties -nodename=bootstrap -launch' exits with error code 8. For details see log file(s) jstart_bootstrap_J00.log.).
I did a system search for the jstart_bootstrap_J00.log and it is empty.
Any help would be appreciated.
Thanks,
Mike

Hi Mike,
Could you check the SAPInst installation directory (..\Program Files\SAP\sapinst_instdir\...\..\..) for latest updated files?
They may have information about the error.
Regards,
Srikishan

SAP R/3 Problem

I need some detail solutions and suggests about below these problems [SAP R/3] :
Problem 4: Problems in the installation of SAP R/3 Server
Problem 4.1: Computer Name of the SAP R/3 server has been changed after the full installation of Oracle 9i and SAP R/3.
Problem 4.2: A network card of a server was faulty and it was replaced by a new network card but the SAP R/3 license was expired.
Problem 4.3: You would like to reinstall SAP R/3 on a server which has previously installed with SAP R/3 but the same error message appears during the re-installation.

HI,
I don't know the answer to your questions, but these are more of a SAP Baisis question. I would suggest posting this question on the Basis forum.
Naing

DSL and 9.1 to 9.2 upgrade problems? Please Help!!

I have a Beige g3 - 300 w/ 160 megs of memory - using Netscape 7.02 and occasionally Gatesmess IE-5. I have had dial up for 5 years and recently upgraded to DSL w/ Linksys WRT54G router connected via ethernet cable. Wifes HP laptop uses the wireless.
Problem is when connected to the internet, I get a looong -(30 - 40 second) delay between selecting the url and the page loading with a "resolving host" message at the bottom of the page. The modem send light flashes every five seconds or so and once the system locks on the url it loads really fast. With the dialup there was no delay in finding the url but took a long time to load. Result is it takes about the same amount of time to browse now as before. I don't think the winbox is having the same problem.
To try to resolve the "resolving host" issue I have been trying to upgrade from 9.1 to 9.2. When I download the package from apple.com at the end I get a 127 error which reestablishes itself everytime I click OK til I force quit the System. When I restart the computer, the file is on desktop OS 9.2 update.smi. First I opened the file w/ stuffit 5.2 and tried to install it following the instructions (sharing off, OS 9 extensions only etc) and about 4 minutes into the process I get the Bomb error 10. I have downloaded this three times and upgraded the Stuffit to 7.03 but am having the same problem. In order to get to 9.2.2 you have to upgrade to 9.2.1 first and that is what I am doing.
Anybody have any ideas either on the "resolving host" issue or the upgrade problem.
Thanks in advance,
Beige g3 - 300mghz 160 meg memory Mac OS 9.1.x

Thanks Grant.
I read the article and it was of some help. Reference TCP/IP control panel settings. I called Commspeed support and they gave me their three current DNS numbers. I typed them per article and nothing - dead. Called them back and they gave me the typical winbox answers "No hable apple" so left to my own devices and considering the stratigies suggested in the article I did two things.
I opened the TCP/IP control panel and deleted the Name Server Address - As they are supposed to be assigned by the server. There was also a check box that said use 802.3 which was checked. I unchecked it and tried the internet. Blam it was right there. I don't know which stratigy worked as I did them simultaneously.
Still don't know about upgrading to 9.2.
Thanks again,
Bill
Beige g3 - 300mghz 160 meg memory Mac OS 9.1.x

Unicode kernel upgrade problem in XI server

Hi
I'm trying to upgrade the Brtools in XI server and getting the following problem:
rx2n0v4:xdvadm 23> SAPCAR -xvf DBATL640O92_45-10002837.SAR
stderr initialized
processing archive DBATL640O92_45-10002837.SAR...
--- Unicode interface [u16_get.c line 233] pid = 6963 :
Invalid UTF-8 encountered by fgetsU16 (fileno 0x4)
fd
Characters previously read:
0043 0041 0052 0020 0032 002e 0030 0031
0052 0047 030 0031
--- Unicode interface -
End of message -
Illegal byte sequence DBATL640O92_45-10002837.SAR
Couple of times, i downloaded the kernel today and tried but get the same error. Here XI (6.40)is the unicode server and i downloaded the unicode kernel from sapnet (brtools and SAPCAR kernel). I tried with version 7.00 kernel but get the same problem.
Any solution of this problem?
Regards
Amar

Confusion About SP16 Unicode Kernel Patch/Upgrade
Problem with updating XI 3.0 (Kernel etc.)
Check this might be useful.

Extraction from SAP, hidden fields problem

Hi Expeerts,
I have the following problem / question:
From an SAP Datasource (2lis_11_vaitm) we have some fileds, those are HIDED, and we need them. This is a central SAP, and a lot of BW systems connect to this SAP.
The problem is, that we need a field from that datasource (and other BWs do not need), that has 'HIDDEN' option. The SAP side is afraid of having problem, when they just uncheck that option. (TELF1; KONDA fields we need).
Does anyone know, what is the affects on other BW systems, when we unhide this fields? Of course we load with delta from this source.
If a field is hidden in SBIW-Maintain Datasources, am I right, that the delta does not collect those fields, or it is collected, just not sent to BW systems?
Any good idea, how can we get that fields in other way, because it seems, that the datasource cannot be modifyed, because of the other countries' BWs, connected to teh centra SAP.
I hope i were clear, but if not, please ask me.
Thanks for Your help.
Laszlo
Edited by: László Györkös on Jan 30, 2009 11:07 AM

Hi,
If a field is hidden in SBIW-Maintain Datasources, am I right, that the delta does not collect those fields, or it is collected, just not sent to BW systems?
--> As hidden fields are already available in extract strucute, unhiding will not create any problem. As far as i know hidden means it will transfer data from extract structure to further.
--> You can try pulling this particular data using generic datasource. OR
--> Enhance datasource by adding required fields and use. OR
--> Unhide files and use.
Note: Bit careful while transpporting datasource to production as time stamp changes.
Srini

SAP BW upgrade problem in phase lang_select

Similar Messages

Maybe you are looking for