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

Similar Messages

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

  • 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

  • ACTIVATION Error during phase MAIN_SHDRUN/ACT_UPG

    Hello Experts,
    I am facing an activation error during upgrade o ECC 6.0 EHP 6 in shadow instance.
    ERROR: Detected the following errors:
    # F:\SUM\abap\log\SAPA702EPU.UAS:  3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P" 3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P" 1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check 2WEDT135 Flag: 'Incorrect enhancement category' could not be updated 3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated 1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated  3 EMC738XActivate view "V_T706S_EHP" 1EEMC560 Field "T706S"-"D2100" does not exist 1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist 1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist 3 EMC742 View "V_T706S_EHP" was not activated 1EEDO519 "View" "V_T706S_EHP" could not be activated
    ...skipped 13 more lines. Please see ACTUPG.html for more information.
    SAPup_troubleticket.log
    This trouble ticket was created by SAPup on 20140801092425
    SAPup broke during phase ACT_UPG in module MAIN_SHDRUN / Shadow System Operations: SPDD and Activation
    Error Message: Detected 5 errors summarized in 'ACTUPG.ELG'
    Calling 'F:\SUM\abap\exe/tp' failed with return code 8, check F:\SUM\abap\log\SAPup.ECO for details
    tp used shadow connect
    ACTUPG.ELG:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in F:\SUM\abap\log\SAPA-10202INPOASBC.UAS
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "8">
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA702EPU.UAS
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       3 EDT012XActivate table "PTRV_UTIL_VPFPS_VPFPA_P"
       3 EDT402 Append structure "PTRV_VPFPS_VPFPA_P_APPEND" appended to table "PTRV_UTIL_VPFPS_VPFPA_P"
       1EEDT963 Field "TIME_DURATION" in table "PTRV_UTIL_VPFPS_VPFPA_P" is specified twice. Please check
       2WEDT135 Flag: 'Incorrect enhancement category' could not be updated
       3 EDT013 Table "PTRV_UTIL_VPFPS_VPFPA_P" was not activated
    1EEDO519X"Table" "PTRV_UTIL_VPFPS_VPFPA_P" could not be activated
       3 EMC738XActivate view "V_T706S_EHP"
       1EEMC560 Field "T706S"-"D2100" does not exist
       1EEMC560 Field "T706S"-"EXCHANGE_DATE" does not exist
       1EEMC560 Field "T706S"-"TRIP_BREAK_CNTRY" does not exist
       3 EMC742 View "V_T706S_EHP" was not activated
    1EEDO519 "View" "V_T706S_EHP" could not be activated
       3 EDT014XActivate dependent table "/MRSS/T_CUP_OBJECT"
       1EEDT242 Field "FIELD_DESCRIPTIONS": Component type or domain used not active or does not exist
       2WEDT183 Field "INSTANCE"-"/MRSS/IF_CUP_OBJECTS": Reference type used is not active
       1EEDT005 Nametab for table "/MRSS/T_CUP_OBJECT" cannot be generated
       3 EDT015 Dependent table "/MRSS/T_CUP_OBJECT" was not activated
    1EEDO519 "Table" "/MRSS/T_CUP_OBJECT" could not be activated
       3 EDT014XActivate dependent table "T706S"
       1EEDT963 Field "TRIP_BREAK" in table "T706S" is specified twice. Please check
       3 EDT015 Dependent table "T706S" was not activated
    1EEDO519 "Table" "T706S" could not be activated
    1 ETP111 exit code           : "8"
    SAPA702EPU.SID
    ent tables)
    2WEDO549 "View" "V_TWGVALE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWH01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0100" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0200" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0250" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF0260" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF501" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF600" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWICSCMF8003" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWLOF" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWMWQ" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWPC_COLHEAD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWPC_COLHEAD_C" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWRF2" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWSD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWTFMA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TWZLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TXW_AD01D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZB0W" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZB6D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZBABG" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZBABGZB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0B" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0BI" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZD0BW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZE02" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZE03D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZONE_M" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZPAB3" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZT01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZT01D" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_TZV04" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_UEBER" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USCOMP" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USCOMPA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_USR_NAME" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VGNVA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VGNWA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_BUK" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GFL" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GR" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_GRA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIGWVOBW_WE" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB01" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB02" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VIOB03" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VITXT" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VLBLTD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VLTD" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VTDST" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_VTSPLS" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WBEW" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WCUSDOC_RELA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WITH_CTNCOT005" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFBA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFBB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFKC" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFRA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFRB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WLFZUC10" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRBLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRGLA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRGLB" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRLBA" was activated (warning for the dependent tables)
    2WEDO549 "View" "V_WRSZ" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_VBRK_WBGT" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_WBRK_WBRP" was activated (warning for the dependent tables)
    2WEDO549 "View" "WB2_V_WBRK_WBRP2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVAP" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVHE" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVITX" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVJ" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVM1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVN1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO3" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO4" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO5" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO6" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO7" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO8" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVO9" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOA" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOC" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOD" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVODX" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOE" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOF" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVOI" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP0" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP3" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP4" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP5" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP6" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP7" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVP8" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVPN1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVPU1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVW" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVWA1" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVWA2" was activated (warning for the dependent tables)
    2WEDO549 "View" "WCVZ1" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWM_VSNACH_LIKP" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_DLR_BR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_DLR_PROOR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_EMGAR_DC" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_USR_DISTR" was activated (warning for the dependent tables)
    2WEDO549 "View" "YWTY_V_WORKBY" was activated (warning for the dependent tables)
    2WEDO549 "View" "ZZLIB_V_HKTK" was activated (warning for the dependent tables)
    2WEDO549 "View" "ZZLIB_V_LIFNR_C" was activated (warning for the dependent tables)
    1 ED0301X*************************************************************************
    1 ED0306       "Final log"
    1 ED0322 End phase  "006" ***********************************************************
    1 ED0320XStart phase "007" **********************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0301 *************************************************************************
    1 EDO601XNumber of objects to be activated............:  "35325"
    1 EDO605 Objects not activated........................:  "4"
    1 EDO606 Activated objects with errors in dependencies:  "4"
    1 EDO604 Objects activated with warning...............:  "5531"
    1 EDO603 Successfully activated objects...............:  "29786"
    1 EDO602 Number of objects to be deleted..............:  "128"
    1 EDO608 Objects not successfully deleted.............:  "0"
    1 EDO607 Successfully deleted objects.................:  "128"
    1 EDO609 Tables/views with DROP/CREATE................:  "0"
    1 EDO610 No. of them marked for DROP/CREATE: "0"
    1 EDO611 Not marked for DROP/CREATE: "0"
    1 EDO620 Number of nametabs to be deleted.............:  "0"
    1 EDO622 Successfully deleted nametabs................:  "0"
    1 EDO621 Nametabs that were not successfully deleted..:  "0"
    1 ED0301X*************************************************************************
    1 ED0306       "Statistics on Activated and Deleted Objects"
    1 ED0322 End phase  "007" ***********************************************************
    1 ED0302X=========================================================================
    1 ED0314 Mass Activation
    1 ED0302 =========================================================================
    1 ED0327 Process..................: "defnsv1466_14_59636"
    1 ED0319 Return code..............: "8"
    1 ED0313 Phase 001..................: 00:00:13 (Take Over Switch-Dependent Objects)
    1 ED0314 Phase 002..................: < 1 sec. (Deletion of objects: 1th call)
    1 ED0314 Phase 003..................: 00:00:47 (Berechnung der Abhängigen:)
    1 ED0313 Phase 004..................: 00:15:00 (Object Activation)
    1 ED0314 Phase 005..................: < 1 sec. (Puffer Sync für Abhängige refTo ...)
    1 ED0314 Phase 006..................: < 1 sec. (Final log)
    1 ED0314 Phase 007..................: < 1 sec. (Statistics on Activated and ...)
    1 ED0309 Program runtime..........: "00:16:01"
    1 ED0305 Date, time...............: "01.08.2014", "09:23:55"
    1 ED0318 Program end==============================================================
    1 ETP155 ACTIVATION OF DD-OBJECTS
    1 ETP110 end date and time   : "20140801092355"
    1 ETP111 exit code           : "8"
    1 ETP199 ######################################
    4 EPU202XEND OF SECTION BEING ANALYZED END OF ACT_UPG =====================================================
    Please suggest.
    Regards,
    Alok

    Hi Divyanshu,
    thanks for your prompt reply,
    As per the error occurred, PTRV_UTIL_VPFPS_VPFPA_P is the table but when I check in SE16 its saying PTRV_UTIL_VPFPS_VPFPA_P not a table its a STRUCTURE
    In SE11 its saying "PTRV_UTIL_VPFPS_VPFPA_ "does not exist.Check name.
    Here it is not taking full name of table "PTRV_UTIL_VPFPS_VPFPA_P".
    Pl suggest.
    BR,
    Alok

  • EHPI install - Error in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_GRANT!

    I am trying to install EHPI and this is the error I am getting:
    Severe error(s) occured in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_GRANT!
    Last error code set: 1 error during parallel execution of processes, check 'SQLEXEGR.LOG' for details > 2 processes failed, check 'SCEXEC_G.*' for details
    This is what hte PTALGR02.LOG says:
    tp_exec_statement: GRANT ALL ON SAPSR3."FLEMP~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."FLIGHTB~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."FLIGHTM~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."FLIGHTP~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."FLIGHTS~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_QUEUE~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_QUEUE_DATA~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_QUEUE_LG_T~" TO SAPSR3SHD
    I guessed it's a ppermissions issue and I "gave SAPDBA and DBA roles to both the users SAPSR3 and SAPSR3SHD". But that didn't work.
    Any help is appreciated.

    Here is the SQLEXEGR.LOG:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ANALYSIS OF LOG FILE '/usr/sap/NWD/upg/EHPI/abap/log/PTALGR00.LOG'
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ANALYSIS OF LOG FILE '/usr/sap/NWD/upg/EHPI/abap/log/PTALGR01.LOG'
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ERROR: Found pattern "TPERR-" 2 times, but expected 0!
    Analyze the log file for further error messages or program abort.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ANALYSIS OF LOG FILE '/usr/sap/NWD/upg/EHPI/abap/log/PTALGR02.LOG'
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    This is the PTALGR02.LOG:
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_QUEUE_LG_T~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_QUEUE_LOG~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_SA_APPL~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTFT_SA_APPL_T~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTMCORREL~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTMEXTID~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTMLEXENT~" TO SAPSR3SHD
    tp_exec_statement: GRANT ALL ON SAPSR3."SRTMLEXICO~" TO SAPSR3SHD

  • NW 7 Install Error on Phase 43 of 47 (Start Instance) Dispatcher stopping

    Dear Experts,
    I'm trying to install NW 7 ABAP system on window server 2008 stand. I have been getting errors on this phase. I have tried installing it multiple times.
    When I look at the sapmmc console, dispatcher is stopping. When i looked at the work look, it is failing to communicate to its own IP. I was able to telnet to this machine and works fine. however, it is trying to connect on port 3302 which is failing and telnet is failing too. I have tried adding this port to firewall and disabled firewall but it does not solve it. Please help.
    Work Log Error:
    Thu Jul 08 13:34:53 2010
    ***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2770]
    ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1836
        (SI_ECONN_REFUSE/10061; I4; ST; 192.168.1.108:3302) [nixxi.cpp    2770]
    ERROR => GwIConnect: GwConnect to WIN-T3RJKF8RM0T / 3302 failed (rc=NIECONN_REFUSED) [gwxx.c       296]
    ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx.c       297]
    ***LOG S0R=> GwIConnect, GwConnect () [gwxx.c       299]
    ***LOG S0S=> GwIConnect, GwConnect (3302) [gwxx.c       301]
    ***LOG S90=> SAP_CMREGTP2, GwIConnect ( 236) [r3cpic.c     9624]
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner 'WIN-T3RJKF8RM0T:3302' not reached
    TIME        Thu Jul 08 13:34:53 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2770
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     168
    Your help is really appreciated!
    Thanks,
    Afi

    Hi,
    First of all what I can think of is your hostname is very long.
    For ABAP installation on window and oracle, maximum length is 12 characters. But in your case it is 15. Check SAP note 849423.
    If combination is not window and oracle, maximum length can be 13 characters. Check SAP note 611361.
    Please correct this and then  try.
    Thanks
    Sunny

  • Install Error in Phase 31

    Hi,
    I'm just trying to install ERP 2005. Its a Windows system and I use MaxDB.
    In Phase 31 I got this Error.
    ERROR 2008-04-01 16:59:14
    CJS-30105  Instance ABC/DVEBMGS03 reached state SHUTDOWN after having state STARTING. Giving up.
    ERROR 2008-04-01 16:59:14
    FCO-00011  The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|0|0|start was executed with status ERROR .
    Does anybody know how to solve this problem?
    thanks.

    check
    dev_disp
    dev_w0
    in the instance work directory for possible errors.
    Markus

  • Ce71 install error with phase for install java engine!!!!

    HI expert,
         I  encounter issues with install ce71, below is trace log info please help me ,thanks!!!!!!
    TRACE      2010-09-12 21:00:34.421
    FSPath(D:\usr\sap\EPD\J02\exe\jstart.exe) done
    WARNING    2010-09-12 21:00:34.421
               CJSlibModule::writeWarning_impl()
    Execution of the command "D:\usr\sap\EPD\J02\exe\jstart.exe pf=D:\usr\sap\EPD\SYS\profile\EPD_J02_g2s1-sap -file=D:\usr\sap\EPD\J02\exe\startup.properties -nodename=bootstrap -launch" finished with return code 1. Output:
    TRACE      2010-09-12 21:00:34.421
    FSPath(D:\usr\sap\EPD\J02\exe\jstart.exe) done
    TRACE      2010-09-12 21:00:34.421
    ChildApplication(D:\usr\sap\EPD\J02\exe\jstart.exe).run(): 1. done.
    TRACE      2010-09-12 21:00:34.421
    FSPath(D:\usr\sap\EPD\J02\exe\jstart.exe) done
    TRACE      2010-09-12 21:00:34.421
    NWException thrown: nw.processError:
    Process call 'D:\usr\sap\EPD\J02\exe\jstart.exe pf=D:\usr\sap\EPD\SYS\profile\EPD_J02_g2s1-sap -file=D:\usr\sap\EPD\J02\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J02.log.
    TRACE      2010-09-12 21:00:34.421
    Function setMessageIdOfExceptionMessage: nw.processError
    ERROR      2010-09-12 21:00:34.421
               CJSlibModule::writeError_impl()
    CJS-30023  Process call 'D:\usr\sap\EPD\J02\exe\jstart.exe pf=D:\usr\sap\EPD\SYS\profile\EPD_J02_g2s1-sap -file=D:\usr\sap\EPD\J02\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J02.log.
    TRACE      2010-09-12 21:00:34.421 [iaxxejsbas.hpp:488]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2010-09-12 21:00:34.468 [sixxcstepexecute.cpp:984]
    FCO-00011  The step runBootstrap with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|7|0|runBootstrap was executed with status ERROR ( Last error reported by the step :Process call 'D:\usr\sap\EPD\J02\exe\jstart.exe pf=D:\usr\sap\EPD\SYS\profile\EPD_J02_g2s1-sap -file=D:\usr\sap\EPD\J02\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J02.log.).
    TRACE      2010-09-12 21:00:34.500
    Instantiating new NWUsageTypeBasic
    TRACE      2010-09-12 21:00:34.500
    NWUsageTypeBasic() done
    TRACE      2010-09-12 21:00:34.500
      Call block:CallBackInCaseOfAnErrorDuringStepExecution
        function:CallTheLogInquirer
    is validator: true
    WARNING    2010-09-12 21:00:34.500 [iaxxejshlp.cpp:150]
    Could not get property IDs of the JavaScript object.
    ERROR      2010-09-12 21:00:34.500 [iaxxejsctl.cpp:492]
    FJS-00010  Could not get value for property .
    TRACE      2010-09-12 21:00:34.578
    A problem occurs during execution the inquirer callback. SAPinst will switch back to the standard behaiviour.
    TRACE      2010-09-12 21:00:34.578 [iaxxgenimp.cpp:707]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver CE Productive Edition > Installation Options > Standard System > Standard System( Last error reported by the step :Process call 'D:\usr\sap\EPD\J02\exe\jstart.exe pf=D:\usr\sap\EPD\SYS\profile\EPD_J02_g2s1-sap -file=D:\usr\sap\EPD\J02\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J02.log.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/CE71_PROD_ORA/INSTALL/STD/AS. </p> </body></html>
    TRACE      2010-09-12 21:00:34.578 [iaxxgenimp.cpp:1245]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    INFO       2010-09-12 21:01:00.296 [sixxcstepexecute.cpp:1064]
    An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|7|0|runBootstrap".

    Hi,
    The logs generated during installation will be written under the folder sapinst_instdir.
    Can you please check the logs in the path  C:\Program Files/sapinst_instdir/CE71_PROD_ORA/INSTALL/STD/AS and search for Errors in that.
    Please share that error message from that log file.
    Thanks

  • 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

  • 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

  • SAP NetWeaver 7.3 AS Java install error in Install Java Engine phase

    Hi All,
    I am doing my first installation of SAP NetWeaver 7.3 AS Java on Windows Server 2008 R2 with Oracle database 11.2.0.3, this is a domain installation.
    I have been following the SAP Installation guide and everything has been going well but I am now stuck with an error in the Install Java Engine phase of the installation.
    The error message I am receiving is:
    An error occurred while processing option SAP NetWeaver 7.3 > SAP Systems > Application Server Java > Standard System > Standard System( Last error reported by the step: Process call 'C:\usr\sap\E1D\J00\exe\jstart.exe pf=\\sourcing\sapmnt\E1D\SYS\profile\E1D_J00_sourcing -file=C:\usr\sap\E1D\J00\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J00.log.)
    When I check the jstart_bootstrap_J00.log it is empty.
    I have done some searching for a solution for this error and it seems it may be related to the database not running. I can confirm that I have run lsnrctl start and also, in sqlplus, run startup; both commands showed that the starting of the listener and database were successful.
    Does anyone know what might be causing this error?
    Many thanks
    Dan

    Hi Srikishan,
    In C:\Program Files\sapinst_instdir\NW73\INSTALL\NW73\ORA\STD the file jstart_bootstrap_J00.log is empty.
    In C:\usr\sap\E1D\J00\work there was no jstart_bootstrap_J00.log file, however there was a file called log_bootstrap.0.log, the contents are:
    <!--LOGHEADER[START]/-->
    <!--HELP[Manual modification of the header may cause parsing problem!]/-->
    <!--LOGGINGVERSION[2.0.7.1006]/-->
    <!--NAME[..\..\work\log_bootstrap.log]/-->
    <!--PATTERN[log_bootstrap.log]/-->
    <!--FORMATTER[com.sap.tc.logging.TraceFormatter([%24d] %m)]/-->
    <!--ENCODING[UTF8]/-->
    <!--FILESET[0, 3, 5242880]/-->
    <!--PREVIOUSFILE[log_bootstrap.2.log]/-->
    <!--NEXTFILE[log_bootstrap.1.log]/-->
    <!--LOGHEADER[END]/-->
    [Aug 22, 2012 12:11:10 PM] Starting to configure the bootstrap
    [Aug 22, 2012 12:11:10 PM]       Bootstrap properties file [C:\usr\sap\E1D\J00\j2ee\cluster\bootstrap\bootstrap.properties] found
    [Aug 22, 2012 12:11:10 PM] Bootstrap configured for [32] ms
    [Aug 22, 2012 12:11:10 PM]
    [Aug 22, 2012 12:11:10 PM] Memory available to the bootstrap JVM: [2 GiB / 3113877504 bytes]
    [Aug 22, 2012 12:11:10 PM]
    -----[Bootstrap Module started]--------[Wed Aug 22 12:11:10 BST 2012]-------
    [Aug 22, 2012 12:11:10 PM]
    +------------[Bootstrap synchronization activities information]-----------+
    | Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |
    |  Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |
    +-------------------------------------------------------------------------+
    [Aug 22, 2012 12:11:10 PM] Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, log[defaultTrace].pattern=..\..\work\log_bootstrap.log, log[consoleLog].formatter=formatter[ConsoleFormatter], com.sap.engine.bootstrap.severity=Info, formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, com.sap.engine.bootstrap.logs=log[defaultTrace],log[consoleLog], log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]
    [Aug 22, 2012 12:11:10 PM] Bootstrap initialized for [63] ms
    [Aug 22, 2012 12:11:10 PM] Watchdog [90000] ms checking every [2000] ms started
    [Aug 22, 2012 12:11:10 PM] Starting to initialize database connection
    [Aug 22, 2012 12:11:11 PM] Exception occurred for component [internal/unkown] of type [unkown]
    com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed.Check if the database is running and the database connection properties
        at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:138)
        at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
        at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
    ----------==[ Caused by: ]==----------
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:167)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)
        at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:138)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:307)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
        at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:131)
        at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
        at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
    Caused by: com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver with class loader com.sap.engine.offline.FileClassLoader@68814013.
        at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:210)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createVendorDriver(VendorConnectionFactory.java:43)
        at com.sap.sql.connect.factory.DriverPooledConnectionFactory.<init>(DriverPooledConnectionFactory.java:31)
        at com.sap.sql.connect.datasource.DataSourceManager.createPooledConnectionFactory(DataSourceManager.java:642)
        at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:603)
        at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:137)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.getDataSource(OpenSQLDataSourceImpl.java:272)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:208)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:399)
        ... 13 more
    Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
        at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:911)
        at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:802)
        at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:750)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:206)
        ... 21 more
    [Aug 22, 2012 12:11:11 PM] [Bootstrap]> Error during synchronization. More details: the previous log entries
    [Aug 22, 2012 12:12:29 PM] Starting to configure the bootstrap
    [Aug 22, 2012 12:12:29 PM]       Bootstrap properties file [C:\usr\sap\E1D\J00\j2ee\cluster\bootstrap\bootstrap.properties] found
    [Aug 22, 2012 12:12:29 PM] Bootstrap configured for [32] ms
    [Aug 22, 2012 12:12:29 PM]
    [Aug 22, 2012 12:12:29 PM] Memory available to the bootstrap JVM: [2 GiB / 3113877504 bytes]
    [Aug 22, 2012 12:12:29 PM]
    -----[Bootstrap Module started]--------[Wed Aug 22 12:12:29 BST 2012]-------
    [Aug 22, 2012 12:12:29 PM]
    +------------[Bootstrap synchronization activities information]-----------+
    | Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |
    |  Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |
    +-------------------------------------------------------------------------+
    [Aug 22, 2012 12:12:29 PM] Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, log[defaultTrace].pattern=..\..\work\log_bootstrap.log, log[consoleLog].formatter=formatter[ConsoleFormatter], com.sap.engine.bootstrap.severity=Info, formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, com.sap.engine.bootstrap.logs=log[defaultTrace],log[consoleLog], log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]
    [Aug 22, 2012 12:12:29 PM] Bootstrap initialized for [63] ms
    [Aug 22, 2012 12:12:29 PM] Watchdog [90000] ms checking every [2000] ms started
    [Aug 22, 2012 12:12:29 PM] Starting to initialize database connection
    [Aug 22, 2012 12:12:30 PM] Exception occurred for component [internal/unkown] of type [unkown]
    com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed.Check if the database is running and the database connection properties
        at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:138)
        at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
        at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
    ----------==[ Caused by: ]==----------
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:167)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)
        at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:138)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:307)
        at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
        at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:131)
        at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
        at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
    Caused by: com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver with class loader com.sap.engine.offline.FileClassLoader@38ee6681.
        at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:210)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createVendorDriver(VendorConnectionFactory.java:43)
        at com.sap.sql.connect.factory.DriverPooledConnectionFactory.<init>(DriverPooledConnectionFactory.java:31)
        at com.sap.sql.connect.datasource.DataSourceManager.createPooledConnectionFactory(DataSourceManager.java:642)
        at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:603)
        at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:137)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.getDataSource(OpenSQLDataSourceImpl.java:272)
        at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:208)
        at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:399)
        ... 13 more
    Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
        at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:911)
        at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:802)
        at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:750)
        at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:206)
        ... 21 more
    [Aug 22, 2012 12:12:30 PM] [Bootstrap]> Error during synchronization. More details: the previous log entries
    Many thanks
    Dan

  • ERP - EHP5 upgrade - error in phase Preprocessing - MAIN_SHDRUN/DDIC_UPG

    Dear SAP,
    I have started my upgrade from ERP EHP4 to EHP5.
    During phase PreProcessing - the phase MAIN_SHDRUN/DDIC_UPG fails for the following reason :
    In TP.SAV, I have this error :
    ERRORS: Highest tp internal error was: 0232
    TRACE-INFO: 32:  [     dev trc,00000]     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12537:                       58  0.045050
    TRACE-INFO: 35:  [    dbsloci.,00000]  *** ERROR => CONNECT failed with sql error '12537'                                 32  0.045096
    TRACE-INFO: 36:  [     dev trc,00000]     set_ocica() -> SQL error code 12537                                             15  0.045111
    TRACE-INFO: 38:  [     dev trc,00000]     OCIErrorGet -> SQL error code: 12537                                            51  0.045175
    TRACE-INFO: 41:  [     dev trc,00000]  SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12537.                               28  0.045221
    TRACE-INFO: 43:  [    dblink  ,00000]  ***LOG BY2=>sql error 12537  performing CON                                        60  0.045304
    ERRORS: Highest tp internal error was: 0232
    I have already changed the R3trans and tp executable.
    Any help is very welcome.
    Best regards
    SAP NetWeaver Admin

    Hi,
    The phase is stopped with the following error
    ERROR => CONNECT failed with sql error '12537'
    SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12537.
    ***LOG BY2=>sql error 12537  performing CON
    ***LOG BY0=>ORA-12537: TNS:connection closed
    1AETW000 ===> HALT: reconnect to DB failed Please contact the SAP support.
    4 ETW000 End of Transport (0016)
    This issue is caused by misconfigured parameters for Oracle. The main
    ones are the parameters: PROCESSES and SESSIONS.
    Please check SAPnote # 1431798 and correct/increase the parameters.
    then repeat the phase to proceed further with the upgrade.
    Thank You.
    Regards,
    Deepika

  • Error in Phase 44/44 installing SM 4.0 SR3 on Windows 2003 64 bit Oracle 10

    Hello All,
    this is my first post here and I'm having issue installing SM 4.0 SR3. It stops with an error  on Phase 44/44. here's the error log. I've tride searching for answer but no luck. can anybody please help?
    Solution Manager 4.0 SR3 64 bit Installation
    Windows 2003 R2 64 bit
    Oracle Database 10g
    Java 1.5.0_14 64 bit
    INFO 2008-01-17 11:34:22.483
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.8.xml'.
    INFO 2008-01-17 11:34:22.530
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.9.xml'.
    INFO 2008-01-17 11:34:24.124
    Execute step Component  W2K_ServicePack_Check|ind|ind|ind|indPreprocess  of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
    INFO 2008-01-17 11:34:38.108
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.5.xml'.
    INFO 2008-01-17 11:34:38.342
    Execute step callOfflineCTC of component |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0.
    INFO 2008-01-17 11:34:39.404
    Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\LaunchOfflinectc.bat.log.
    INFO 2008-01-17 11:34:39.436
    Working directory changed to E:/usr/sap/S20/DVEBMGS00/j2ee/ctc.
    INFO 2008-01-17 11:34:39.451
    Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS.
    INFO 2008-01-17 11:34:39.467
    Output of E:\usr\sap\S20\DVEBMGS00\j2ee\ctc\LaunchOfflinectc.bat is written to the logfile LaunchOfflinectc.bat.log.
    WARNING 2008-01-17 11:34:42.107
    Execution of the command "E:\usr\sap\S20\DVEBMGS00\j2ee\ctc\LaunchOfflinectc.bat" finished with return code 1. Output:         1 file(s) copied.java.io.BufferedInputStream@6686fe26Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Start Execution of Offline CTC TemplatInstallerJan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Looking for initial Properties in file '../../../config/usagetypes.properties'Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Loading of initial Properties-File successful Jan 17, 2008 11:34:39... ....tc.lm.ctc.OfflineTemplateImporterJAR [Thread[main,5,main]] Info: Selected Usages:SolManager:SolManager JavaPerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathJan 17, 2008 11:34:41... ...c.cul.cpi.exceptions.CPIBaseException [Thread[main,5,main]] Path: Exception : The proivder ConfigManagerProvider is not able to startupjava.lang.Exception     at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)     at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413)     at com.sap.exception.BaseException.<init>(BaseException.java:302)     at com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException.<init>(CPIBaseException.java:63)     at com.sap.tc.lm.ctc.provider.configurationmanager.exceptions.ConfigManagerProviderBaseException.<init>(ConfigManagerProviderBaseException.java:52)     at com.sap.tc.lm.ctc.provider.configurationmanager.offline.ConfigurationManagerOfflineStartup.createProvider(ConfigurationManagerOfflineStartup.java:59)     at com.sap.tc.lm.ctc.cul.offline.OfflineCTCFramework.startupSystem(OfflineCTCFramework.java:69)     at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.executeWizard(OfflineTemplateImporterJAR.java:113)     at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.main(OfflineTemplateImporterJAR.java:549)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:585)     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)     at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)     at com.sap.tc.lm.ctc.provider.configurationmanager.offline.ConfigurationManagerOfflineStartup.createProvider(ConfigurationManagerOfflineStartup.java:57)     at com.sap.tc.lm.ctc.cul.offline.OfflineCTCFramework.startupSystem(OfflineCTCFramework.java:69)     at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.executeWizard(OfflineTemplateImporterJAR.java:113)     at com.sap.tc.lm.ctc.OfflineTemplateImporterJAR.main(OfflineTemplateImporterJAR.java:549)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:585)     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)     at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)     at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)     ... 14 more
    ERROR 2008-01-17 11:34:42.139
    CJS-00030  Assertion failed: in function NW_Call_Offline_CTC_ind_ind_ind_ind_SubComponentContainer_callOfflineCTC() {    var nw = NWInstall.getSystem(context.get("sid"));    var ctcDirFs = nw.getCI().getInstanceDir().concat("j2ee", "ctc");    var ctcExeFile = installer.onWindows() ? "LaunchOfflinectc.bat" : "LaunchOfflinectc.sh";    var ctcCall = ctcDirFs.concat(ctcExeFile);    installer.writeTrace("CTC is in" + ctcCall);    ASSERT(arguments.callee, ctcCall.isExisting(), "CTC executable cannot be found in " + ctcCall.toString());    var pmgt = new ProcessMgt();    var app = pmgt.createChildApplication(ctcCall, []);    var userData = nw.getUsers().getAccountData(NWUsers.roles.SIDAdm);    var user = (new AccountMgt()).getUser(userData.name);    var env = pmgt.getProcessEnvironment();    if (installer.onUnix()) {        env.setUser(user);    }    env.setWorkingDirectory(ctcDirFs.getNode());    env.setEnvironmentVariable(new Property("JAVA_HOME", nw.getJavaHome().toString()));    installer.writeTrace("For the Offline CTC Call, JAVA_HOME is set to " + env.getEnvironmentVariable("JAVA_HOME"));    app.setEnvironment(env);    var retval = app.run([], true);    ASSERT(arguments.callee, retval == 0, "CTC retval is not 0 but " + retval);    installer.writeTrace("CTC has been called in Offline Mode.");}CTC retval is not 0 but 1
    ERROR 2008-01-17 11:34:42.217
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2008-01-17 11:34:42.264
    FCO-00011  The step callOfflineCTC with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|callOfflineCTC was executed with status ERROR .

    Uninstall Java 1.5 - it will not work.
    You MUST use Java 1.4 for 64bit windows from note 941595 - Download J2SE 1.4.2 for the x64 platform
    I suggest you start over with your installation since the wrong path is in quite a few locations.
    Markus

  • Phase MAIN_SHDRUN/ACT_UPG - SAPA741EPU

    Hi,
    I am making an upgrade from ERP 6.0 EhP 5 to ERP 6.0 EhP 7
    I am facing an error message during phase MAIN_SHDRUN/ACT_UPG.
    The ACTUPG.ELG log file Looks like this:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DDIC ACTIVATION ERRORS and RETURN CODE in SAPA741EPU.<SID>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1EEDO516X"Index" "CRMD_PARTNER" "HIL" could not be activated
       3 EDT014XActivate dependent table "COMT_PCAT_HDR_0010"
       2WEDT192 Enhancement category for table missing
       2WEDT193 Enhancement category for include or subtype missing
       3 EDT199 Exactly one field "LANGU" of type LANG: Selection as text language possible
       2WEAD285 Check table "CRMD_KW_TEMPL" does not exist or has no key fields
       2WEAD285 Check table "CRMD_KW_TEMPL" does not exist or has no key fields
       1EEDT352 Search field "COMT_PCAT_HDR_0010"-"BASE_LOC_ID" of search help attachment: search help "COM_PCAT_LOC_ID_NAME" not active
       3 EDT015 Dependent table "COMT_PCAT_HDR_0010" was not activated
    1EEDO519 "Table" "COMT_PCAT_HDR_0010" could not be activated
    1 ETP111 exit code           : "8"
    The error looks quite similar to what is described in MAIN_SHDRUN/ACT_UPG error (solution -> SAP Note1909524 )
    I am not quite sure if I should apply the solution "Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG".
    Kind regards,
    Niklas

    Hi Niklas,
    Above tables and index are related to CRM. As your environment is ECC you may accept to ignore the non-severe errors and proceed with the upgrade.
    Hope this helps.
    Regards,
    Deepak Kori

  • Phase MAIN_SHDRUN/ACT_UPG hanging?

    <h5>
    I am upgrading from NW 7.0 Enhancement Package 1 (7.01) using SAPEhpi. The SAPEhpi tools shows that the ABAP progress has status RUNNING 'Executing phase MAIN_SHDRUN/ACT_UPG', and J2EE progress has status WAITING 'Waiting for synchronization event PREPUPTIME=FINISHED'. The status has been the same for the last three days. I understand that long run times are not unusual for this phase, but I have my doubts due to the below circumstances.
    <h5>
    The shadow instance and standard instance is installed on the same server. I got lots of activation errors '8' in phase MAIN_SHDRUN/ACT_UPG as seen from Filepath:...\EHPI\abap\log\SAPehpiConsole.log
    <h5>
    Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
    <h5>
    Last error code set: Process 'tp.exe' exited with 8, see
    'C:\SAP_Download\EHPI\abap\tmp\MSGOUT.LOG' for details Check logfiles
    'ACTUPG.ELG' and 'C:\SAP_Download\EHPI\abap\log\SAPehpi.ECO'
    01)  -  Repeat phase ACT_UPG to continue at the point it stopped
    02)  *  Initialize phase ACT_UPG to restart it from the beginning
    03)  -  Accept non-severe errors and repeat phase ACT_UPG
    04)  -  Exit this program
    Choose action: Initialize phase ACT_UPG to restart it from the beginning
    <h5>
    >> 2009/11/21 05:20:35  START OF PHASE MAIN_SHDRUN/ACT_UPG
    <h5>
    running C:\SAP_Download\EHPI\abap\exe\tp.exe pf=C:\SAP_Download\EHPI\abap\bin\SHADOW.TPP checkimpdp AII
    Collecting adjustments ...
    <h5>
    <h5>
    But before i initialized the phase ACT_UPG I realised that the shadow instance was unable to connect to the message server. The disp+work was yellow with message 'could not connect to message server'. The DEFAULT.PFL profile for the shadow instance showed the following parameter for the message server: rdisp/msserv = 3607. So I changed the DEFAULT.PFL of the shadow instance to point to the message server of the standard instance. The standard instance nr. = 5, while the shadow instance nr. = 7.
    <h5>
    rdisp/mshost = turin-1
    <h5>
    rdisp/msserv = sapmsAII
    <h5>
    rdisp/msserv_internal = 3905
    <h5>
    I restarted the shadow instance using SAPMMC for Windows and the message server was then green. I chose to Initialize phase ACT_UPG as option 02)  *  Initialize phase ACT_UPG to restart it from the beginning.
    <h5>
    After this decision I can not see any entries in any logs in EHPI directories except the below log. No action for 3 days now, still waiting.....I can log on to the shadow instance using DDIC user but for other users I get message that 'Upgrade still running: Logon not possible'.
    <h5>
    Any ideas? How can I really determine if the upgrade is still running?
    <h5>
    Filepath:...\EHPI\sdt\trc\server.trc
    <h5>
    Nov 24, 2009 1:33:23 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:101) [Thread[ExecuteWorker,5,main]]: Execution of command com.sap.sdt.engine.core.communication.CmdActionEvent@71475e19 failed: null
    Nov 24, 2009 1:33:23 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: null
    Nov 24, 2009 1:33:23 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: null
    Nov 24, 2009 1:33:23 AM [Error]:                                                 com.sap.sdt.engine.core.communication.CmdActionEvent [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException
         at com.sap.sdt.engine.core.admin.AbstractServerAdmin.getClientConnection(AbstractServerAdmin.java:192)
         at com.sap.sdt.server.core.controls.ServerControlFactory.getConsumer(ServerControlFactory.java:102)
         at com.sap.sdt.server.core.controls.ServerControlFactory.register(ServerControlFactory.java:83)
         at com.sap.sdt.server.core.controls.SDTControlFactory.createFrame(SDTControlFactory.java:114)
         at com.sap.sdt.server.core.controls.SDTFrame.createDelegate(SDTFrame.java:119)
         at com.sap.sdt.server.core.controls.SDTBase.getDelegate(SDTBase.java:127)
         at com.sap.sdt.server.core.controls.SDTFrame.<init>(SDTFrame.java:41)
         at com.sap.sdt.server.core.admin.SDTServerAdmin.getFrame(SDTServerAdmin.java:358)
         at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.showBreakPointScreen(AbstractUpgradeViewManager.java:622)
         at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.actionBreak(AbstractUpgradeViewManager.java:417)
         at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.performMenuAction(AbstractUpgradeViewManager.java:160)
         at com.sap.sdt.dsu.service.controls.DSUToolListener.actionPerformed(DSUToolListener.java:48)
         at com.sap.sdt.server.core.controls.SDTActionListener$Listener.actionPerformed(SDTActionListener.java:49)
         at com.sap.sdt.engine.core.communication.CmdActionEvent.actOnEvent(CmdActionEvent.java:38)
         at com.sap.sdt.engine.core.communication.CmdEvent.execute(CmdEvent.java:54)
         at com.sap.sdt.engine.core.communication.ExecWorker.handleCmd(ExecWorker.java:48)
         at com.sap.sdt.engine.core.communication.AbstractWorker.run(AbstractWorker.java:85)

    <h5>
    I was able to continue the upgrade by resetting the DEFAULT.PDF profile with original message server: rdisp/msserv = 3607 information, and restart the shadow instance.
    <h5>
    Had to follow other forum advice and disregard activation errors in ACT_UPG phase.
    <h5>
    But the shadow instance disp+work is still not able to connect to the message server, even if I can see that the message server is running green for the shadow instance. There must be something wrong with the parameters in the DEFAULT.PDF profile. Can someone please post an example for a DEFAULT.PDF profile so that I can compare the content?
    <h5>
    Hopefully I will not get stuck later in the upgrade process?

Maybe you are looking for

  • HT203353 Safari app on my MAC is not opening AT ALL? What should i do?

    Safari app on my MAC is not opening after the lat updates. at the beginning is started acting funny than crashed and refused to open again. There is always a window opens automatically each time i try to open Safari and i have no idea what is trying

  • ASSIGN  TO betrag could not be performed (system error)

    Hi Gurus, Can anybody let me know when we will get the above said Subject error. I had encountered it in MIGO GR transaction. Iam pasting the total text of the error below ASSIGN  TO <betrag> could not be performed (system error)     Message no. M710

  • Help menu function plz help:)))

    Hello there. I've been trying to design a GUI providing the users with help function as well. I create the html file, map file(in .jhm format) and HelpSet (in .hs format) and run the help menu via hsviewer. The first problem is that when the hsviewer

  • Mass changes in routing

    HI, I need to add one more operation in the existing routings, every routing is mutiple routing and addtion to be made in all the headers. Can we do this using CA85N or should we have to user BDC or is there any other method available. Regards, Jag

  • [svn:osmf:] 11045: Increasing timer interval in attempt to fix unit test on the build server.

    Revision: 11045 Author:   [email protected] Date:     2009-10-21 02:32:45 -0700 (Wed, 21 Oct 2009) Log Message: Increasing timer interval in attempt to fix unit test on the build server. Modified Paths:     osmf/trunk/framework/MediaFrameworkFlexTest