Upgradation phase GETSYNC_PREUP_FINI_R1

Hi,
we are upgrading sap from ECC5 to ECC6.but at the phase GETSYNC_PREUP_FINI_R1 it got stuck.
any body plz give me the solution.
this is little urgent.
Rajender.J

Hi ,
There is BUG in EHPI 700 tool, if you disabled java before starting,but still phase GETSYNC_PREUP_FINI_D running or sync with Java
SAP Reply=======================
Thank you for the update.
I have got this from my next level of support.
It seems the parameter "javadisabled=true" is not properly working for
SAPehpi 700 release lmt_001, as a workaround you should move the j2ee
directory from /usr/sap/<sid>/DVEBMGS* and reset the EHP installation
re-starting from the scratch (one more time). Sorry for it!!!
Thanks.
Warm Regards,
Sriram
AGS Primary Support, Business Suite & Technology

Similar Messages

  • 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

  • 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.

  • 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

  • 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

  • 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.

  • Reg: Upgrade Phase RUN_UACC_POST

    Hi All,
    We are in process of upgrade fro 4.7SR1 to ECC6.0 SR3 ( O/S Sun Solaries & Database is Oracle)
    Right now we are facing issue in the Phase RUN_UACC_POST. The Log file shows
    geupg:updadm 12% more UACCUPG.LOG
    1 ETQ201XEntering upgrade-phase "RUN_UACC_POST" ("20081214225715")
    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=SAPUPD
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ010 Date & Time: 20081214225715
    4 ETQ265 Starting report "UACC_UPG_STEPS" with variant "SAP_UPG_POST" in batch
    4 ETQ359 RFC Login to: System="UPD", Nr="00", GwHost="geupg", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
    2WETQ360 RFC of "subst_start_report_in_batch" failed:
    2WETQ361 code/exception  : BATCH_SCHEDULING_FAILED
    4 ETQ359 RFC Login to: System="UPD", Nr="00", GwHost="geupg", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    2EETQ261 Start of batchjob "UACC_UPG_STEPS" failed
    2EETG890 Exception "BATCH_SCHEDULING_FAILED" raised, job scheduling failed with error code -1
    1EETQ204 Upgrade phase "RUN_UACC_POST" aborted with severe errors ("20081214225717")
    Please check and update the solution.
    Regards,
    Venu

    Hi All,
    The issues has been resolved by applying Support Pack ST-PT 2005_1_700 (SAPKITLQI6)
    Regards,
    Venu

  • 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

  • ECC6 upgrade phase XPRAS_UPG running for long time

    Hi,
    I am performing a Downtime minimized upgrade (MODPROF_TRANS) from R34.7ext2 to ECC6.0 / Windows2003/MSSQL2005
    Currently i am in the phase XPRAS_UPG .It is running for really long time.I tried to reset the phase but still went on for more than 10 hrs. I initialized the phase now its running for more than 7 hours. There are no processes when i check in SM50 and no log files updated. There is no log file called XPRAS_UPG.ELG.SM37 no jobs running.
    Though if it takes long time , How do i confirm that my upgrade phase is running ??????????as its not updating anything
    In PARDIST_SHD phase when there was en error , i have manuall deleted the DB trigger acording to the note 956198. And the phase went on.
    Now after reading few messages reg this error , i checked DB02 but no locks on any table . Have cheked note 558197,1292069,1142410,1138351,1062559,597885,551298. But nothings applicable in my case.
    Please suggest ...
    will really appreciate your help.
    Chandra

    Dear Chandra,
    Regarding long runtime for XPRAS phase kindly note the following:
    1. The reason of slow performance of XPRAS phase can vary differently.
    Basically during XPRAS phase, there're a lot of reports to run. These
    reports are inlcuded in the transport requests(both upgrade
    requests and support packages). If there's a performance problem,
    it very likely the database performance problem, such as wrong
    access plan was chosen, or missing index, etc.
    2. To find out the performance problems in the XPRAS, you can always
    logon into the system. During the XPRAS phase, the system has to be up and running.
    In SM50, usually you can find which report is running, and/or which table is being accessed.
    If you find some table accesses take unusually long time, please
    record the table name and find the SQL statement. Sometimes a simple
    index can solve the problem, sometimes you need help from Oracle
    to get the solution.
    3. If you want to shorten the downtime, you can select less support
    packages since all SPs have a lot of reports to run in XPRAS. But
    remember you need to import them soon or later. But if you prefer
    import them later it's fine.
    Currently if you check in SM37 then you can see RDDEXECL job in active status.
    Check for the job log, if there are any errors reported?
    Thereafter check the SM50 and see if its taking unusually long time for some particular table.
    If so then it might be because you might have not updated the statistics for that particular table.
    Also check what was the parameter value of Number of batch processes defined by you
    for upgrade. If you have defined very less number of batch processes for upgrade then also
    it will take more time.
    Check accordingly and let me know for further help.
    Regards,
    Abhishek
    Edited by: Abhishek Srivastava on May 9, 2010 10:57 AM

  • 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

  • Different tp r3trans versions in kernel upgrade phase

    Hi,
    we're actually in an kernel upgrade phase (R/3 6.40 from 175 to 196). The new kernel version will be deployed first on DEV system, and after evaluation/troubleshooting the PRD will be done. The tp and r3trans programs are also upgraded.
    My question is the following : is it possible to do transports from DEV to PRD when you're working with different tp and r3trans versions (during the upgrade phase) ?
    Kind regards,
    Erik

    Hi Erik,
    There is no problem if you transport,we have recently changed the tp and r3trans in our DEV and have done many transport everthing worked fine,no problems.You can proceed.
    Make sure you back up the sys/exe directory.
    Reward points if helpfull.
    Regards,
    Vamshi.

  • 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 "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

  • Upgrade phase STARTSAP_NBAS error: SYSTEM START failed

    During an upgrade from BW 3.5 to BI 7.0, I get the following error
    message in phase STARTSAP_NBAS:
    SYSTEM START failed, code -2
    -2: the test rfc did not work.
    Try to log on to the system with user DDIC
    When I try to log on to the system as user DDIC, I get the following
    error message:
    DB-Error -0
    The same thing happens when I try to log on as SAP*. I am certain that
    the password I submit is correct. I have not changed this password at
    any time.
    I have included SAP_BASIS support package 14 into this upgrade, and
    this requires kernel version 133 at least (Note 822379). This kernel
    was copied into the usr\sap\put\exenew directory before the upgrade
    began. However, the system still seems to run on kernel version 111.
    I have tried to put the 133 kernel into
    F:\usr\sap\BWS\SYS\exe\nuc\NTAMD64 so that it is copied into
    F:\usr\sap\BWS\SYS\exe\run during system startup, but then all my work
    processes die. The gateway also seems to be down using this kernel.
    Please help!
    Regards,
    Thomas

    Hi.
    I made a stupid mistake.. the kernel I was using was unicode, but I should use a non-unicode kernel..
    Regards,
    Thomas

  • Problem in CRM upgrade - phase MAIN_NEWBAS/JOB_RSINDCHK

    Hello,
    Iu00B4m in the middle of a CRM migration from 4.0 to 7.0. In phase MAIN_NEWBAS/JOB_RSINDCHK I get the error RFC_ERROR 2: DUMP_ERROR.
    I know I can solve the problem applying note 1483283 but have a problem in the process.
    First I unlock de system with commands...
    tp unlocksys SAPSID pf=(DIR_UPG)/bin/DEFAULT.TPP
    tp unlock_EU SAPSID pf=(DIR_UPG)/bin/DEFAULT.TPP
    ...then I can login in the system but when try to access transaction SE24 or any other I get a dump
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_ENH_INTERNAL_ERROR
    Date and Time          29.12.2010 09:39:19
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_ENH_INTERNAL_ERROR' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program
          'CL_R3STANDARD_PERSISTENCE=====CP' has to be
         terminated.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_ENH_INTERNAL_ERROR', was not
          caught in
         procedure "SFW_GET_SWITCHPOS" "(FUNCTION)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         No text available for this exception
    Missing RAISING Clause in Interface
        Program                                 SAPLSFW_COMMON
        Include                                 LSFW_COMMONU01
        Row                                     1
        Module type                             (FUNCTION)
        Module Name                             SFW_GET_SWITCHPOS
    Trigger Location of Exception
        Program                                 CL_R3STANDARD_PERSISTENCE=====CP
        Include                                 CL_R3STANDARD_PERSISTENCE=====CM00Z
        Row                                     46
        Module type                             (METHOD)
        Module Name                             LOAD_SPOT
    Any idea about that?
    When I execute tp commands I get this message
    G:\usr\sap\CRQ\upg\abap\exe>tp unlocksys CRQ pf=G:\usr\sap\CRQ\upg\abap\bin\DEFAULT.TPP
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 372.04.40 (release 701)
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 0
    meaning:
      Everything OK
    Do you think it could be the problem? Why I get the message of unknown SID & profile? Syntax problem? Iu00B4m working on Windows Server 2003.
    Thanks in advance.

    Hi,
    I've got strictly the same error in my upgrade step JOB_RSINDCHK  ( from ECC5.0 to     ECC6.0  Ehp4 / 701 NW)
    same step and  same symptoms .
    (job failed, dump on ST22, CX_ENH_INITERNAL_ERROR ,   object SFW_GET_SWITCHPOS)
    We solved the issue by implemented manually the oss note 1483283
    It mean :
    Unlock your system : tp unlocksys <SID> pf=/usr/sap/<SID>/upg/abap/bin/DEFAULT.TPP
    Then logon on your system  with your user
    se06 :  change the setting if necessary to allow modifications
    se80 :  chose class :  CL_ENH_BADI_PREGENERATION
                   then chose method =  BADI_PREGENERATION
    change "display" to "Change"
    and apply manually the corrections intructions deliver in oss note 1483283 (= correction 943161)
    by clic on it you can then acces to the code.
    after that check + activate the badi
    try to liberate your OT (for us only the task has been liberated, no way to liberate the OT...).
    Logoff
    Then re-lock your system :  tp locksys <SID> pf=/usr/sap/<SID>/upg/abap/bin/DEFAULT.TPP
    Repeat the failure step : job_rsindchk  .   For us it has been worked.
    Best regards
    Stéphane

Maybe you are looking for