Error in upgrade in TOOLIMPD3 phase

hi all,
we are getting eror in TOOLIMPD3 phase while doing upgrade.
as per the log....
ERROR: 1 activities have been aborted in TOOLIMPD3.
ERROR: Operation(s) not completely processed.
       Remaining change requests found in buffer PRD.
       Ignoring aborted import steps will cause severe inconsistencies
       and will likely require a full repeat of the whole upgrade.
       !!! Do not manipulate the import buffer !!!
       Analyze summary error logfile TOOLIMPD.ELG
       and remove all error conditions in the way
       it is described in the upgrade manual. Repeat
       this phase until it is error free.
       Additional hints may be given in logfiles
       SLOG700 and /usr/sap/put/log/SAPup.ECO
as per the log..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA700VTA.PRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 ETP111 exit code           : "12"
we are unable to find any other specific log other than this.
thanks,
srikanth.

Hi srikanth,
The upgrade seems stoped at the DDIC ACTIVATION phase.
Check log files
SAPA700VTA.PRD
TOOLIMPD.ELG
SAPup.ECO
It will give you the error information.
Check also the for the import for DDIC Activation failure.
Regards
Ashok

Similar Messages

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

SCM5.0 Upgrade error in PREPARE IMPORT / CNV_CHK_IMP Phase

Hi,
we are upgrading from APO 3.1 to SCM 5.0 upgrade.
we are running PREPARE and getting this error during the PREPARE / Import Phase.
PE0353ERROR: Outstanding DB conversions found.
All converter entries are listed in /usr/sap/put/log/TBATGCHK.LOG.
Proceed as described in the upgrade manual and repeat this phase
until all converter entries are removed.
This is the entry in TBATGCHK.LOG file
pg TBATGCHK.LOG
CONV ENTRY TBATG ENQU/SAPAPO/E_OMUPGR                 0CNVI 20080920DDIC
CONV ENTRY TBATG ENQUESICNV                           0CNVI 20080920DDIC
and the entry in TBATG table in sap is as below
Object type Object name   Index ID Sequence Function Backg. or upgrade Date       Req. by
ENQU        /SAPAPO/E_OMUPGR            0        CNV      I                        09/20/2008 DDIC
ENQU        ESICNV                                  0        CNV      I                        09/20/2008 DDIC
Could anyone suggest on this.. Any help is welcome.
Regards,
Sandeep.

this issue is resolved with solution from other thread.
The proble is not with table TBATG. The problem is with object ENQUESICNV. You can enter transaction code SE11 and activate the lock object "ESICNV" manually. After that you can repeat the Upgrade phase.
prepare error
Thanks,
Sandeep.
Edited by: Sandeep Soman on Sep 21, 2008 1:44 AM

ERROR in ADD-ON conflict phase while upgrading ECC 6.0 system

Hi all,
I am having ECC 6.0 system and am upgrading its SAP-APPL component to 603 patch level 03. I was having SAP-APPL 603 but at patch level 0, i checked for all dependencies and defined the queue in SPAM and it showed all green (OK) for SAP-APPL and so i started but i faced error in add-on coflict phase. It said CRT needed for ADD-ON FICAX release 603. I searched alot but i cant find it on market place. This conflict occured for SAP-APPL 603 patch level 01 it said either include CRT as mentioned above or remove SAP-APPL 60301. Please help me out.

The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60301.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60302.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60303.
Check the support packs of components FI-CAX on Service Market place, I think FI-CAX is dependant on SAPKH603301 and others so you can check the import condidtions of FI-CAX on service marketplace and update FI-CAX first then only you would be able to update patch of SAPKH60301
Regards
Subhash

Error while executing SDM process phase with action DEPLOY_SLOT

Hi,
I am upgrading CRM 2007 to CRM 7.0 and got an error in Java side.
Following is DEPLOY_SLOT_1_DON_01.LOG
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG]/>
<!PATTERN[DEPLOY_SLOT_1__DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
May 20, 2009 4:15:48 AM Info:
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: = Starting to execute command 'deploy' =
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: Starting SDM - Software Deployment Manager...
May 20, 2009 4:15:49 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
May 20, 2009 4:15:51 AM Info: SDM operation mode successfully set to: Standalone
May 20, 2009 4:15:52 AM Info: Initializing Network Manager (50017)
May 20, 2009 4:15:52 AM Info: Checking if another SDM is running on port 50018
May 20, 2009 4:15:53 AM Info: -
Starting deployment -
May 20, 2009 4:15:53 AM Info: Error handling strategy: OnErrorSkipDepending
May 20, 2009 4:15:53 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
May 20, 2009 4:15:53 AM Info: Update strategy: UpdateLowerVersions
May 20, 2009 4:15:53 AM Info: Starting deployment prerequisites:
May 20, 2009 4:15:55 AM Info: Loading selected archives...
May 20, 2009 4:15:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA'
May 20, 2009 4:16:43 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA'
May 20, 2009 4:16:48 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA'
May 20, 2009 4:16:50 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA'
May 20, 2009 4:17:00 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA'
May 20, 2009 4:17:02 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA'
May 20, 2009 4:17:13 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA'
May 20, 2009 4:17:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA'
May 20, 2009 4:17:31 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA'
May 20, 2009 4:17:35 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA'
May 20, 2009 4:17:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA'
May 20, 2009 4:18:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA'
May 20, 2009 4:18:04 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA'
May 20, 2009 4:18:08 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA'
May 20, 2009 4:18:09 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA'
May 20, 2009 4:18:10 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA'
May 20, 2009 4:18:13 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA'
May 20, 2009 4:18:20 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA'
May 20, 2009 4:18:26 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA'
May 20, 2009 4:18:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA'
May 20, 2009 4:18:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA'
May 20, 2009 4:18:50 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA'
May 20, 2009 4:18:51 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA'
May 20, 2009 4:18:56 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA'
May 20, 2009 4:19:03 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA'
May 20, 2009 4:19:10 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA'
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
May 20, 2009 4:19:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA'
May 20, 2009 4:19:48 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA'
May 20, 2009 4:19:49 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA'
May 20, 2009 4:20:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA'
May 20, 2009 4:21:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA'
May 20, 2009 4:21:39 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA'
May 20, 2009 4:23:18 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA'
May 20, 2009 4:23:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA'
May 20, 2009 4:23:27 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA'
May 20, 2009 4:23:33 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA'
May 20, 2009 4:23:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA'
May 20, 2009 4:23:54 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA'
May 20, 2009 4:23:58 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA'
May 20, 2009 4:23:59 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA'
May 20, 2009 4:24:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA'
May 20, 2009 4:24:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA'
May 20, 2009 4:24:05 AM Error: Error while loading selected archives.
May 20, 2009 4:24:05 AM Error: Prerequisites were aborted.
May 20, 2009 4:24:13 AM Error: Error while loading selected archives.
May 20, 2009 4:24:13 AM Info: Summarizing the deployment results:
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA
May 20, 2009 4:24:13 AM Error: Precondition violated: C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA
May 20, 2009 4:24:13 AM Error: Processing error. Return code: 4
It appears to me that somehow there is a component conflict:
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
Is it advisable at all to manually delete the above LMTOOLS03_01.SCA from the location and try again or this will lead to more errors?
Please help ASAP, thanks a lot,
Shival

Following is the trouble ticket information:
Trouble Ticket Report
Upgrade to Enhancement Package 1 SR1 for SAP NetWeaver/ SAP Business Suite 7 SR1
SID................: CD1
Hostname...........: nbg-dev-cd1
Install directory..: c:/usr/sap/CD1
Upgrade directory..: C:\usr\sap\jupgrade
Database...........: SAP DB
Operating System...: NT
JDK version........: 1.4.2_15 Sun Microsystems Inc.
SAPJup version.....: 1.5.6
Source release.....: 700
Target release.....: 700
Current usages.....: AS;EP;EPC;BP-CRM;JCRM;AAS
ABAP stack present.: true
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters C:/usr/sap/jupgrade/tmp/SLOT.DEPLOY.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 C:\usr\sap\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 C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade

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.

Error in upgrade slm4.0

Hi all,
We encountered an error during upgrade solution manager 4.0.
Our OS is Windows 2003 server and Database is DB2.
We have upgraded the central instance successfully and then installing java Components, but the installation end with the following eroor.
We have refered to some documents about CJS-00030, but we can find anything do really help for our case.
Please help me!
ERROR 2007-10-30 09:02:02.687
CJS-00030 Assertion failed: in
function (role) {
 NWUsers.trace("NWUsers.getAccountData(", role, ")");
 this._initAccountData();
 ASSERT(arguments.callee, this.haveAccountData(role), "role " + role + " is not created yet.");
 var ad = this._readAccountDataFromKeydb(role);
 ad = this._readAccountData(ad);
 var masterpwd = this.getMasterPassword();
 if (ad.password == "" && this._useMasterPasswordForAccountData(ad) && ad.type == "USER" && masterpwd !== undefined && role != NWUsers.roles.J2EEGuest && !ad.locked) {
 ad.password = masterpwd;
 NWUsers.trace("NWUsers.getAccountData(): ", dump_properties(ad));
 return ad;
role DB6_DB2SID is not created yet.
ERROR 2007-10-30 09:02:02.687
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-10-30 09:02:02.703
FCO-00011 The step dialogPreconditions with step key |NW_Addin_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|7|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB6|ind|ind|ind|ind|5|0|dialogPreconditions was executed with status ERROR .
INFO 2007-10-30 09:08:42.609
An error occured and the user decide to stop.\n Current step "|NW_Addin_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|7|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB6|ind|ind|ind|ind|5|0|dialogPreconditions".
Regards,
Terry

hi Siddhesh,
 Thanks for you help.
 We have checked the user and password and redo it, the same error still standing in the phase.
 We have refered to Note 921594, it talk about the likely error and tell me to modify the control.xml. But in that case it is ORA DB, in my case it is DB2.
Any idea?
Best Regards,
Terry qin

Error in Upgrade to PI 7.1EHP1 in CHECK_AVAILABLE_FREE_SPACE Step.

Hello Experts,
We are Upgrading PI7.0 to PI7.1 EHP1 in that we are facing error in "PREPARE/CHECKS/CHECK_AVAILABLE_FREE_SPACE" phase in "Checks" Step is occured
Following is TroubleTicket_09.txt
================================================================================
Trouble Ticket Report
Upgrade to SAP NetWeaver 2007
SID................: JRX
Hostname...........: jsplnode1
Install directory..: /usr/sap/JRX
Upgrade directory..: /oracle/upg/java
Database...........: Oracle
Operating System...: UNIX
JDK version........: 1.5.0_20 Sun Microsystems Inc.
SAPJup version.....: 2.1.15
Source release.....: 700
Target release.....: 710
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....: AS;PI;AAS;AAS
ABAP stack present.: true
The execution of PREPARE/CHECKS/CHECK_AVAILABLE_FREE_SPACE ended in error.
*Can not invoke getUsableSpace(String ...) method.*
java.lang.reflect.InvocationTargetException
java.lang.NoClassDefFoundError: com/sap/jvm/impl/monitor/vm/natives/VmNatives
=========================================================================
Can any one plese help me in this...As this error has stoped Upgrade and i have dedline to catch..........
waiting for the reply ...
Tnx in advance.......
Anupam Parekh

I assume you need to make sure that you are performing the upgrade with the SAP JVM. You do not need a separate Sun JDK next to the SAP JVM because SAP JVM is a complete Java environment.
So you could try to deinstall the Sun JDK, to make sure you are using the right JVM for your upgrade.
Note that I did not check any install notes. It is just an assumption out of your exception traces. Maybe the install docs will tell you more about the needed JVM.
CSY

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

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

Error in PREP_EXTENSION/EHP_INCLUSION! phase

Hi Experts,
I am in Support pack stack upgrade activity from SPS10 to SPS11 through SUM.Our environment is ERP6.0-->Ehp5,OS400,DB2.
I am getting error in PREP_EXTENSION/EHP_INCLUSION! phase.
Last error code set: Disassembling patch queue failed rc = 3, reason = 'Error when creating cofile for transport request SAPKITAB7J' If you put new packages in the download directory, use option 'init' to upload them .
Can some one please help me to resolve the issue.

Hello
2WETQ399 File '/z_tmp/SPS11_SE4/KGS6024' size 0kB could not be recognized!
2WETQ399 File '/z_tmp/SPS11_SE4/KH60511' size 0kB could not be recognized!
2WETQ399 File '/z_tmp/SPS11_SE4/KITAB7J' size 0kB could not be recognized!
2EETQ095 Disassembling package queue failed, rc = "3", reason = "Error when creating cofile for transport request SAPKITAB7J"
4 ETQ399 Deleting '/DEV4DD0/usr/sap/SE4/SUM/abap/data/RITAB7J.SAP'.
1EETQ399 Last error code set is: Disassembling patch queue failed rc = 3, reason = 'Error when creating cofile for transport request SAPKITAB7J'
I see most of the files with 0 KB size.
Try updating the SAPCAR file.
If you have uploaded a newly downloaded package then stop the SUM tool completely.
Restart the SUM tool and start the phase again.
You need to make sure all the packages are good and there is enough free space in the transport directory.
Regards
RB

Error during upgrade from OBIEE 10G to 11G

Hello All
I ran into this issue while trying to upgrade my 10g RPD and catalog to 11.1.1.7
After installing 11G, I launched the upgrade utility from Oracle_Common/bin/ua in linux.
I am getting the below error:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Based on the Oracle Doc. it has the following desc:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.
Action: None.
Level: 1
Type: ERROR
Impact: Upgrade
So what should I do to resolve this issue?
Thanks in advance

Hi,
First of all i am not familiar on linux box.
I tried in windows environment the rpd is deployed with out any errors.
But i ran the ua.bat file in the following path
\MWHOME\Oracle_BI1\bin\ua.bat.
while i am running in oracle_common\bin\ua.bat is not responding in my local system.
Please Mark if it helpful.
Thanks

Error while upgrading to 10.1.3.5

I am getting error while upgrading to 10.1.3.5.
getting error while configuring OWSM. here is the error log.
*09/09/28 14:28:53 Notification ==>Application Deployer for coreman STARTS.*
*09/09/28 14:28:53 Notification ==>Undeploy previous deployment*
*09/09/28 14:28:58 Notification ==>Initialize /space/oracle11bpel/j2ee/oc4j_soa11wf/applications/coreman.ear begins...*
*09/09/28 14:28:58 Notification ==>Initialize /space/oracle11bpel/j2ee/oc4j_soa11wf/applications/coreman.ear ends...*
*09/09/28 14:28:58 Notification ==>Starting application : coreman*
*09/09/28 14:28:58 Notification ==>Initializing ClassLoader(s)*
*09/09/28 14:28:58 Notification ==>Initializing EJB container*
*09/09/28 14:28:58 Notification ==>Loading connector(s)*
*09/09/28 14:28:58 Notification ==>Starting up resource adapters*
*09/09/28 14:28:58 Notification ==>Initializing EJB sessions*
*09/09/28 14:28:58 Notification ==>Committing ClassLoader(s)*
*09/09/28 14:28:58 Notification ==>Initialize coreman begins...*
*09/09/28 14:28:58 Notification ==>Initialize coreman ends...*
*09/09/28 14:28:58 Notification ==>Started application : coreman*
*09/09/28 14:28:58 Notification ==>Binding web application(s) to site default-web-site begins...*
*09/09/28 14:28:58 Notification ==>Binding web application(s) to site default-web-site ends...*
*09/09/28 14:28:58 Notification ==>Deleting: /space/oracle11bpel/j2ee/oc4j_soa11wf/applications/coreman.ear*
*09/09/28 14:28:58 Notification ==>Deleting: /space/oracle11bpel/j2ee/oc4j_soa11wf/applications/coreman/coreman.war*
*09/09/28 14:28:58 Notification ==>Begin adding application: coreman to container runtime for: oc4j-develop-12420-default*
*09/09/28 14:28:58 Notification ==>Operation failed with error:*
Unable to find/read file META-INF/ra.xml in /space/oracle11bpel/j2ee/oc4j_soa11wf/connectors/coreman/coreman archive (IO Error: error in opening zip file)
Deploy error: Deploy error: Operation failed with error:
Unable to find/read file META-INF/ra.xml in /space/oracle11bpel/j2ee/oc4j_soa11wf/connectors/coreman/coreman archive (IO Error: error in opening zip file)
I checked the Connectors directory for coreman but its not available. I even checked with my previous successful installations for this directory, its not even there too.
The only difference i found in the error logs and the successful logs is ..
*09/09/28 14:28:58 Notification ==>Begin adding application: coreman to container runtime for: oc4j-develop-12420-default*
I did not see this line in the success log.
Here is my environment information.
I have an OPMN clustered environment. The second node in the cluster was down while this upgradation.
There are two groups -- default_group and abcbpel_group
abcbpel_group contains the soa instance. while default_group contains home instance.

Hi.
I have the same problem too.
Had You found the solution?

Error while upgrading Portal from 10.1.2 to 10.1.4

This is the error message I am getting when I try to upgrade portal from 10.1.2 to 10.1.4 by applying the patch.
NOTIFICATION:1 Framework: Error: Component upgrade failed PORTAL
NOTIFICATION:1 Framework: Error: PORTAL component version is: 10.1.2.0.2 INVALID.
Please let me know if any has has a solution?
==========================================
D:\Software\Oracle\IDM\as_windows_x86_portal_1014\mrua_051020\mrua>mrua.bat -ora
cle_home D:\Software_Installations\OraHome_Infra_01 -oid_host <hostname> -oid_ssl_port 636
Executing mrua.pl
Running on Windows
OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.0
Enter the password for SYS:
Enter the password for cn=orcladmin:
Enter the password for cn=orcladmin:
Upgrading the OracleAS Metadata Repository to release 10.1.4.0.0
Calling upgrade plugin for MRUA
Component has already been upgraded MRUA
Calling upgrade plugin for PORTAL
Error: Component upgrade failed PORTAL
Error: PORTAL component version is: 10.1.2.0.2 INVALID
Calling upgrade plugin for MRC
Component has already been upgraded MRC
FAILURE: Some OracleAS plug-ins report failure during upgrade.
Log file: D:\Software_Installations\OraHome_Infra_01\upgrade\logs\mrua2007-07-1
3_02-07-15PM.log
Finished mrua.pl

That didn't help for me....
I have those things shut down already and you can see below what I'm getting on the re-run:
-bash-3.00$ /app/oracleas/as1012portal/bin/emctl stop iasconsole
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.2 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://asdev:1811/emd/console/aboutApplication
Stopping Oracle Enterprise Manager 10g Application Server Control ...
Cannot determine Oracle Enterprise Manager 10g Application Server Control process; /app/oracleas/as1012portal/bin/emctl.pid does not exist.
Oracle Enterprise Manager 10g Application Server Control may not be running.
-bash-3.00$ /app/oracleas/as1012portal/opmn/bin/opmnctl stopall
opmnctl: opmn is not running
-bash-3.00$ mrua/mrua.sh -oracle_home /app/oracleas/as1014metadatarepository -oid_host asdev -oid_ssl_port 636
Executing mrua.pl
Running on UNIX
OracleAS Metadata Repository Upgrade Assistant 10.1.4.0.0
Enter the password for SYS:
Enter the password for cn=orcladmin:
Upgrading the OracleAS Metadata Repository to release 10.1.4.0.0
Calling upgrade plugin for MRUA
Component has already been upgraded MRUA
Calling upgrade plugin for PORTAL
Error: Component upgrade failed PORTAL
Error: PORTAL component version is: 10.1.2.0.2 INVALID
Calling upgrade plugin for MRC
Component has already been upgraded MRC
FAILURE: Some OracleAS plug-ins report failure during upgrade.
Log file: /app/oracleas/as1014metadatarepository/upgrade/logs/mrua2007-10-23_00-42-55PM.log
Finished mrua.pl
-bash-3.00$ grep PORTAL /app/oracleas/as1014metadatarepository/upgrade/logs/mrua2007-10-23_00-42-55PM.log
2007/10/23 12:43:06.236 CST NOTIFICATION:1 Framework: Calling upgrade plugin for PORTAL
2007/10/23 12:43:28.203 CST NOTIFICATION:1 Framework: Error: Component upgrade failed PORTAL
2007/10/23 12:43:28.209 CST NOTIFICATION:1 Framework: Error: PORTAL component version is: 10.1.2.0.2 INVALID
There is another oracle instance we have, the one that is hosting the LDAP server, and after the above I also tried doing a stopall there, then bringing up only the ldap server which is required for the upgrade, and then shutting down the iasconsole for that instance too so that only the ldap server remained, then re-running the portal upgrade. It didn't help.
Any ideas?

11.1.0.6.0 - 11.1.0.7 dbua error while upgrading

hello all i'm attempting to upgrade 11.1.0.6.0 to 11.1.0.7 and once in dbua i'm at upgrade process 85%, and i'm receiving this error:
database upgrade assistant:
ORA-04043: Object XDB_DATASTORE_PROC does not exist , ignore | Abort
i'm not too sure what i should do at this point, any help is appreciated
this is a linux 32bit machine/db

Welcome to the forums !
Pl see MOS Doc 360907.1 (catupgrd.sql gives error on XDB_DATASTORE_PROC ORA-4043)
HTH
Srini

Error in upgrade in TOOLIMPD3 phase

Similar Messages

Maybe you are looking for