Error in phase MAIN_SHADOW/START_SHDI_FIRST (Upgrade EHP)

Hello to all,
(This plataform is an IBM DB2 for i5/OS)
I´m performing a Enhancement Package upgrade in our sap system from EHP3 to EHP5, but I´m stuck in phase MAIN_SHADOW/START_SHDI_FIRST (STARTS THE SHADOW SYSTEM). This error show the following message:
severe error(s) occured in phase MAIN_SHADOW/START_SHDI_FIRST!
Last error code set: Shadow instance couldn´t be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG'
So, I will post here that log files.
STARTFI.LOG:
1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
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 Set tool parameters for shadow connect:
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="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2 ETQ399 Stopping shadow instance
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2 ETQ353 Starting system
3 ETQ399 Executing command: 'startsap  SID(DEV) INSTANCE(01) PROFILE('/usr/sap/DEV/EHPI/abap/DEV/SYS/profile/START_DVEBMGS01_SAPDEV') TYPE(*SHD)'.
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DEV", Nr="01", GwHost="SAPDEV", GwService="sapgw01"
2 ETQ231 RFC Login failed
2WETQ372 test RFC failed, rc="-1"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally
DEVTRACE.LOG:
DpShMCreate: sizeof(j2ee_adm)     3952
DpShMCreate: SHM_DP_ADM_KEY          (addr: 700000060000000, size: 6379664)
DpShMCreate: allocated sys_adm at 700000060000010
DpShMCreate: allocated wp_adm_list at 700000060002ff0
DpShMCreate: allocated wp_adm at 7000000600031e0
DpShMCreate: allocated tm_adm_list at 7000000600104b0
DpShMCreate: allocated tm_adm at 700000060010500
DpShMCreate: allocated appc_ca_adm at 700000060562e20
DpShMCreate: allocated comm_adm at 700000060572830
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 7000000606011d0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 700000060601280
DpShMCreate: allocated j2ee_adm at 7000000606012c0
DpShMCreate: allocated ca_info at 700000060602240
DpCommAttachTable: attached comm table (header=700000060572830/ft=700000060572840)
MtxInit: -2 0 0
DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm
Mon Sep  5 22:48:58 2011
GwISigint: received SIGINT (2), start shutdown phase
***LOG S30=> GwStopGateway, gateway stopped () [gwxxrd.c     12995]
Can you help me please, how to solve this error?
Best regards,
João Dimas - Portugal

... continuation...
The dev_w0:
M Mon Sep  5 22:48:48 2011
M  ThInit: running on host SAPDEV
M  calling db_connect ...
B  Loading DB library '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' ...
B  Library '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' loaded
B  Version of '/usr/sap/DEV/EHPI/abap/exe/dbdb4slib.o' is "720.00", patchlevel (0.98)
C  DB4 SQL Reparse Activated
C  *** ERROR => dbs/db4/schema contains wrong schema name SAPR3.
[dbsldb4.cpp  7094]
C  Error is ignored. Schema R3DEVDATA is used.
C  IBM i 7.1 - XDN Default
C  XDN-Port: Assuming 9600 + sapmsDEV mod 100 = 9600
C  as4IsHostLocal: SAPDBHOST 'SAPDEV' is local
C  R3INLPGM: RmtExeLib from /usr/sap/DEV/EHPI/abap/exe/DBSLDB4RMT
C  R3INLPGM: RmtExeLib is SAPDEVUPG
C  DBSLENCWT: rc=0, msg=CPF9897 CONCURRENT WRITE IS ENABLED.                                   
C  QXDARECVR PTF Level is: SI37200  

C Mon Sep  5 22:48:49 2011
C  DbSl/DB codepage check: OK - (Unicode).
C  Checking journal settings for QSQJRN    /R3DEVDATA : OK
C  === Central DB connect successfull! ===
C  === Connection settings ===
C  connected               = TRUE
C  con_hdl                 = 0
C  db_handle               = 1
C  dbhost                  = SAPDEV
C  dbhostport              = 9600
C  rdbname                 =                  
C  dblib                   = R3DEVSHD
C  r3sysle_changed         = TRUE
C  query_compl_reval       = O
C  dbconnecttype           = L
C  user                    = DEV01    
C  qaqqinilib              = Default (QUSRSYS)
C  dbjobname               = WP00     
C  dbjobuser               = DEV01    
C  dbjobno                 = 012091
C  rmtexelib               = SAPDEVUPG
C  parallel_alter_tables   = *OFF
C  ===========================
C  Query options file QUSRSYS/QAQQINI not found.
C  -----------------------------------------------------------------------------
C  ----- DbSl EGO Structure
C  -----------------------------------------------------------------------------
C     SAPSYSTEMNAME               = DEV
C     Character encoding          = UNICODE
C     process class               = dialog process
C     workprocess id              = 0
C     local host                  = SAPDEV
C     dbhost                      = SAPDEV
C     dbhostport                  = 9600
C     rdbname                     =                  
C     dbname                      = DEVSAPDEV
C     dblib                       = R3DEVSHD
C     application server          = DVEBMGS01
C     driver                      = DBSLDirectDrive
C     Connect type                = LOCAL
C     pid                         = 9088
C     wpjobname                   = WP00
C     wpjobuser                   = DEV01
C     wpjobno                     = 012091
C     DB2/400 vers. appl. server  = PASE 7.1
C     DB2/400 vers. DB server     = V7R1
C     da_cache_size               = 100
C     dbsl_buffersize             = 131072
C     reopen                      = ON
C     timeout_retry               = 3
C     alter_table_timeout_retry   = 3
C     ODP threshold               = 800
C     ODP commit thresh.          = 810
C     ODP open thresh.            = 850
C     QAQQINI library             = Default (QUSRSYS)
C     Alternate QAQQINI library   = Not specified
C     use_lobs_for_long           = ON
C     use_lobs_for_short          = OFF
C     single_execution_threshold  = 2000
C     single_execution_reuse      = OFF
C     keep_tmp_SQLpkgs            = OFF
M Mon Sep  5 22:48:54 2011
M  SecAudit(rsauinit): Start init of Security Audit Log for first wp.
M  in_ThErrHandle: 1
M  ThIErrHandle: new stat of W0 is WP_SHUTDOWN   
M  ThIErrHandle: I'm during shutdown
M  PfStatDisconnect: disconnect statistics
M  ThIErrHandle: entering ThSetStatError
M  ThShutDownServer: shutdown server
M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M  Entering ThReadDetachMode
M  call ThrShutDown (1)...
M  ***LOG Q02=> wp_halt, WPStop (Workp. 0 9088) [dpuxtool.c   327]

Similar Messages

  • Error in phase XPRAS_AIMMRG for Upgrade from 4.7 to ERP6 ehp5 sps5

    Hi All,
    We are in process in upgrading our sandbox system from 4.7 to ERP6.0
    EHP5 SPS5.
    During the downtime step we are facing an error in phase XPRAS_AIMMRG
    Upon investigation we found that there are short dumps in the system
    due to this error.
    Below is the extract of the short dumps generated by the job RDDEXECL
    Category Internal Kernel Error
    Runtime Errors DDIC_TYPE_INCONSISTENCY
    Application Component BC-ABA-LA
    Date and Time 05.12.2011 08:58:48
    Short text
    Inconsistency in the dictionary for the structure "KOMG".
    What happened?
    Error in the SAP kernel.
    The current ABAP "SAPLF82V" program had to be terminated because
    the
    ABAP processor detected an internal system error.
    Also, We I try to check the Table KOMG in SE11 is get the below messages.
    Check table KOMG (DDIC/05.12.11/10:00)
    Append structure OILKOMG appended to table KOMG
    Append structure OIUKOMG appended to table KOMG
    No customer or SAP include SI_KOMK_CM exists
    No customer or SAP include SI_KOMP_CM exists
    No customer or SAP include CI_PRS_CPILS_2 exists
    Enhancement category 3 possible, but include or subty. not
    yet classified
    Field LGORT in table KOMG is specified twice. Please check
    KOMG-ZZMVGR4: Table TVM1T in search help attachment differs
    from table of search field
    Check on table KOMG resulted in errors
    Has anyone received the below message in XPRAS phase during the upggrade.
    Any suggestion would be most welcome.
    Regards,
    Nilesh Jagtap

    Dear Nilesh,
    The reason for this issue is that the component 'LGORT' is indeed specified twice in structure KOMG on your system.
    It might be definied in the standard include as well as in your customer include.
    Please bear in mind, that if you append customer own structures to SAP standad structures, that the component names should start with 'Z' or even better 'ZZ'.
    That prevents the case which might have happened here, that the field you have added on customer side has also been delivered as part of an SAP standard include.
    So you should change your structure accordingly.
    Note 531835 describes how to add an own field to such structures. It might also be helpful for you.
    After you have repaired your structure you can activate the structure KOMG and the issue should be solved.
    Best Regards,
    Abhishek

  • Error in PHASE PREP_EXTRACT/PREIMP: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP4

    Hello,
    I'm currently in upgrading a SAP R/3 4.7 system to a SAP ECC 6.0 EHP4.
    Therefore I followed the Upgrade Guide from marketplace - installation- and upgrade guides - SAP ERP - SAP ERP 6.0 - SAP Enhancement Package 4 for SAP ERP 6.0 - Upgrade Guide SAP ERP including EHP4 SR1 - Unix on MaxDB.
    I downloaded media from marketplace/swdc - Installations and Upgrades - SAP Application Components - SAP ERP - SAP ERP ENHANCE PACKAGE - EHP4 FOR SAP ERP 6.0 / NW7.01 - Upgrade.
    I'm starting upgrade with upgrade master DVD 51036889_1 and      51036889_2.
    Now upgrade breaks down in phase PREP_EXTRACT/PREIMP with error:
    Severe error(s) occured in phase PREP_EXTRACT/PREIMP!
    Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
    PREIMP.ELG says:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    R3trans preimport and RETURN CODE in R710VPE.REX
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
    Kernel is stored in /usr/sap/REX/SYS/exe/run and database is ADA (maxdb).
    File R710VPE.REX says:
    4 EPU201XBEGIN OF SECTION BEING ANALYZED
    4 ETW000 R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 07.03.2011 - 15:28:36
    4 ETW000 control file: /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
    4 ETW000 > import
    4 ETW000 > file='/usr/sap/REX/upg/abap/bin/R710VPE.SAP'
    4 ETW000 > safeandslow=yes
    4 ETW000 > buffersync =yes
    4 ETW000 > commit     =1048576
    4 ETW000 > importtruncated =yes
    4 ETW000 R3trans was called as follows: R3trans -w /usr/sap/REX/upg/abap/tmp/R710VPE.REX -u 1 /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
    4 ETW000 active unconditional modes: 1
    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
    4 EPU202XEND OF SECTION BEING ANALYZED
    Can anybody help me out here?
    Regards,
    Julia

    Hello,
    I run 'R3trans -x' command, but there was no problem - connection to database was working.
    Problem was following:
    Before starting the sdt service on host, I set environment variables JAVA_HOME and LD_LIBRARY_PATH for sidadm. That's not neccessary and that was the problem. Without setting these variables it is working now.
    Thanks,
    Julia

  • Error in phase SCEXEC_ALIAS in upgrade process(during preprocessing)

    Hi all experts,
    i encountered error during upgrade from 4.7 to ecc 6
    with message :
    severe error during SCEXEC_ALIAS phases
    file /usr/sap/<SID>/upg/abap/log/PTALDC00.LOG not found
    below is some related log content for this error:
    tail log of ULOG11_2
    Phase SCEXEC_ALIAS:
    <sid>adm       20110527220015    : /usr/sap/<SID>/upg/abap/exenew/tp pf=/usr/sap/<SID>/upg/abap/bin/EXDBNEW.TPP execdbscript <SID> -x PTALDC00.XQL DBEXECNONT DBEXECNOCHECK  (pid=512002)
    <sid>adm       20110527220016    : /usr/sap/<SID>/upg/abap/exenew/tp pf=/usr/sap/<SID>/upg/abap/bin/EXDBNEW.TPP execdbscript <SID> -x PTALDC01.XQL DBEXECNONT DBEXECNOCHECK  (pid=1204298)
    <sid>adm       20110527220017    :/usr/sap/<SID>/upg/abap/exenew/tp pf=/usr/sap/<SID>/upg/abap/bin/EXDBNEW.TPP execdbscript <SID> -x PTALDC02.XQL DBEXECNONT DBEXECNOCHECK  (pid=675990)
    tail log of SLOG701
    Phase SCEXEC_ALIAS:
    ERROR: Connect to <SID> failed (20110527190129, probably wrong environment).
    ERROR: Connect to <SID> failed (20110527190130, probably wrong environment).
    ERROR: Connect to <SID> failed (20110527190131, probably wrong environment).
    my questions are:
    1. where is the environment variable stored during this phase which is used by tp tool?
    i have checked the profile EXDBNEW.TPP and compared it with other profile in the same directory which have been used by tp before(phases before this one), which resulted in no different for every environment related value.
    2. i tried to emulate the execution of the command in ULOG11_2 with default environment of <sid>adm with adjustments(e.g db_ora_scheme=SHDTMP, DIR_LIBRARY= /usr/sap/<SID>/abap/exenew) it run with no error of wrong environment whatsoever >.<, so can i just point the environment scheme to <SID>SHD  and executed it manually?

    well, actually i did not looking at the right place at the error , my apologize for that.
    there are another error messages at this log file SCEXEC_A.ECO
    TRACE-INFO: 68:  [dev trc    ,00000]  -->oci_prepare_stmt(con_hdl=0, len=0, stmth_p=110b1b588)                          20  0.209414
    TRACE-INFO: 69:  [dev trc    ,00000]        SELECT USERID,PASSWD FROM SAPUSER WHERE USERID IN (:A0,:A1)                                                            
    TRACE-INFO: 70:                                                                                11  0.209425
    TRACE-INFO: 71:  [dev trc    ,00000]  -  oci_bind  ( 0: SQLT_STR, l=256, con_hdl=0, stmth_p=110b1b588, vp=9001000a10b6ea2,ip=0,rlp=0,rcp=0)
    TRACE-INFO: 72:                                                                                21  0.209446
    TRACE-INFO: 73:  [dev trc    ,00000]  -  oci_bind  ( 1: SQLT_STR, l=256, con_hdl=0, stmth_p=110b1b588, vp=fffffffffffd978,ip=0,rlp=0,rcp=0)
    TRACE-INFO: 74:                                                                                14  0.209460
    TRACE-INFO: 75:  [dev trc    ,00000]  -->oci_define ( 0: SQLT_STR, l=256, con_hdl=0, stmth_p=110b1b588, vp=fffffffffffda78,ip=fffffffffffd7a0,rlp=0,rcp=0)
    TRACE-INFO: 76:                                                                                13  0.209473
    TRACE-INFO: 77:  [dev trc    ,00000]  -->oci_define ( 1: SQLT_AFC, l=256, con_hdl=0, stmth_p=110b1b588, vp=fffffffffffdb78,ip=fffffffffffd7a2,rlp=0,rcp=0)
    TRACE-INFO: 78:                                                                                16  0.209489
    TRACE-INFO: 79:  [dev trc    ,00000]  -->oci_execute_stmt(con_hdl=0, stmth_p=110b1b588, iters=1, rowoff=0, dml_batch_errors=0)
    TRACE-INFO: 80:                                                                                13  0.209502
    TRACE-INFO: 81:  [dev trc    ,00000]  OCIStmtExecute() completed, rc=100=OCI_NO_DATA, no further data                  8738  0.218240
    TRACE-INFO: 82:  [dev trc    ,00000]    -> rc=1403=OCI_ERR_NOT_FOUND                                                    18  0.218258
    TRACE-INFO: 83:  [dev trc    ,00000]  <--oci_execute_stmt(rc=1403, iters-errors = 1-0) [time 0,009s]                    11  0.218269
    TRACE-INFO: 84:  [dbsloci.    ,00000]  *** ERROR => ORA-1403 when accessing table SAPUSER                                15  0.218284
    TRACE-INFO: 85:  [dev trc    ,00000]    set_ocica() -> SQL code 1403                                                    8  0.218292
    TRACE-INFO: 86:  [dev trc    ,00000]  -->oci_get_errmsg (con_hdl=0, rc=1403)                                              7  0.218299
    TRACE-INFO: 87:  [dev trc    ,00000]    OCIErrorGet -> SQL error code: 1403                                            20  0.218319
    TRACE-INFO: 88:  [dev trc    ,00000]    ORA-01403: no data found      
    TRACE-INFO: 101:  [dev trc    ,00000]  Assigning username to user session: con_hdl=0, usrhp=110c09428                      8  0.219570
    TRACE-INFO: 102:  [dev trc    ,00000]  Assigning password to user session: con_hdl=0, usrhp=110c09428                    12  0.219582
    TRACE-INFO: 103:  [dev trc    ,00000]  Starting user session: OCISessionBegin(con_hdl=0, usr=SAPR3SHD/<pwd>, svchp=110b045e0, srvhp=110b05e88, usrhp=110c09428)
    TRACE-INFO: 104:                                                                                133  0.219715
    TRACE-INFO: 105:  [dev trc    ,00000]    OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR                        6298  0.226013
    TRACE-INFO: 106:  [dev trc    ,00000]    OCISessionBegin(OCI_DEFAULT) failed with SQL error 28000:                      11  0.226024
    TRACE-INFO: 107:  [dev trc    ,00000]    ORA-28000: the account is locked                                                                              
    TRACE-INFO: 108:                                                                                10  0.226034
    TRACE-INFO: 109:  [dev trc    ,00000]  server_detach(con_hdl=0,stale=1,svrhp=110b05e88)                                    8  0.226042
    TRACE-INFO: 110:  [dev trc    ,00000]  Detaching from DB Server (con_hdl=0,svchp=110b045e0,srvhp=110b05e88)                9  0.226051
    TRACE-INFO: 111:  [dev trc    ,00000]  Deallocating server context handle 110b05e88 from con_hdl=0                      176  0.226227
    TRACE-INFO: 112:  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '28000'                                14  0.226241
    TRACE-INFO: 113:  [dev trc    ,00000]    set_ocica() -> SQL error code 28000                                              7  0.226248
    TRACE-INFO: 114:  [dev trc    ,00000]  -->oci_get_errmsg (con_hdl=0, rc=28000)                                            7  0.226255
    TRACE-INFO: 115:  [dev trc    ,00000]    OCIErrorGet -> SQL error code: 28000                                            8  0.226263
    TRACE-INFO: 116:  [dev trc    ,00000]    ORA-28000: the account is locked                                                                              
    TRACE-INFO: 117:                                                                                10  0.226273
    TRACE-INFO: 118:  [dblink      ,00433]  ***LOG BY2=>sql error 28000  performing CON [dblink#4 @ 433]                      22  0.226295
    TRACE-INFO: 119:  [dblink      ,00433]  ***LOG BY0=>ORA-28000: the account is locked [dblink#4 @ 433]                      8  0.226303
    From the log, the problem actually lies in authorization for ops$user + locked shadow user account. After corrected these problems, the process continued. But this still bother me how this error came up since other tp processes(phases before this one) run successfully. But i will mark this question as answered. Thanks for all the attention and hope this will help others too ^^.

  • Error in phase "main_shdrun/act_upg" upgrade sapnetweaver 7.0 to EHP1

    Hello expert,
    I get error when upgrade our sapnetweaver pi 7.0 SP09 to EHP1 in phase MAIN_SHDRUN/ACT_UPG. I've try many suggestion in sdn forums, but cannot resolve my troubles. This is the content of file ACTUPG.ELG in my EHPI\abap\log:
      LIST OF ERRORS AND RETURN CODES  *******
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70105.X00
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "8"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPAA70106.X00
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "8"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPAB70010.X00
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1EEDO536X"Technical Settings" "DB6PMSQ_DB" could not be activated
    ETP111 exit code           : "8"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPAW70106.X00
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "8"
    I have try to edit the table from SE11, but it say: the table doesn't exist. And when i try to create the table, it's say: the table already exist.
    Please help me

    Hi,
    As described in archived SAP note that is no longer available the table DB6PMSQ_DB contains only
    SQL Cache snapshot data.
    Regarding these Technical Settings
    you can ignore these messages regarding technical settings.
    Please continue with option "Accept non severe errors and repeat phase"
    This should not cause any trouble later in the upgrade or in steps after phase ACT_UPG.
    Regards,
    Aidan

  • Error in PHASE ACT_UPG: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP

    Hello,
    I'm facing an error in phase MAIN_SHDRUN/ACT_UPG (see errors below).
    After searching for the errors I found postings with advice to change R3trans and tp to the newest version. Strangely system did not take the newest kernelpatch I stored in upgrade folder. So I changed the files in the /usr/sap/SID/abap/exe folder and repeated the phase.
    But the error is still there.
    A solution was to reset the queue, but this is only possible with help by sap.
    Error  in phase: DDIC_ACTIVATION
    So I'm waiting for their reaction since two days, but nothing happens.
    My questions are now:
    what happens if I use the option "initialize phase ACT_UPG to restart it from beginning"? Will the new R3trans be used? Have we got to to the SPDD again?
    What happens if I use the option "accept non severe errors and repeat phase ACT_UPG? Are these language errors "non-severe"?
    Errors:
    In error log ACTUPG.ELG I find logs like:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INERECRUIT.REX
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "8"
    In error log SAPup.ECO I find:
    EXECUTING /usr/sap/REX/upg/abap/exe/tp (/usr/sap/REX/upg/abap/exe/tp) pf=/usr/sap/REX/upg/abap/bin/ACTUPG.TPP put REX
    This is /usr/sap/REX/upg/abap/exe/tp version 376.01.14 (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.
    Looking for effective putsteps ... ... ready (looking for putsteps)
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    Process with ID 13163 terminated with status 8
    In the last touched SP-File SAPAAAA701.SID I can find errors like:
    "1EEDO545 "LANG" "DTEL" "*": Object information could not be imported"
    Regards,
    Julia

    After pushing the message at SAP I got the following answer:
    It is the problem from note 1417505. There is no guarantee that all objects where imported with the used R3trans. A rerun of phase will be unsuccessfully because error came up in DDIC_IMPORT.
    A reset of the queue is only possible if SPAM/SAINT is used for importing support packages. In case of upgrade, like here, the upgrade has got to be resetted as described in upgrade guide.
    After start between phase extraction and configuration the newest R3trans has got to be copied manually in /abap/exe folder.
    Regards,
    Julia

  • EHP installing. Error in phase MAIN_SHDRUN/JOB_MSSSPEXE_SHD

    Hello all,
    Dealing with ECC's EHP4 installation and having problem with step JOB_MSSSPEXE_SHD.
    Firstly, want to give some system overview.
    System was migrated from x32 non-Unicode to x64 Unicode through SystemCopy
    OS: Windows Server 2008 SP2
    DB: MS SQL Server 2008 version 10.0.2531.0
    SAP: (only ABAP Web AS is installed)
    NW 7.0, ECC 6.0 SPS 20, kernel version 7.0 236
    java version - 1.4.2_17-x64
    Now doing installation of ECC EHP 4 / NW 7.01 SPS6 .
    Using SAPehpi 710 2.005.001 package 24
    Using latest dbmsslib.dll (released 05/12/2010)
    Had no problems till the Preprocessing Step
    Error that EHPi produced is:
    Severe error(s) occured in phase MAIN_SHDRUN/JOB_MSSSPEXE_SHD!
    Last error code set: BATCHJOB MSSSPEXE on shadow instance FAILED: Batchjob MSSSPEXE aborted.
    JOBLOG.LOG :
    |Time |User |Program |Priority|Grp|N|Text |
    |09:25:07|SAPSYS|RSBTCRTE| |EB |E|Failed to read step $$$$$ of job (database error code: 00064)|
    |09:25:07|SAPSYS|RSBTCRTE| |EB |C|> Job MSSSPEXE |
    |09:25:07|SAPSYS|RSBTCRTE| |D0 |1|Transaction Canceled 00 529 ( 001 ) |
    PMSSSPEXE.LOG:
    1 ETQ200 Executing actual phase 'MAIN_SHDRUN/JOB_MSSSPEXE_SHD'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'MSSSPEXE'
    2 ETQ399 Arg[1] = ''
    2 ETQ399 Arg[2] = 'NO-IGNORE'
    2 ETQ399 Arg[3] = ''
    2 ETQ399 Arg[4] = '5'
    2 ETQ399 Arg[5] = 'MSSQL SPECIFIC ACTIONS'
    2 ETQ399 Arg[6] = 'PMSSSPEX.ELG'
    4 ETQ260 Starting batchjob "MSSSPEXE"
    4 ETQ010 Date & Time: 20100625092507
    4 ETQ260 Starting batchjob "MSSSPEXE"
    4 ETQ230 Starting RFC Login to: System = "PRD", GwHost = "SAP", GwService = "sapgw01"
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    4 ETQ399 JOBNAME='MSSSPEXE', REPNAME='MSSSPEXE', VARNAME='', BATCHHOST='SAP', IV_SCHEDEVER=' '
    4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
    4 ETQ399 Returned JOBCOUNT='09250700'
    4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
    4 ETQ010 Date & Time: 20100625092512
    4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
    4 ETQ239 Logging off from SAP system
    2EETQ262 Batchjob "MSSSPEXE" aborted
    4 ETQ359 RFC Login to: System="PRD", Nr="01", GwHost="SAP", GwService="sapgw01"
    4 ETQ232 RFC Login succeeded
    Next I've connected to shadow instance, increased Trace level of batch process to 3 and went to ST11.
    dev_w12 log:
    L BtcAuthSet: Begin: username=DDIC
    L BtcAuthSet: zttabtckln = 500
    L BtcAuthSet: jobname=MSSSPEXE , jobcount=09250700, status=S
    L BtcAuthSet: jobgroup=%_IMMEDIATE , stepcount=0
    L BtcAuthSet: authcknam= , authckman=000
    L BtcAuthSet: step_cnt=33679104
    L BtcAuthSet: step_ptr->stepcount=1
    B { db_rtab( fcode = 'RT_READ_ONLY', tname = 'TBTCPV' ) {btcjcntl.c:941}
    B NTAB: tabname: TBTCPV , fcode: 1
    M PfSetActDBConRec: record found for dbcon <>
    M PfStatBegin: open DBCON rec with opcode 10
    M push timestack[0] = STAT_READDIR
    M pop timestack[0] = STAT_READDIR
    M PfStatEnd: close DBCON rec after opcode 10
    M PfSetActDBConRec: record found for dbcon <>
    M PfStatBegin: open DBCON rec with opcode 10
    M push timestack[0] = STAT_READDIR
    M pop timestack[0] = STAT_READDIR
    M PfStatEnd: close DBCON rec after opcode 10
    B } db_rtab( fcode = 'RT_READ_ONLY', retcode = 64 )
    L *** ERROR => BtcAuthSet: db_rtab-call failed, rc: 64 [btcjcntl.c 946]
    A + SAPSYS 40088 BATCH 00 529 rlv=clean
    A RFC> get SPA_SESSION_ARFC: NORMAL
    A RFC> ab_RfcTraceConnInfo (OFF) (handle: 0, dump_connection_info: 0)
    A ab_rfcclose_ex: closed 0 handles for owner 39368 (0 skipped)
    A RFC> not running in Plugin session
    Free space is about 50 Gb on server. Database files have unrestricted growth.
    I have no idea what kind of error is "db_rtab-call failed, rc: 64"
    Any help will be highly appreciated.
    Thank you
    Alexey

    Hi
    I am getting error in MSSSPEXE job in Preprocessing phase in Ehp6 upgrade.
    MAIN_SHDPREPUT/JOB_MSSSPEXE_SHD_PRE
    MSSSPEXE job aborted
    Batchjob 'MSSSPEXE' with id '11484300' aborted
    Reviewing Short dump is says the following:
    Runtime Errors         SYNTAX_ERROR
    Date and Time          03.11.2013 00:47:55
    Short Text
         Syntax error in program "SAPLMSSPROCS ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "MSSSPEXE" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLMSSPROCS " in inclu
          "LMSSPROCSUXX " in
         line 9:
         "INCLUDE report "LMSSPROCSU04" not found"
         The include has been created and last changed by:
         Created by: "SAP "
         Last changed by: "SAP "
         Error in the ABAP Application Program
         The current ABAP program "MSSSPEXE" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          03.11.2013 00:47:55
    Short Text
         Syntax error in program "SAPLMSSPROCS ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "MSSSPEXE" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLMSSPROCS " in inclu
          "LMSSPROCSUXX " in
         line 9:
         "INCLUDE report "LMSSPROCSU04" not found"
         The include has been created and last changed by:
         Created by: "SAP "
         Last changed by: "SAP "
         Error in the ABAP Application Program
         The current ABAP program "MSSSPEXE" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Regards

  • Error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC - EHP3 upgrade

    Hello all,
    Using SUM while running SCM 7.0 EHP3 upgrade I am getting error in phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC:
    Checks after phase MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC were negative!
    Last error code set: Single errors (code &gt; 8) found in logfile 'MVNTFDC.ELG'<br/> 1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
    ERROR: Detected the following errors:
    # D:\SUM\abap\log\PD000203.SCD:
    3 ETP000 NOT NULL )
    3 ETP000 ON [/BIC/FZT_DEL_C1_PSCH000]
    3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
    3 ETP000
    2WETP000 11:10:14: Retcode 1: error in DDL statement for "/1CRR/TG00003781 " - repeat
    2EETP345 11:10:26: Retcode 1: SQL-error "2726-Partition function '/BIC/FZT_DEL_C1_PFUN000' uses 1 c
    2EETP345 olumns which does not match with the number of partition columns used to partition the tab
    2EETP345 le or index." in DDL statement for "/1CRR/TG00003781 "
    2 ETP000 --------------- DB-ROLLBACK() ---------------
    2EETP334 11:10:26: error in DDL, nametab for "/1CRR/TG00003781" not activated
    3 ETP000 NOT NULL )
    3 ETP000 ON [/BIC/FZT_DEL_C2_PSCH000]
    3 ETP000 WITH ( DATA_COMPRESSION = PAGE )
    ...skipped 18 more lines. Please see MVNTFDC.html for more information.
    I checked some other log files:
    MVNTFDC
    1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC" ("20150203110951")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'
    1 ETQ206 Executing pre-phase DB specific actions.
    1 ETQ200 Executing actual phase 'MAIN_SHDRUN/SUBMOD_FDC_RUN/PARMVNT_FDC'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'TP_MOVENTABS_SHD'
    2 ETQ399 Arg[1] = 'INTDEL;INTACT;NOBUFFRESET;SHADOW_ONLY'
    2 ETQ399 Arg[2] = 'MF=F,STEP=T,RANGE-TS'
    2 ETQ399 Arg[3] = 'MVNTFDC.TP0'
    1 ETQ399 Using error summary log 'MVNTFDC.ELG'.
    1 ETQ399 Using 8 parallel processes
    2 ETQ399 Empty putsteps - configuring at least parallel batches and main import processes.
    2 ETQ399 Distribute 8 parallel processes to 2 tp and 4 R3trans.
    4 ETQ380 computing toolpath for request "TP_MOVENTABS_SHD"
    4 ETQ381 request "TP_MOVENTABS_SHD" means "tp mvntabs for shadow tables"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHD"
    4 ETQ399 Requirement for tp maps to 'exe'
    4 ETQ383 translates to path "D:\SUM\abap\exe"
    2 ETQ399 Starting 8 tp processes:
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 7444 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 7444
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 4888 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=01" "seltsize=1" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP01.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 4888
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 9100 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=02" "seltsize=2" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP02.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 9100
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 736 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=03" "seltsize=3" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP03.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 736
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 8864 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=04" "seltsize=4" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP04.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 8864
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 9264 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=05" "seltsize=5" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP05.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 9264
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 9732 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=06" "seltsize=6" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP06.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 9732
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203110952: PID 11492 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=07" "seltsize=7" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP07.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 11492
    3 ETQ123 20150203110954: PID 9264 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110954: PID 7444 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110954: PID 4888 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110954: PID 736 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110954: PID 9732 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110956: PID 11492 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110956: PID 9100 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    3 ETQ123 20150203110956: PID 8864 exited with status 0 (time 0.000 real)
    2 ETQ399 tp ddlntabs finished with exit code 0.
    2 ETQ399 Looking for pattern 'PD00....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD000203.SCD'.
    1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 9525 to 12695 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
    2 ETQ399 Looking for pattern 'PD01....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD010203.SCD'.
    1 ETQ124 Scanned file 'log\PD010203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD01....\.SCD'
    2 ETQ399 Looking for pattern 'PD02....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD020203.SCD'.
    1 ETQ124 Scanned file 'log\PD020203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD02....\.SCD'
    2 ETQ399 Looking for pattern 'PD03....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD030203.SCD'.
    1 ETQ124 Scanned file 'log\PD030203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD03....\.SCD'
    2 ETQ399 Looking for pattern 'PD04....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD040203.SCD'.
    1 ETQ124 Scanned file 'log\PD040203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD04....\.SCD'
    2 ETQ399 Looking for pattern 'PD05....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD050203.SCD'.
    1 ETQ124 Scanned file 'log\PD050203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD05....\.SCD'
    2 ETQ399 Looking for pattern 'PD06....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD060203.SCD'.
    1 ETQ124 Scanned file 'log\PD060203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD06....\.SCD'
    2 ETQ399 Looking for pattern 'PD07....\.SCD'
    2 ETQ399 Wasting log file 'D:\SUM\abap\log\PD070203.SCD'.
    1 ETQ124 Scanned file 'log\PD070203.SCD' from offset 3394 to 6564 for errors.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD07....\.SCD'
    2 ETQ399 Starting 1 tp processes:
    4 ETQ010 Starting: tp ddlntabs operation
    3 ETQ121 20150203111013: PID 8692 execute 'D:\SUM\abap\exe\tp "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"' in background, output written to 'D:\SUM\abap\log\TP00.ECO'.
    2 ETQ399 Started tp ddlntabs with pid 8692
    3 ETQ123 20150203111050: PID 8692 exited with status 8 (time 0.000 real)
    2EETQ399 tp ddlntabs failed with exit code 8.
    2 ETQ399 Operation 'ddlntabs' looking for pattern 'PD00....\.SCD'
    1 ETQ124 Scanned file 'log\PD000203.SCD' from offset 12805 to 18826 for errors.
    4 ETQ399 html file conversion from 'D:\SUM\abap\log\MVNTFDC.ELG' to 'MVNTFDC.html' succeeded.
    4 ETQ010 Date & Time: 20150203111051 
    1EETQ399 Last error code set is: Single errors (code > 8) found in logfile 'MVNTFDC.ELG'
    1 tp processes returned errors. View latest 'TP*.ECO' files in log-directory for details
    1EETQ203 Upgrade phase "PARMVNT_FDC" aborted with errors ("20150203111051")
    TP00.ECO
    SAPup> Starting subprocess in phase 'TP_ACTION_CP2SINI' at 20150202112054
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\CP2SHDI.TPP" r3e SAPKBBF740 -s SCD u18
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    This is D:\SUM\abap\exe\R3trans.exe version 6.24 (release 741 - 11.08.14 - 17:21:00).
    unicode enabled version
    D:\SUM\abap\exe\R3trans.exe finished (0004).
    INFO: No client specified on command line. Taking client 0 from E070C.
    tp finished with return code: 4
    meaning:
      A tool used by tp produced warnings
    SAPup> Process with PID 7592 terminated with status 4 at 20150202112055!
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213004
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 0
    meaning:
      Everything OK
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150202213118
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    SAPup> Process with PID 5336 terminated with status 8 at 20150202213638!
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102328
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 0
    meaning:
      Everything OK
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203102350
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    SAPup> Process with PID 10396 terminated with status 8 at 20150203102427!
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203110952
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" "seltsize=0" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 0
    meaning:
      Everything OK
    SAPup> Starting subprocess in phase 'PARMVNT_FDC' at 20150203111013
        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        ENV: PATH=D:\SUM\abap\exe;D:\sapdb\programs\bin;D:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;D:\Program Files\Microsoft SQL Server\100\Tools\Binn;D:\usr\sap\SCD\SYS\exe\uc\NTAMD64
        ENV: SAPSYSTEMNAME=SCD
        ENV: dbms_type=mss
        ENV: dbs_mss_schema=scd
        PWD: D:\SUM\abap\tmp
    EXECUTING D:\SUM\abap\exe\tp.EXE "pf=D:\SUM\abap\var\MVNTFDC.TPP" ddlntabs SCD "ddlmode=F" "step=T" "protyear=00" shadow_only "strel=701" "substext=4G" "-Dbuffreset=no"
    This is D:\SUM\abap\exe\tp.EXE version 380.27.37 (release 741, unicode enabled)
    tp finished with return code: 8
    meaning:
      A tool used by tp produced errors
    SAPup> Process with PID 8692 terminated with status 8 at 20150203111050!
    Can someone please help ?

    Hi Pankaj,
    did you get any solution for this issue ? I am also facing the same error in my BW upgrade to EHP3.
    Please share the solution if you get any.
    Regards,

  • SRM 4.0 upgrade to SRM 7.0 - Error in Phase PARDIST_SHD

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

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

  • EHP4 upgrade: Error in Phase ACT_UPG

    Hi All,
    While upgrading to EHP4 on ECC 6 system, we got error in phase MAIN_SHDRUN/ACT_UPG
    Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
    Last error code set: Unresolved requests in buffer RH4 Check logfiles 'ACTUPG.ELG' and '/sapdump/SAPehpi/EHPI/abap/log/SAPehpi.ECO'
    ACT_UPG log:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-604DMINISPSCA.RH4
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "12"
    Log of SAPA-604DMINISPSCA.RH4
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP101 transport order     : "SAPK-604DMINISPSCA"
    1 ETP102 system              : "RH4"
    1 ETP108 tp path             : "/sapdump/SAPehpi/EHPI/abap/exe/tp"
    1 ETP109 version and release : "372.04.70" "700"
    1 ETP198
    3 EPU324 See log for request "/sapdump/SAPehpi/EHPI/abap/tmp/SAPAB70015.RH4" (timestamp "01:26:08", system "RH4")
    1AETR012XProgram terminated (job: "RDDMASGL", no.: "01260600")
    1AEPU320 See job log"RDDMASGL""01260600""RH4"
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP110 end date and time   : "20091012033215"
    1 ETP111 exit code           : "12"
    1 ETP111 exit code           : "12"
    Job RDDMASG log :
    Job cancelled with following log
    2.10.2009 01:26:07 Job started                                                               00           516          S
    2.10.2009 01:26:07 Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)      00           550          S
    2.10.2009 01:26:08 Start of mass activation 01:26:08                                         AD           010          S
    when tried to log into shadow instance after getting error, it is giving error
    RH4: system message
    work process restarted; session terminated;
    we restarted shadow system. There is no dumps in the shadow system.
    Work process getting killed after 7800s
    checked in work directory of Shadow system:  devdisp log :_*
    Mon Oct 12 04:49:46 2009
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1694]
    ***LOG Q0K=> DpMsAttach, mscon ( HW136799) [dpxxdisp.c   12639]
    DpStartStopMsg: send start message (myname is >HW136799_RH4_22                         <)
    DpStartStopMsg: start msg sent
    Warning: Swap space is configured quite small with 20477 MB.
    It should be configured with at least 20 GB on 64 bit systems.
    See note 153641 for more information.
    Warning: tmpfs at /dev/shm is configured quite small with 1972 MB!
    Minimum value is 8192 MB.
    Recommended size is 75 % of RAM + swap.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Mon Oct 12 04:49:47 2009
    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 221
    Release check o.K.
    MBUF state ACTIVE
    DpModState: change server state from STARTING to ACTIVE
    Mon Oct 12 06:57:01 2009
    ERROR => DpWPCheck: W8 (pid 9769) died (severity=0, status=7) [dpxxdisp.c   15776]
    child (pid=9769) killed with signal 7
    Mon Oct 12 06:57:43 2009
    ERROR => DpWPCheck: W7 (pid 9768) died (severity=0, status=7) [dpxxdisp.c   15776]
    child (pid=9768) killed with signal 7
    Please let us know what needs to be cheked for the problem
    Thanks,
    Ramesh Ramagowni

    Hi Markas and All,
    Thanks for the information. /dev/shm was 100% full. now, the issue is solved after deleting its contents. and we have finished with EHP4 upgrade.
    After upgrade, SAP_AP component still showing as 700
    SAP_AP - 700 - 0015 - SAPKNA7015 -SAP Application Platform
    Can we delete old tablespace PSAPSR3700, it is showing as 0% used in brspace at present.
    Also while trying to move some datafiles using brtools after upgrade we are getting following error,
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.52
    BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
    c
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0252E Function fopen() failed for '/oracle/RH4/sapbackup/.user.pas' at location BrToolCall-2
    BR0253E errno 13: Permission denied
    BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
    BR0280I BRTOOLS time stamp: 2009-10-20 01.45.54
    BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
    There is no file in the directory '/oracle/RH4/sapbackup/.user.pas'
    Please suggest what needs to be for this issue..Do we need to upgrade BRTOOLS..
    Thanks,
    Ramesh R

  • Error encountered in phase SHDINST_DB_PREP - EHP1 upgrade using EHPI.

    Hi Experts,
    I am currently in the configuration phase of Enterprise Portal upgrade from 700 to EHP1 then i got this error in phase SHDNST_DB_PREP, I am using OS platform Windows Server 2003; here is the message:
    On the EHPi GUI:
    Decide how you want to continue
    Checks after phase PREP_INSTALL/SHDINST_DB_PREP were negative!
    Last error code set: Process 'brconnect' exited with 5, see 'D:\EHPI\abap\log\SHDUSRCRE.LOG' for detai
    Trouble Ticket Generation
    A trouble ticket and an archive with all relevant log files have been generated. Trouble ticket: "D:\EHPI\abap\log\SAPehpi_troubleticket.log" Log archive: "D:\EHPI\abap\log\SAPehpi_troubleticket_logs.sar"
    Choose Action:
    Repeat phase SHDNST_DB_PREP to continue at the point it stopped.
    Restart the current module from the beginning
    Exit this program
    for SHDUSRCRE.LOG:
    SAPehpi> Starting subprocess brconnect with id 13588 at 20100816143027
    Environment: CLASSPATH=C:\oracle\CUSDEV01\102\jdbc\lib\ojdbc14.jar;
    Environment: JAVA_HOME=C:\j2sdk1.4.2_13-x64
    Environment: NLS_LANG=AMERICAN_AMERICA.UTF8
    Environment: ORACLE_HOME=C:\oracle\EP1\102
    Environment: ORACLE_SID=EP1
    Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
    Environment: Path=E:\oracle\CUSPRD01\102\bin;C:\oracle\CUSDEV01\102\bin;C:\oracle\EP1\102\BIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Dell\SysMgt\oma\bin;C:\usr\sap\EP1\SYS\exe\uc\NTAMD64;C:\Program Files (x86)\Dell\SysMgt\oma\bin
    Environment: auth_shadow_upgrade=0
    Environment: dbms_type=ora
    Environment: dbs_ora_schema=SAPEP1
    Environment: dbs_ora_tnsname=EP1
    BR0801I BRCONNECT 7.00 (42)
    BR0280I BRCONNECT time stamp: 2010-08-16 14.30.28
    BR0301E SQL error -28003 at location crown_main-1, SQL statement:
    '/* BRCONNECT */ CREATE USER "SAPEP1SHD" IDENTIFIED BY "kXZvHmKI.42aB"'
    ORA-28003: password verification for the specified password failed
    ORA-20003: Password should contain at least one \
                  digit, one character and one punctuation
    BR1336I Creating database owner SAPEP1SHD failed
    BR0280I BRCONNECT time stamp: 2010-08-16 14.30.28
    BR0804I BRCONNECT terminated with errors
    Process with ID 15076 terminated with status 5
    Did you encounter this error? How can i solve it?
    Thanks a lot!
    Regards,
    Tony

    Hello Experts,
    I already solved the issue, just creating the user manually at command promp,
    the problem is that the password that SAP generated was not compatible or not acceptble to the system that is why i manually created the user:
    SQL> CREATE USER SAPEP1SHD IDENTIFIED BY kXZvHmKI_42aB;   - > correct one
    SQL> CREATE USER SAPEP1SHD IDENTIFIED BY kXZvHmKI.42aB;    - > incorrect; generated by the system
    Thanks & Regards,
    Tony

  • We are upgrading EHP 3 on ECC 6.0, but we received the following error:

    The installation was stopped, since an error occurred during the phase
    DDIC_ACTIVATION, which the Add-On Installation Tool is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Continue in the queue display.
    The following details help you to analyze the problem:
    - Error in phase: DDIC_ACTIVATION
    - Reason for error: TP_STEP_FAILURE
    - Return code: 0008
    -Error message: OCS Package SAPK-60301INEAAPPL, tp step A, return
    code 0008
    - REA16-KONZIGR: Field TARIFNR of the assignment does not exist in the search help ISU_FFEE_GROUP
    Regards,
    Tuvya

    HEllo, did you fix it ? we jumped into the same Issue and our EHP3 implementation broke and have to return to backups. Best Regards
    Juan

  • Error at Phase SHDINST_OS in 4.71 upgrade

    Hi,
    I am getting the below error. i created a service SAPDEV_01 by using the below give syntax, it was created but when i am trying to start that service(SAPDEV_01) i am getting an error called " cannot start the service in the local computer. error1069: service could not start due to logon failure." so please help me in solving below error:
    START OF PHASE SHDINST_OS
    An error occurred during the installation of the
    SAP service SAPDEV_01:
    Possibly the password for user .\SAPServiceDEV entered in phase
    INITPUT was wrong. You can reset it by calling 'R3up set stdpar'.
    Try to execute SAPSTARTSRV.EXE manually using the following syntax:
    C:\usr\sap\put\exe\sapstartsrv.exe -r
    -p C:\usr\sap\put\DEV\SYS\profile\START_DVEBMGS01_home1 -s DEV -n 01
    -U .\SAPServiceDEV -P <PASSWORD> -e HOME1\devadm
    and check if the service SAPDEV_01 can be stopped and restarted.

    this post is duplciated at Re: Error at Phase SHDINST_OS in 4.71 upgrade

  • Errors in PHASE DIFFEX phase during the CRM 6.0 upg from CRM 5.0

    Hello,
    I am in the process of upgading our CRM systems from CRM 5.0 version to
    CRM 6.0 and having issues at the PHASE DIFFEXPADDE during the upgrade
    right after the DB_ACTION_LOWQ1 phase and ADJUSTCHK being the previous
    phase.
    We are currently at CRM 5.0 dual stack system on Linux X86_64 SLES9 and
    DB - Oracle 10.2.0.2.
    I was able to finish the PREPARE phases on both ABAP & JAVA stacks
    successfully.
    The phase DIFFEXPADDE is failing with a error message in the
    DIFFEXPA.ELG which I have mentioned below. I am also attching few other
    related logs for your reference in the attached zip file
    (DIFFEXPA_logs.rar)
    DIFFEXPA.LOG
    UpgDialog.log
    SAPECCI700.C15
    TP00.ECO
    SAPup.log
    "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ADD ON OBJECTS (DATA)-Export ERRORS and RETURN CODE in SAPECCI700.<SID>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EETW190 "INDX" "WFMFC_INDTOR_GRP 01 " has no active
    version.
    Long text:
    Cause
    You have tried to export a Dictionary object that has no active
    version. The reason for this probably is that the author of the DD object has forgotten to activate it.
    System Response
    The transport request is not released.
    What to do
    Activate the Dictionary object and repeat the export.
    2EETP200 Export with errors, request will not be imported
    Long text:
    Cause
    The export was finished with errors or terminated (return code >=
    8).
    System Response
    The request is not imported. Instead it is set back to "can be
    changed"
    in the source system.
    What to do
    The export log contains remarks concerning the reason for the
    incorrect
    export. Correct the error and repeat the export.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ADD ON OBJECTS (DATA)-Export ERRORS and RETURN CODE in SAPECCI701.C15
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ADD ON OBJECTS (DATA)-Export ERRORS and RETURN CODE in SAPECCI702.C15
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    I am stuck at this step and unable to move forward until I get past
    this error. Please let me know how do I proceed and if you have any
    more questions.
    Would appreciate your early help!
    Thanks in advance!

    I was able to get past this issue by logging in to the client 000 and
    activate the object WFMFC_INDTOR_GRP from transaction SE11.
    Dictionary Object --> Activate from the menu bar. Gave me few warnings
    but did not error out.
    Hence went past the phase and the upgrade is progressing as of now.
    However, can you please confirm if this is a correct fix or do you want
    me to do anything different since I have not reached the MODPROF_TRANS
    phase yet.
    Thanks

  • SAINT error in phase DISASSEMBLE

    Hi,
    I am performing Delta-upgrade of component ST-SER from 700_2007_1 to 700_2008_1 via SAINT on our Solution Manager 4.0 system. (Windows server 2003 / MS SQL)
    The SAR archive (KITLONB.SAR) is of 141 MB.
    while trying to uncar i get following message:
    SAPCAR: processing archive D:\SPS17\ST-SER_2008\Inst\KITLONB.SAR (version 2.01)
    x EPS/in/CSR0120031469_0029513.ATT
    x EPS/in/CSR0120031469_0029513.PAT
    SAPCAR: error reading from D:\SPS17\ST-SER_2008\Inst\KITLONB.SAR
    But the EPS files have been loaded in the system & visible in the queue as well.
    The import fails in phase DISASSEMBLE with following error:
    Error in phase - DISASSEMBLE
    Reason for error - PATCH_FILE_READ_ERROR
    Return code - 12
    Error message - OCS Package : SAPKITLONB
    File has Full Control given to groups Administrator, SAP_LocalAdmin and SYSTEM.
    What could be the reason?

    Check your SAPCAR executable. 
    File hasn't been uncared properly.  You may uncar on your desktop and then transfer to server. 
    Other option is to load from SAINT tool > Load > Package from Application Server > Give location and it will uncar at right place.
    Thanks,
    Digesh
    Edited by: digeshjoshi on Aug 14, 2009 5:01 PM

Maybe you are looking for