Error in ecc upgrade phase

Hi,
while upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
Starting shadow system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
      SAPup error message
SAPup> ERROR: Starting system failed, rc=0
              To analyse the errors during start of shadow instance,
              view files 'STARTSFI.LOG' and 'DEVTRACE.LOG'
              in directory '/dsttemp/put/log'
              Repeat phase until shadow instance is started
              and you can log on instance number '21'.
            - "continue"
            - "cancel"
Enter one of these options [continue] :=
===============================================
===============================================
ERROR in PHASE STARTSAP_IMP
================================
=================================
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
       It is recommended that you repeat phase STARTSAP_IMP
       You can exit and restart the phase after the errors
       have been corrected. Alternatively, if you know that
       the error is not of concern, you may ignore it
       and continue with phase REPACHK2
              You are urged to repeat phase STARTSAP_IMP !
            - "repeat"
            - "init"
            - "exit"
            - "ignore"
Enter one of these options [repeat] := init
14:50:31 UPGRADE/EUIM: END OF PHASE   STARTSAP_IMP
14:50:31 UPGRADE/EUIM: START OF PHASE STARTSAP_IMP
Starting system ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
waiting 20 seconds for system to come up ...
testing if system is available ...
      SAPup error message
SAPup> SYSTEM START failed, code -2
                    -2: the test rfc did not work.
                    Try to log on to the system with user DDIC.
            - "continue"
            - "cancel"
Enter one of these options or "help" [continue] :=
Enter one of these options or "help" [continue] :=
      SAPup message
SAPup> CHECKS AFTER UPGRADE PHASE STARTSAP_IMP WERE NEGATIVE !!!
       It is recommended that you repeat phase STARTSAP_IMP
       You can exit and restart the phase after the errors
       have been corrected. Alternatively, if you know that
       the error is not of concern, you may ignore it
       and continue with phase REPACHK2
              You are urged to repeat phase STARTSAP_IMP !
            - "repeat"
            - "init"
            - "exit"
            - "ignore"
Enter one of these options [repeat] :=
Appreciate for an immediate response ...
Thanks in advance

while upgrading ECC 4.7 to ECC 6.0, I am not able to start shadow instance. Following error is giving .
Aditionally I can able to open the shadow instance from GUI lavel. But unable to login through DDIC password. The ddic password has been locked. Can anyone advice me how to unlock the ddic password in the upgrade phase.
This doesn´t make sense. If you can´t start the shadow instance then you can´t logon to the system
Try the following:
cd <put-directory>/bin
./SAPup stopshd
set the parameter
login/no_automatic_user_sapstar = 0
in the instance profile of the shadown instance
then start the shadow instance
cd <put-directory>/bin
./SAPup startshd
Unlock the shadow instance using
./SAPup unlockshd
Try to logon with user SAP* and unlock DDIC.
Markus

Similar Messages

Error during the upgrade phase "start_shdi_first"

Hello,
We are having issue with upgrading r/3 4.7 enterprise extension set to ECC 6.0
Here the error message goes....
starting system failed rc=0
to analyse the error during start of shadow instance
view files 'Startsfi.log' and 'devtrace.log'
in directory usr\..put
repeat phase until shadow instance is started
and u can logon instance no '01'"
We have changed the DDIC password during upgrade.after that we ran the initphase to update the password.
I think sapup is referring the old password which was entered initially during the upgrade and we dont remember the old password also.
Appreciate your response
Startsfi.log
1 ETQ201XEntering upgrade-phase "START_SHDI_FIRST" ("20080218175653")
2 ETQ366 Connect variables are set for shadow instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399   dbs_mss_schema=de4
4 ETQ399   auth_shadow_upgrade=1
4 ETQ399 Set environment for shadow connect:
4 ETQ399 ENV: dbs_mss_schema=de4
4 ETQ399 ENV: auth_shadow_upgrade=1
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399   default TPPARAM: SHADOW.TPP
4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
2 ETQ399 Starting shadow instance
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2 ETQ353 Starting system
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DE4", Nr="01", GwHost="MTW02SDEC01", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally
2EETQ399 Dialogue: ERROR
2EETQ399 Starting system failed, rc=0
DEVTRACE:
trc file: "dev_disp", trc level: 1, release: "700"
sysno      01
sid        DE4
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    111
intno      20050900
make:      multithreaded, ASCII, optimized
pid        2272
Mon Feb 18 16:08:40 2008
kernel runs with dp version 229(ext=109) (@(#) DPLIB-INT-VERSION-229)
length of sys_adm_ext is 364 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 2272) [dpxxdisp.c   1239]
     shared lib "dw_xml.dll" version 111 successfully loaded
     shared lib "dw_xtc.dll" version 111 successfully loaded
     shared lib "dw_stl.dll" version 111 successfully loaded
     shared lib "dw_gui.dll" version 111 successfully loaded
     shared lib "dw_mdm.dll" version 111 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
Mon Feb 18 16:08:52 2008
WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0065.qqq.nxst) took 12 seconds
Mon Feb 18 16:09:10 2008
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 18 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5361]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >MTW02SDEC01_DE4_01                      <
DpShMCreate: sizeof(wp_adm)          19976     (908)
DpShMCreate: sizeof(tm_adm)          3605136     (17936)
DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)          528048     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1296)
DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 065C0040, size: 4241064)
DpShMCreate: allocated sys_adm at 065C0040
DpShMCreate: allocated wp_adm at 065C1B30
DpShMCreate: allocated tm_adm_list at 065C6938
DpShMCreate: allocated tm_adm at 065C6968
DpShMCreate: allocated wp_ca_adm at 06936BF8
DpShMCreate: allocated appc_ca_adm at 0693B248
DpShMCreate: allocated comm_adm at 0693C9B8
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 069BD868
DpShMCreate: allocated gw_adm at 069BD8A8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 069BD8D8
DpShMCreate: allocated wall_adm at 069BD8E0
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 2046 blocks reserved for free list.
ES initialized.
WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   12437]
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( MTW02SDEC01) [dpxxdisp.c   11753]
DpStartStopMsg: send start message (myname is >MTW02SDEC01_DE4_01                      <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 111
Release check o.K.
Mon Feb 18 16:09:13 2008
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 4724] Mon Feb 18 16:08:40 2008
[Thr 4724] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    110
intno      20050900
make:      multithreaded, ASCII, optimized
pid        5420
[Thr 4724] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 5420) [msxxserv.c   1824]
[Thr 4724] MsInitAclInfo: acl file D:\usr\sap\put\DE4\SYS\global\ms_acl_info.DAT not found, unrestricted access
[Thr 4724] MsGetOwnIpAddr: my host addresses are :
[Thr 4724]   1 : [172.20.28.159] MTW02SDEC01.mindsap.com (HOSTNAME)
[Thr 4724]   2 : [127.0.0.1] MTW02SDEC01.mindsap.com (LOCALHOST)
[Thr 4724] MsHttpInit: full qualified hostname = MTW02SDEC01.mindsap.com
[Thr 4724] HTTP logging is switch off
[Thr 4724] MsHttpOwnDomain: own domain[1] = mindsap.com
[Thr 4724] ms/icf_info_server : deleted
[Thr 4724] *** I listen to port sapmsSHDDE4 (3601) ***
[Thr 4724] CUSTOMER KEY: >J1537289841<
trc file: "dev_rd", trc level: 1, release: "700"
Mon Feb 18 16:09:10 2008
***LOG S00=> GwInitReader, gateway started ( 2344) [gwxxrd.c     1694]
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    110
intno      20050900
make:      multithreaded, ASCII, optimized
pid        2344
gateway runs with dp version 229(ext=109) (@(#) DPLIB-INT-VERSION-229)
gw/local_addr : 0.0.0.0
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
Bind service sapgw01 (socket) to port 3301
GwPrintMyHostAddr: my host addresses are :
1 : [172.20.28.159] MTW02SDEC01.mindsap.com (HOSTNAME)
2 : [127.0.0.1] MTW02SDEC01.mindsap.com (LOCALHOST)
DpSysAdmExtCreate: ABAP is active
DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
DpShMCreate: sizeof(wp_adm)          19976     (908)
DpShMCreate: sizeof(tm_adm)          3605136     (17936)
DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)          528048     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1296)
DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 06110040, size: 4241064)
DpShMCreate: allocated sys_adm at 06110040
DpShMCreate: allocated wp_adm at 06111B30
DpShMCreate: allocated tm_adm_list at 06116938
DpShMCreate: allocated tm_adm at 06116968
DpShMCreate: allocated appc_ca_adm at 0648B248
DpShMCreate: allocated comm_adm at 0648C9B8
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0650D868
DpShMCreate: allocated gw_adm at 0650D8A8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0650D8D8
MtxInit: -2 0 0
Mon Feb 18 16:09:14 2008
GwDpInit: attached to gw_adm at 0650D8A8
Thanks,
Vadi

Dear All,
The issue has been resolved by changing the DDIC password to what it was when we have started the upgrade.The password was "welcome" when we have started with upgrade after that it has been changed to
"basis05" during upgrade.we changed it back to welcome and it started working fine.
Here it took long time to find out what was the password when we have starte upgrade.Resetting to standard ddic password also ddint help out in our case.
Thanks for all your replies.

Javascript errors after ecc upgrade

Hi,
At customer site an ECC 4.7 -> 6.0 upgrade has been performed. The BSPs from the old portal server are moved to the ECC6 backend system (ABAP stack installed only).
Now the BSPs are returning javascript errors when pressing buttons, tabstripitems etc. The error is 'object expected'. These BSPs are using htlmb tags. I made a simple test BSP with a click button and that one is also returning the javascript error.
When checking the generated code, I see a lot of javascript methods being called, but I dont see them declared.
Can anyone help me out?
With regards,
Mike

js definitions would be as a separate file in the mime repository.
couple of things to check
1. check in SICF whether sap/public/bc and sap/public/bsp nodes are active
2. invalidate the server cache from transaction SMICM->goto
and search for possible oss notes

Error in SAP Upgrade 4.6C to ECC 6.0 in CONFLICT_CHECK Phase

Hi All,
I am doing an SAP Upgrade frm SAP 4.6C SR2 to ECC 6.0 SR2. When it enters the CONFLICT_CHECK we are facing the following error. i am performing this on Production system. Your immediate help is highly appreciated.
#---- MASKING file CONFLCHK.LOG from E:\usr\sap\put\log
#---- TIME: 20091212095249
1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20091212094722")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '22', GwService = 'sapgw22'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
2 ETQ160 Starting conflict check
4 ETQ010 Date & Time: 20091212094722
4 ETQ230 Starting RFC Login to: System = "CPA", GwHost = "DERSHASKFI140", GwService = "sapgw22"
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
2EETQ360 RFC of "spda_conflict_check" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message         :
2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ                    .
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "SPDA_CONFLICT_CHECK" by RFC failed (error-status "-2")
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20091212094903
4 ETQ010 Date & Time: 20091212094903
Hemanth

Hi,
> 2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ
Have you checked tablespace have sufficient space ?
Thanks
Sunny        .

Error during upgrade phase JOB_RSUPGCUA_SHD

Hi Everyone,
We are in the process of completing a combined ERP 6.0 Upgrade / Unicode Conversion. Our starting release is ECC 5.0 (ABAP only) and we are running Oracle 10.2.0.2 on AIX 5.3.
We are receiving the following error in phase JOB_RSUPGCUA_SHD:
1 ETQ201XEntering upgrade-phase "JOB_RSUPGCUA_SHD" ("20080812163717")
2 ETQ366 Connect variables are set for shadow instance access
4 ETQ399 System-nr = '56', GwService = 'sapgw56'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPR3
4 ETQ399 auth_shadow_upgrade=1
4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
4 ETQ010 Date & Time: 20080812163717
4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
4 ETQ230 Starting RFC Login to: System = "ENP", GwHost = "aix12j1", GwService = "sapgw56"
4 ETQ359 RFC Login to: System="ENP", Nr="56", GwHost="aix12j1", GwService="sapgw56"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
2EETQ235 Call of function module "SUBST_START_BATCHJOB" by RFC failed (error-status "10")
2EETQ261 Start of batchjob "RSUPGCUAGEN111" failed
1EETQ203 Upgrade phase "JOB_RSUPGCUA_SHD" aborted with errors ("20080812163717")
We originally had some issues with the shadow system not starting in phase START_SHDI_FIRST. The source of the problem was the value of paramter ipc/shm_psize_40 in the instance profile of the shadow system. When we ran "sappfpar check" on the profile, the output indicated that the paramter was too small. We backed up the profile, increased the parameter to the value "sappfpar check" recommended and then stopped the shadow system via "SAPup stopshd." We then repeated the phase. The shadow instance was started successfully and the upgrade proceeded with subsequent phases.
We encountered the error above several phases later. The shadow instance is started and I am able to login with user DDIC. As detailed in the error message above, function module SUBST_START_BATCHJOB is aborting with error code 10. Based on what I can interpret from source code of the function module, this seems to indicate that there is a problem with the program values. The SM21 log indicates that "Program name RSUPGCUAGEN111 is invalid."
What do we need to do to get past this error?
Thanks in advance for any assistance,
Tommye

for our case it was that the shadow instance was not completely stsarted, some processes were down, cause the ipc pool 40 was too small, i found the error in the killed work processes.
Probleme resolved as susch. i hope it will help someone.
Regards

SEVERE ERROR in Upgrade Phase ADDON_SPEC2

I`m trying to upgrade R/3 Release 4.6C to SAP ECC 6.0 SR3 (7.0) Abap:
Unix - Oracle.
I found no errors in log files.
I have successfully completed all the PREPARE PHASES.
Source System:
SAP release: R/3 Release 4.6C
DB version: 10.2.0.2
S.O. version: HP-UX B.11.23 U ia64
Kernel: 46D_Ext
Target System:
SAP release: ECC 6.0 R/3 (7.0)
DB version: 10.2.0.2
S.O. version: HP-UX B.11.23 U ia64
Please help,
Regards,
Erick

more SAPup.log
UPGRADEPHASE ADDON_SPEC2
...started at 20090219124818
Phase log file: 'ADDONSPEC2.LOG'
..finished at 20090219124818 with SEVERE ERROR(S).
...begin dialogue at 20090219124818
...end dialogue at 20090219135001
..answered at 20090219135001.
-> decided to exit.
more ADDONSPEC2.SAV
#---- MASKING file ADDONSPEC2.LOG from /usr/sap/put/log
#---- TIME: 20090219124818
1 ETQ201XEntering upgrade-phase "ADDON_SPEC2" ("20090218183020")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSP1
4 ETQ399   auth_shadow_upgrade=0
ADDONSPEC2.SAV: END
more ADDONSPEC2.LOG
1 ETQ201XEntering upgrade-phase "ADDON_SPEC2" ("20090219124818")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSP1
4 ETQ399   auth_shadow_upgrade=0
Some idea,
Erick

Upgrade-phase "SYIDUP_EXTRACT/PROFREAD" error

We are upgrading SCC system.
While generating stack.xml file from solman 7.1 sp 10, we got error in the verification execution as Cannot recognize installed product instance in lmdb.
We referred the note - 1816146 - Correction of installed software information (CISI.
1. We run the report RLMDB_DOWNLOAD_INST_SOFT_INFO and created .xml file.
2. downloaded SUM sp10
While running SUM tools we got the error the phase "SYIDUP_EXTRACT/PROFREAD" as below.
Attaching files as -
1. All log file from directory 'S:\usr\sap\SCC\SUM\abap\log'
2. All profiles
We analyzed the issue. Error is coming the file PROFREAD.LOG as
1 ETQ201 Entering upgrade-phase "SYIDUP_EXTRACT/PROFREAD" ("20140409192228")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '', GwService = 'sapgw' Client = '000'
4 ETQ399 Environment variables:
4 ETQ399 auth_shadow_upgrade=<null>
1 ETQ200 Executing actual phase 'SYIDUP_EXTRACT/PROFREAD'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DDICPWD_ONLY'
4 ETQ399 Starting dialog 'Passwords' at 20140409192229.
1 ETQ359 RFC Login to: System="SCC", AsHost="dl5802" Nr="", GwHost="dl5802", GwService="sapgw"
2EETQ231 RFC Login failed
4EETQ399 Dialogue validator 'DDICValidator' failed with 'DDIC password does not work:
RFC login to system SCC ashost dl5802 nr gwhost dl5802 gwservice sapgw failed with code 1 key RFC_COMMUNICATION_FAILURE:
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR      partner 'dl5802:3300' not reached
TIME        Wed Apr 09 19:22:37 2014
RELEASE    721
COMPONENT NI (network interface)
VERSION    40
RC          -10
MODULE      nixxi.cpp
LINE        3285
DETAIL      NiPConnect2: 172.17.206.26:3300
SYSTEM CALL connect
ERRNO      10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER    1
4 ETQ399 Repeat dialog since input validation failed.
Please check the same and revert backup.
Thanks,
Kundan Gandhi
9930446697

Hi all,
Please check 4 ETQ399 System-nr = '', GwService = 'sapgw' Client = '000' in the log mentioned.
Why it is not picking up any value for System-nr = (It should get system no. 40 - as my system no is 40)
Please revert, if any body faced this type of issue.
Thanks,
Kundan Gandhi

Upgrade-phase "CONFLICT_CHECK" fails with error

Please help, I am trying to run the prepare for our BW 3.5 to BI 7.0 (SR2) upgrade and am running into an error in the CONFLICT_CHECK phase:
Conflict check failed, rc = "-2", reason = "Internal error: OCS_COLLECT_ADDON_TASKS: MISSING_CMD_IMPORT SAPK
INBC9D"
When i ran this in our beta and dev environment I wasn't updating as many support packs and plug in's; and I did not run into this error. Here are the addon's I am updating
Addon       current version           upgraded version       how I am updating
PI_BASIS     2005_1_640     2006_1_700     UPG With ADDON CD
BI_CONT     353                     703                     UPG WITH SAINT PACK
ST-A/PI     01F_BCO640     -                     DELETE
ST-PI     2005_1_640     2005_1_700     UPG WITH SAINT PACK
Here is the output file:
more CONFLCHK.LOG
1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20071011155952")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '30', GwService = 'sapgw30'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPBWS
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
2 ETQ160 Starting conflict check
4 ETQ010 Date & Time: 20071011155952
4 ETQ230 Starting RFC Login to: System = "BWS", GwHost = "sapbws", GwService = "sapgw30"
4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
2 ETQ161 Conflict check failed, rc = "-2", reason = "Internal error: OCS_COLLECT_ADDON_TASKS: MISSING_CMD_IMPORT SAPK
INBC9D"
4 ETQ010 Date & Time: 20071011155952
As you can see it is looking for SAPKINBC9D. This is not an addon package I selected. The PI_BASIS uses SAPKINBC9A. I checked SEPS (EPS admin) and do not see this. I also tried to search for this file on service.sap.com and do not see it. I have no idea what could be causing this. Please help!
Erika

Hello,
If I remember correctly it was the version of PI_BASIS. I ended up upgrading the following addon's during the upgrade follows:
PI_BASIS     2005_1_640     2005_1_700     Inst/UPG with STD CD
BI_CONT     353     703     UPG WITH SAINT PACK
ST-A/PI     01F_BCO640     -     DELETE
ST-PI     2005_1_640     2005_1_700     UPG WITH SAINT PACK
After the upgrade, I applied the PI_BASIS upgrade and support packs.

4.0B to ECC 6.0; SPDD in PREPARE or UPGRADE phase?

Hi Gurus,
I am working on an upgrade from R/3 4.0 to ECC 6.0. I worked on pgrades before but am alien 4.0B. BTW, from a Developer perspective:
1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
Helpful Answers will be rewarded

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

Error in PREP_INIT/VERSCHK_INI phase during upgrade to NW70 EHP1 SR1

Hi All,
We have a NW system with the following components to NW 70 EHP1 SR1:
SAP_ABA     700     0013     SAPKA70013     Cross-Application Component
SAP_BASIS     700     0013     SAPKB70013     SAP Basis Component
PI_BASIS     2005_1_700     0013     SAPKIPYJ7D     PI_BASIS 2005_1_700
ST-PI     2005_1_700     0000          -     SAP Solution Tools Plug-In
SAP_BW     700     0015     SAPKW70015     SAP NetWeaver BI 7.0
BI_CONT     703     0000          -     Business Intelligence Content
We are in the process of upgrade to SAP EHP1 FOR SAP NETWEAVER 7.0 SR1 and we got the below error during the upgrade:
Checks after phase PREP_INIT/VERSCHK_INI were negative!
Last error code set: Start Release configuration 'SAP_ABA=700,SAP_BASIS=700,SAP_BW=700' is not supported Compare the release of your SAP system with the requirements listed in the documentation.
Choose action
     Repeat phase VERSCHK_INI to continue at the point it stopped
     Cancel the current phase VERSCHK_INI and go back to wizard
     Exit this program
We verified the DVDs (media list) we are uing for the upgarde and it is correct.
Any ideas on how this can be resolved?
Regards
ND

Have you read this note: https://service.sap.com/sap/support/notes/1568031
Looks like you have to include the latest corrections for EHPI installer.
Thanks
Srikanth Mandalapu
Cert Basis/Netweaver

Errors in DDIC Activation phase during upgrade.

Hi,
Title: Errors in DDIC Activation phase during upgrade.
During preprocessing phase (phase ACT_UPG) we got many DDIC activation errors such as:
SAPup broke during phase ACT_UPG in module MAIN_SHDRUN / Shadow System Operations: SPDD and Activation.
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCI702.CPE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EEDO519 "Data Element" "/BI0/OICH_AT" could not be activated
1EEDO519 "Data Element" "/BI0/OICREA_TIME" could not be activated
1 ETP111 exit code           : "8"
We have searched the SDN, many posts say that we have to just activate them. But my question is where - in source system OR in Shadow system?
We assumed it is Source system (please correct if it is wrong), unlocked the system and logged in as normal user and tried to activate the Data Element. Now, it says "Search Help /BI0/OICH_AT is not active or contains no parameter".   How to go about it?
If it is Shadow System, how can i unlock the system?
Many thanks,
Mohan.

Dear Mohan,
There are search helps configured for the dataelements in ACTUPG.ELG. These search helps were created by mistake by the system.
The search helps can be deleted manually in the shadow instance.
In this case you should remove these fields in se11 (in your shadow instance) as the Search help shouldn't exist.
You should do this step for all data elements shown in the log ACTUPG.ELG:
For example: SE11 -> /BI0/OICH_AT -> Change -> Tab "Further characteristics"
1. Goto SE11:
2. Select Data type and fill "/BI0/OICH_AT" and display
3. Select the tab "Further Characteristics" and
4. Remove the values for fields "Name" and "Parameters"
   then click on icon "Activate"
Please do the same for the other object.
But before performing above steps you need to unlock the shadow instance by the following command:
SAPup unlockshd <SID>
(if using SAPup)
SAPehpi unlockshd <SID>
(if using SAPehpi)
Also do not forget to lock the shadow system again after performing the steps and continuing the upgrade by the following command:
SAPup lockshd <SID>
(if using SAPup)
SAPehpi lockshd <SID>
(if using SAPehpi)
You can logon to your shadow system with any different user than DDIC.
Best Regards,
Abhishek
Edited by: Abhishek Srivastava on Oct 17, 2011 6:26 PM

ECC 6.0 Enhancement Pack 5 upgrade phase ADJUSTCHK faillure

When I run the Enhancement Pack Installation, I get a hard failure at the MAIN_SHDCRE/ADJUSTCHK phase. The error message says "No lines found in logfile matching "UMODPRO\.INX". The log follows...
1 ETQ201 Entering upgrade-phase "ADJUSTCHK" ("20111006131443")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPR3
4 ETQ399 auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_SHDCRE/ADJUSTCHK'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'SAP_MOD_EHP'
2 ETQ399 Arg[1] = 'ADJUSTCK.ELG'
2 ETQ399 Arg[2] = 'ADJUSTMT.INF'
4 ETQ010 Date & Time: 20111006131443
4 ETQ265 Starting report "RSUMOD01" with variant "SAP_MOD_EHP" in batch
4 ETQ359 RFC Login to: System="INX", Nr="00", GwHost="fainx", GwService="sapgw00
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
4 ETQ234 Call of function module "SUBST_START_REPORT_IN_BATCH" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ311 Batch job "RSUMOD01" with job count "13144400" scheduled
4 ETQ359 RFC Login to: System="INX", Nr="00", GwHost="fainx", GwService="sapgw00
4 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20111006131819
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
1EETQ248 Missing log file(s) of report "RSUMOD01", matching "UMODPROT\.INX"
What does this mean?
Is the backslash supposed to be in the name UMODPROT.INX?

Hi,
Please check in SM37 if there is any job failure in the system. And also check if there is any dump.
Thanks
Sunny

EHP1 upgrade error in PREP_INPUT..phase

Hello,
I am doing EHP1 upgrade and getting error in EHPI during the PREP_INPUT/KX_CPYORG! phase.
Below is the error:
Severe error(s) occured in phase PREP_INPUT/KX_CPYORG!
Last error code set: Cannot open '/usr/sap/<SID>/SYS/exe/run/dbatoolsora.lst': No such file or directory
It complains about dabtoolsora.lst file not existing in /SYS/exe/run Dir. This is because our DB is in separate machine/host and the CI is in separate. Hence the file mentioned above only exist in */SYS/exe/run Dir of DB host.
Can anyone please suggest what steps should be taken to resolve this issue? Do i need to copy that file manually to the CI host's */SYS/exe/run Directory and then repeat the EHPI steps again?
Any help would be greatly appreciated. Thanks.

I know this answer is too late for your question, but it's still the top google hit for this message, so I'm leaving this here for others.
SUM still has this behavior as of 1.0 SP6. One workaround is to copy dbatoolsora.lst from your DB server kernel directory, and create wrapper scripts which will SSH from the CI to the DB and run the brtools commands that SUM would want to run.
Here's an example of such a script, for brtools:
#!/bin/csh
ssh $SAPDBHOST brtools $*
So, you'd have a script like this for brarchive, brbackup, and the other br* tools mentioned in dbatoolsora.lst, each containing the name of the command to run on the db server.
Be sure to look in dbatoolsora.lst for a list of other files it may expect to find.

Upgrade phase "SQLSCREXE_ALI_ORG" aborted with errors

Hi ,
Need some assistance. Logged message with SAP AG, still waiting for response.Anyone that can assist will be appreciated. Error from logs.
/usr/sap/put/log# more SEDCORG.LOG
1 ETQ201XEntering upgrade-phase "SQLSCREXE_ALI_ORG" ("20061108125644")
2 ETQ366 Connect variables are set for shadow instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=1
4 ETQ380 computing toolpath for request "TP_EXECDBSCRIPT_NEW"
4 ETQ381 request "TP_EXECDBSCRIPT_NEW" means "execdbscript with 46A feature"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ276 Executing SQL-script "ALORDC.XQL"
4 ETQ399 ext. env.: DIR_LIBRARY=/usr/sap/put/exe
4 ETQ399 ext. env.: LIBPATH=/usr/sap/put/exe:/usr/sap/BB1/sapjco:/usr/lib:/lib:/usr/sap/BB1/SYS/exe/run:/usr/java131
/jre/bin:/usr/java131/jre/bin/classic
4 ETQ399 2006/11/08 12:56:44: put_execute: (tp) forkpid:97258
2EETQ278 Errors during execution of SQL-script "ALORDC.XQL"
1EETQ203 Upgrade phase "SQLSCREXE_ALI_ORG" aborted with errors ("20061108125645")
Checked TPSQLSTD.OUT log
/usr/sap/put/log# more TPSQLSTD.OUT
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 97258 at 20061108125644
ENV <0x2ff22d14>: dbms_type=ORA
ENV <0x2ff22d22>: dbs_ora_tnsname=BB1
ENV <0x2011c290>: dbs_ora_schema=SAPR3
ENV <0x2ff22d4b>: ORACLE_PSRV=BB1
ENV <0x2ff22d5b>: ORACLE_SID=BB1
ENV <0x2ff22d75>: ORACLE_HOME=/oracle/BB1/102_64
ENV <0x2ff22d94>: ORACLE_BASE=/oracle
ENV <0x2ff22da8>: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV <0x2ff22ddf>: NLS_LANG=AMERICAN_AMERICA.US7ASCII
ENV <0x20147368>: DIR_LIBRARY=/usr/sap/put/exe
ENV <0x2014864c>: LIBPATH=/usr/sap/put/exe:/usr/sap/BB1/sapjco:/usr/lib:/lib:/usr/sap/BB1/SYS/exe/run:/usr/java131/j
re/bin:/usr/java131/jre/bin/classic
ENV <0x2011be90>: auth_shadow_upgrade=1
EXECUTING /usr/sap/put/exe/tp (tp) pf=/usr/sap/put/bin/EXDBNEW.TPP execdbscript BB1 -x ALORDC.XQL
This is /usr/sap/put/exe/tp version 370.00.09 (release 700)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBNAME is no longer used.
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
2EETP000 sap_dext called with msgnr "2":
2EETP000 -
db call info -
2EETP000 function:   db_ntab
2EETP000 fcode:      NT_RDTDESCR
2EETP000 tabname:    TADIR
2EETP000 len:        5
2EETP000 key:        TADIR
2EETP000 retcode:    2
1AETP000 exit in function texitnow
ERROR: EXIT(16) -> process ID is: 97258
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
ERRORS: Highest tp internal error was: 0200
tp finished with return code: 200
meaning:
ERROR: see tp's stdout (Standard Out may not be available)
Process with ID 97258 terminated with status 200
History : Original problem was related to environment variables for DIR_LIBRARY. Resolved that issue; UaGui was started as root and not the <sid>adm user. UaServer was started as correct user. Killed session and logged on as <sid>adm restarted UaGui as the correct user. Now this error comes up, SAPup won't allow me continue or retry
Replaced tp, r3trans and SAPup tools. Also when I run the cmd /usr/sap/put/exe/tp (tp) pf=/usr/sap/put/bin/EXDBNEW.TPP execdbscript BB1 -x ALORDC.XQL in a seperate session, it completes successfully and creates the necessary views as described in ALORDC.XQL. I checked the ALORDC.LOG to confirm this.
Kind Regards,
Ricky Padayachee

Hi John,
The problem I had was wrong environment when starting the Uagui and Uaserver, must be started as adm user. I also restarted the installation from scratch...
I had an issue with a duplicate database object, SVERS in my case. I dropped the object not required and restarted phase, went through fine.
Let me know, how it goes.
Regards,
Ricky

Error in the DEPLOY_ONLINE_DEPL phase in Downtime on Dualstack upgrade

Hi Gurus,
again i got struck with another error in the pahse DEPLOY_ONLINE_DEPL of Downtime.
An error has occurred during the execution of the DEPLOY_ONLINE_DEPL phase.
Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. Could not execute deployment of stack file G:/EHP5DUAL/SMSDXML_IJE_20110925114634.078.xml. The deployment of the queue failed. Deployment of queue sapjup-queue completed with error JSPM version is 7.02.8.0.3. Current JSPM log directory is D:\usr\sap\IJE\DVEBMGS01\j2ee\JSPM\log\log_2011_12_07_19_15_55. sap.com/CAF: Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1': Failed deployment of SDAs: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted Please, look at error logs above for more information! Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/LM-TOOLS: Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/ETPRJSCHEDULER: Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/EPBC2: Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/EP-PSERV: Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/SWLIFECYCL: Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/UWLJWF: Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. sap.com/SAP-EU: Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0': No further description found. Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details. The following SAP Note 1399846 may contain solution for the problem.
You can find more information in the log file G:\EHP5_Down\EHPI\java\log\DEPLOY_ONLINE_DEPL_DDB_02.LOG.
Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager com.sap.sdt.ucp.phases.PhaseException Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action. DEPLOY_ONLINE_DEPL DEPLOYMENT_BASED_UPGRADE NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
When reporting problems to SAP Support, attach the trouble ticket file G:\EHP5_Down\EHPI\java\log\TroubleTicket_37.txt to your message.
JSPM log:
sap.com/SAP_JTECHS: DEPLOYED
sap.com/BI_UDI: DEPLOYED
sap.com/CAF: ERROR
Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted
Please, look at error logs above for more information!
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/LM-TOOLS: ERROR
Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/UMEADMIN: NOT DEPLOYED
Archive G:\EHP5DUAL\UMEADMIN08_0-10006669.SCA has been admitted for deployment but deployment did not start. ready for update (but not updated yet)
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/NET-PDK: DEPLOYED
sap.com/ETPRJSCHEDULER: ERROR
Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/EPBC2: ERROR
Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/EP-PSERV: ERROR
Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/EP-WDC: NOT DEPLOYED
Archive G:\EHP5DUAL\EPWDC08_0-10006502.SCA has been admitted for deployment but deployment did not start. ready for update (but not updated yet)
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/SWLIFECYCL: ERROR
Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/UWLJWF: ERROR
Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
sap.com/SAP-EU: ERROR
Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0':
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/CAF: Deployment of archive G:\EHP5DUAL\CAF08_0-10006486.SCA has been terminated. Aborted: software component CAF/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519132845'/1:
Failed deployment of SDAs:
development component caf/UI/ptn/common/sap.com/MAIN_NW702P03_C/3520877/1 : aborted
Please, look at error logs above for more information!
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/LM-TOOLS: Deployment of archive G:\EHP5DUAL\LMTOOLS08_0-10006642.SCA has been terminated. Aborted: software component LM-TOOLS/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519133035'/1:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/ETPRJSCHEDULER: Deployment of archive G:\EHP5DUAL\ETPRJSCHEDULER08_0-10007220.SCA has been terminated. Aborted: software component ETPRJSCHEDULER/sap.com/SAP AG/1000.7.02.8.0.20110519133428'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/EPBC2: Deployment of archive G:\EHP5DUAL\EPBC208_0-10006500.SCA has been terminated. Aborted: software component EPBC2/sap.com/SAP AG/1000.7.02.8.0.20110519131841'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/EP-PSERV: Deployment of archive G:\EHP5DUAL\EPPSERV08_0-10006501.SCA has been terminated. Aborted: software component EP-PSERV/sap.com/SAP AG/1000.7.02.8.0.20110614172722'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/SWLIFECYCL: Deployment of archive G:\EHP5DUAL\SWLIFECYCL08_0-10006668.SCA has been terminated. Aborted: software component SWLIFECYCL/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519133223'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/UWLJWF: Deployment of archive G:\EHP5DUAL\UWLJWF08_0-10006670.SCA has been terminated. Aborted: software component UWLJWF/sap.com/SAP AG/1000.7.02.8.0.20110519132125'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: sap.com/SAP-EU: Deployment of archive G:\EHP5DUAL\SAPEU08_0-10006663.SCA has been terminated. Aborted: software component SAP-EU/sap.com/MAIN_NW702P08_C/1000.7.02.8.0.20110519132114'/0:
No further description found.
Error during deployment. See D:/usr/sap/IJE/DVEBMGS01/SDM/program/log/sdmcl20111207153503.log for details.
Dec 7, 2011 9:24:48 PM [Error]: Deployment of queue sapjup-queue completed with error
JSPM version is 7.02.8.0.3. Current JSPM log directory is D:\usr\sap\IJE\DVEBMGS01\j2ee\JSPM\log\log_2011_12_07_19_15_55.
Thanks in advance
Venkat

Hi Siva,
Log file:sdmcl20111207153503.log
2011 9:18:11 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 7, 2011 9:18:11 PM   Info: Starting cluster instance processes.
Dec 7, 2011 9:18:11 PM   Info: Starting the instance JC_admin0001_IJE_01 running on host admin0001
Dec 7, 2011 9:18:24 PM   Info: Starting the instance JC_admin0001_IJE_01 processes. The instance is running on host admin0001
Dec 7, 2011 9:18:24 PM   Info: Starting the process dispatcher
Dec 7, 2011 9:18:24 PM   Info: Starting the process server0
Dec 7, 2011 9:22:17 PM   Info: Cluster instance processes have been successfully started.
Dec 7, 2011 9:22:19 PM   Info: Begin of log messages of the target system:
11/12/07 21:18:11 - ***********************************************************
11/12/07 21:22:17 - Start updating EAR file...
11/12/07 21:22:17 - start-up mode is lazy
11/12/07 21:22:17 - EAR file updated successfully for 203ms.
11/12/07 21:22:17 - Start updating...
11/12/07 21:22:18 - EAR file uploaded to server for 485ms.
11/12/07 21:22:19 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
                     Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. 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/cafUIptn~common. 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.update(DeployServiceImpl.java:689)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                          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:104)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                     Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. 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:1052)
                          at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1283)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:402)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:325)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:166)
                          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:3241)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:677)
                          ... 10 more
                     For detailed information see the log file of the Deploy Service.
11/12/07 21:22:19 - ***********************************************************
Dec 7, 2011 9:22:19 PM   Info: End of log messages of the target system.
Dec 7, 2011 9:22:19 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 7, 2011 9:22:19 PM   Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1', grouped by software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. 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/cafUIptn~common. 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)
Dec 7, 2011 9:22:19 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:20 PM   Info: Finished saving the repository for 563 ms.
Dec 7, 2011 9:22:20 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 7, 2011 9:22:20 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132845''/'1':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_NW702P03_C'/'3520877'/'1' : aborted
Please, look at error logs above for more information!
Dec 7, 2011 9:22:20 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:21 PM   Info: Finished saving the repository for 750 ms.
Dec 7, 2011 9:22:21 PM   Info: Starting: Update: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0' updates currently deployed software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.6.1.20060305015600''/'0'.
Dec 7, 2011 9:22:21 PM   Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110614172722''/'0':
No further description found.
Dec 7, 2011 9:22:21 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:21 PM   Info: Finished saving the repository for 735 ms.
Dec 7, 2011 9:22:21 PM   Info: Starting: Update: Selected software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0' updates currently deployed software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.6.0.20060305011500''/'0'.
Dec 7, 2011 9:22:21 PM   Error: Aborted: software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519131841''/'0':
No further description found.
Dec 7, 2011 9:22:21 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:22 PM   Info: Finished saving the repository for 922 ms.
Dec 7, 2011 9:22:22 PM   Info: Starting: Initial deployment: Selected software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0' will be deployed.
Dec 7, 2011 9:22:22 PM   Error: Aborted: software component 'ETPRJSCHEDULER'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519133428''/'0':
No further description found.
Dec 7, 2011 9:22:22 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:23 PM   Info: Finished saving the repository for 531 ms.
Dec 7, 2011 9:22:23 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 7, 2011 9:22:23 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133035''/'1':
No further description found.
Dec 7, 2011 9:22:23 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:24 PM   Info: Finished saving the repository for 750 ms.
Dec 7, 2011 9:22:24 PM   Info: Starting: Initial deployment: Selected software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0' will be deployed.
Dec 7, 2011 9:22:24 PM   Error: Aborted: software component 'SWLIFECYCL'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519133223''/'0':
No further description found.
Dec 7, 2011 9:22:24 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:24 PM   Info: Finished saving the repository for 547 ms.
Dec 7, 2011 9:22:24 PM   Info: Starting: Update: Selected software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0' updates currently deployed software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.00.6.0.20060305024800''/'0'.
Dec 7, 2011 9:22:24 PM   Error: Aborted: software component 'UWLJWF'/'sap.com'/'SAP AG'/'1000.7.02.8.0.20110519132125''/'0':
No further description found.
Dec 7, 2011 9:22:24 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:25 PM   Info: Finished saving the repository for 531 ms.
Dec 7, 2011 9:22:25 PM   Info: Starting: Update: Selected software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0' updates currently deployed software component 'SAP-EU'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.4.20060301135451''/'0'.
Dec 7, 2011 9:22:25 PM   Error: Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_NW702P08_C'/'1000.7.02.8.0.20110519132114''/'0':
No further description found.
Dec 7, 2011 9:22:25 PM   Info: Starting to save the repository
Dec 7, 2011 9:22:25 PM   Info: Finished saving the repository for 578 ms.
Dec 7, 2011 9:22:25 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 7, 2011 9:22:25 PM   Error: -
At least one of the Deployments failed -
Thanks,
Venkat

Error in ecc upgrade phase

Similar Messages

Maybe you are looking for