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.

Similar Messages

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

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.

ECC 6.0 upgrade problem with outbound idocs

We are currently in the process of upgrading from 4.6C to ECC 6 and have found that our outbound idocs that use to process immediately are now pending in status 30. Message type DEBMDM is one of the several outbound messages that has the issue. Any ideas of what may have changed between 4.6C and ECC 6 that may have caused this to occur?

Hi Boss,
This problem is with Upgrading only . so, i can give two solutions for this .
1. create Background job with RSEOUT00 Executable program
and give the time like 2 min or 5 min (your choice)
2. check your code like includes in that code call the two Function modules that is DB_COMMIT
DEQUEUE_ALL
Try with this,,,,,,,,,,,,,
Best Regards,
Narasimha Rao.

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.

SRM 4.0 upgrade to SRM 7.0 - Error in Phase PARDIST_SHD

Hello,
I am upgrading the SAP SRM 4.0 / MSSQL 2005 / Windows 2003 (64 bit) to SRM 7.0 but I am getting this error in the phase PARDIST_SHD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISTRIBUTION ERRORS and RETURN CODE in DS100310.SD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEDA300 No active nametab exists for "CDBC_LANG_TABLES"
Long text:
    Cause
      Thee is no active nametab in the system, although an
      active ABAP/4 Dictionary object was expected.
    System Response
      None
    What to do
      Reactivate the ABAP/4 Dictionary object.
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CDBC_LANG_TABLES":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_ADJCONT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_ADJCONT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_HH_SRV_SYNC"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_HH_SRV_SYNC":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_PROCESSFLTT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_PROCESSFLTT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "CRMC_PROCESS_FLT"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "CRMC_PROCESS_FLT":    Action: "DNA"      Mode flag: "R"    Return code: "9"
2EEDA300 No active nametab exists for "IPCE_MON_NODES"
Long text: see above
2EEDA432 Termination due to inconsistencies
2EEDA471    Result   "IPCE_MON_NODES":    Action: "DNA"      Mode flag: "R"    Return code: "9"
What will I do now? How will resolve this issue? Please help me ASAP
Thanks
Gautam

Go to SE11, Menu->Utilities->Database Object->Check
            Menu->Utilities->Runtime Object->Check
If there are inconsistency, please follow note 211492 to adjust the inc
onsistency in original instance . But if these tables are obsolete,
for example doesn't exist in the system any more, you could also choose the option to 'Ignore' the error and
continue with the upgrade. But this is a BC-UPG issue.
Regards
Lauren

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

ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

Hi
We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
3 ETN256 You want to install the following add-on components:
3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
level: "0" (component type "A")
3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
level: "0" (component type "A")
2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
(type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
3 ETN245 The following import prerequisites of OCS Package "SAPK-
523EXINVIRSAHR" have not been met:
3 ETN264 In the (alternatively) Requirement set "01":
3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
software component vector
1 ETN214X."**************************************************"
We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
Any ideas?
Regards
Chandu

Hi
This is what the solution provided by SAP Support:
Quote:
we have finally found the problem, it's a bug in the package upload
functionality used by the upgrade. The consequence of this bug is that
Support Packages whose EPS files (.PAT files) have a certain string in
the name, namely the string 0000000 after the _ and before .PAT
extension, are not properly uploaded to the ABAP system and hence are
not visible or known to the upgrade.
This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
Check your EPS/in directory after the CAR/SAR Archives of the SPs are
extracted and rename all .PAT and .ATT files, which have a name like
*_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
Afterwards, the upgrade will upload the informations about the SP
properly and the SP can be included into the upgrade.
Files:
31/01/2007 07:32 329 VS30020106486_0000000.ATT
31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
If these two files are renamed to e.g.
VS30020106486_9000000.ATT
VS30020106486_9000000.PAT
the affected VIRSANH SP2 is uploaded correctly by the upgrade
functionality and the SP inclusion of the VIRSANH SPs works.
Sorry, as of now I cannot promise you a date when the tool fix will be
available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
Afterwards, I will know more...
Unquote:
Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
Regards
Chandu
Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

ECC 6.0 Upgrade from 4.7 - EDI Interfaces

Hi Gurus,
Need your inputs on what are the precautions to be taken during ECC 6.0 Upgrade related to EDI Interfaces. with SAP upgrading from 4.7 to ECC 6.0, do you see any precautions need to be taken considering the middle ware involvement. Also, is there any changes in IDOC Structures in ECC 6.0 which my cause issues related mapping with middleware.
Please suggest.
Thanks & Regards,
C.L. Narasimhan "CLN"

Hi,
generally, a release upgrade, delivers new idoc/message types or new releases of existing idoc/message types.
So, taking this in mind, you shouldn't have problems for the mapping of the messages, because the versions of the basic idoc, once released, cannot be changed.
You might have some application problems related to the inbound interfaces, but this is part of the game...the testing phase will highlight whether the problem exists.
A known problem is that the upgrade removes all the customer specific entries in the system table EDIFCT.
Further details are provided in the OSS note [https://service.sap.com/sap/support/notes/865142]
Regards,
Andrea

Upgrade error in Phase STARTSAP_NBAS

Dear Experts,
We are doing ECC 5.0 upgrade to ERP6.0 SR3 and during STARTSAP_NBAS phase DDIC locking out and cant start SAP original system. We tried to unlock the password and also did the reset using SAPup reset DDICpwd. But its still locking out. and through SU01 its not allowing to reset the password of DDIC user using SAP* and its showing " adress is inconsistant".
Please help
Regards,
Pillai.

Hi,
Could you try the steps from below thread?
STARTSAP_NBAS DDIC password locking out
Also, when you try resetting the password from SAPGui - do you get a dump in SU01? The address inconsistency warning can
be skipped in my opinion.
Regards,
Srikishan

4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

Dear all,
We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
I shall modity the same to our customer and submit
Thanks & Regards
Senthil
[email protected]

Preparation Phase* 6 days
Kick Off Meeting 1 day
Upgrade Project Procedures Preparation 1 day
Prepare Upgrade Project Plan 1 day
Technical Requirements Assessment 3 days
Assess Training needs of Key-users & End-users 1 day
Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
Business Blueprint Phase 6 days
Develop System Landscape Upgrade Plan 1 day
Functional Requirement Checklist 1 day
ABAP Development check list 1 day
Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
Identify Testing Scope & Scenarios 1 day
Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
Develop Documents as per Basis Activity List 1 day
Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
Prepare Upgrade Deliverables Checklist 1 day
Realization Phase 28 days
Installation of Solution Manager 3.2 System 1 day
Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
Upgrade Frontend Software 4 days
Perform SPAU & SPDD Corrections 5 days
Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
Perform Upgrade Testing for each Application Module 7 days
Perform Unit & Integration Testing 6 days
Perform Training to Key Users & End Users (Generic & Specific) 3 days
Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
Testing by end users on Quality System 1 day
Production Realization & Go-Live Phase 6 days
Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
User Acceptance Testing 1 day
Production System Go-Live 1 day
Post Go-Live Support 14 days
Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

Load balancing after ECC 6.0 upgrade

Hi
I we this configuration on ECC 6.0 upgrade:
SAPGUI 7.10
SAP_BASIS 700 Patch level 15
SAPportal ESS
Webdispatcher Installed
Internal ITS
Single sign-on
Can somebody assist as with identifying the problem with load balancing (PUBLIC) E.g. When running ESS remuneration package via the Sapportal. we have configured ITS-Based GUI Services on transaction SICF for customised ZESS_PZ11PDF service.
When we have load balancing group on the load balancing does not work, because I see somebodyu2019s payslip
but when using one app server I see my own payslip. Please help.

Hi PR,
Please take a look at the following link:-
http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/28/75153a1a5b4c2de10000000a114084/frameset.htm
"You can only use the SAP message server for HTTP load distribution if
the browser is the direct client of the message server. If another
component lies between the client (browser) and the message server, (for
example, the portal), you cannot use the message server to distribute
the load."
When using the External ITS you could balance the load using the message server and logon groups. In 700 this functionality is not present if there is not a direct connection to the client (Firefox or IE). So you will have to install the webdispatcher to balance the load.
Hope this helps
Michael

Webgui service fails in ECC 6/0 upgraded from ECC 5.0.

Our webgui service worked fine in our ECC. 5.0 system, however after the upgrade to ECC 6.0, the WebGui service fails. Has anyone experienced this? I've found other threads that said to change the WebGui service parameters, however, I'm not sure what the correct parameters are since the one's I have are from a ECC.5.0 system and not from and ECC 6.0 system.

Problem resolved...you need to publish the service "SYSTEM" and "WEBGUI" in se80 after a SP upgrade.

ECC 6.0 Upgrade - FI Posting (Payroll)

Hi,
We have gone for ECC 6.0 upgrade and face problem with FI Postings(Posting not cleared). We found out that in the new version there is a new node that got added up where we need to add all US taxes(Payroll US -> Posting to Financial Accounting ->Define WT posting attributes).
How can i find which all wage types are US tax related. I know there is one processing class 72, which define Employer / employee tax, but is there any other way i can find out.
Thank you
Sreeja

Hi Ted,
I am talking about GB payroll, so we have to defnitely maintain the tax wagetypes in the new table V_T7US3PRTXSYMKO. Apart from that do we need to do any other settings in FI. Because it is showing the Profit center not filled.
We have also maintained the v_t52swcodist .
-Swetha

This is regarding upgrading problem

Hi,
This is regarding upgrading problem.
I am Upgrading 4.7EE IDES to ECC 6.0 but I got the problem with Solman key
When I given the Solmman key it shows illegal solman key. what is the problem ?
system Id    -
>   F06
nstance number --->    30
Hostname is -
>      saibaba
Thanks,
Narshiha rao

Hi,
You genereate new solman key according to your system name and put that. This will work very well. Because when we create solman key then we have to define what is server name etc.
Anil

ECC 6.0 Upgrade - Problem in phase PARDIST_SHD

Similar Messages

Maybe you are looking for