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 > 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,
Similar Messages
-
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 meHi,
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 -
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
AlexeyHi
I am getting error in MSSSPEXE job in Preprocessing phase in Ehp6 upgrade.
MAIN_SHDPREPUT/JOB_MSSSPEXE_SHD_PRE
MSSSPEXE job aborted
Batchjob 'MSSSPEXE' with id '11484300' aborted
Reviewing Short dump is says the following:
Runtime Errors SYNTAX_ERROR
Date and Time 03.11.2013 00:47:55
Short Text
Syntax error in program "SAPLMSSPROCS ".
What happened?
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLMSSPROCS " in inclu
"LMSSPROCSUXX " in
line 9:
"INCLUDE report "LMSSPROCSU04" not found"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Runtime Errors SYNTAX_ERROR
Date and Time 03.11.2013 00:47:55
Short Text
Syntax error in program "SAPLMSSPROCS ".
What happened?
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLMSSPROCS " in inclu
"LMSSPROCSUXX " in
line 9:
"INCLUDE report "LMSSPROCSU04" not found"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "MSSSPEXE" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Regards -
Error at PHASE SHD_FIX_IMP in R/3 upgrade.
Hi,
i am getting the below error:
UPGRADE/SHADOW: END OF PHASE SHD_FIX_IMP
>> 13:00:28 UPGRADE/SHADOW: START OF PHASE SHD_FIX_IMP
running C:\usr\sap\put\exe\tp.exe pf=C:\usr\sap\put\bin\SHD_FIX.TPP put DEV
tp terminated successfully.
analyzing result of tp call ...
ERROR: 6 errors detected during SHD_FIX_IMP.
Analyze summary error logfile SHD_FIX.ELG
and remove all error conditions in the way
it is described in the upgrade manual. Repeat
this phase until it is error free.
Additional hints may be given in logfiles
SLOG640 and C:\usr\sap\put\log\R3up.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CUSTOMER MAIN IMPORT ERRORS and RETURN CODE in B20I8A2NLM.DEV
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 Probably the data file was destroyed during file transfer!?
2EETW000 Probably the data file was destroyed during file transfer!?
2EETW000 Probably the data file was destroyed during file transfer!?
1 ETP111 exit code : "8"
C:\usr\sap\put\exe\R3trans.exe finished (0000).
Syslog: k CPG : &0000&C&0000& rscploc 9Syslog: k CP3 : 0000&TCPDB& rscpmi 1This is C:\usr\sap\put\exe\R3trans.exe version 6.09 (release 640 - 05.04.04 - 14:45:00).
C:\usr\sap\put\exe\R3trans.exe finished (0004).
Syslog: k CPG : &0000&C&0000& rscploc 9Syslog: k CP3 : 0000&TCPDB& rscpmi 1This is C:\usr\sap\put\exe\R3trans.exe version 6.09 (release 640 - 05.04.04 - 14:45:00).
2EETW000 Probably the data file was destroyed during file transfer!?
2EETW000 Probably the data file was destroyed during file transfer!?
2EETW000 Probably the data file was destroyed during file transfer!?
C:\usr\sap\put\exe\R3trans.exe finished (0008).
stopping on error 8 during MAIN IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 8
meaning:
A tool used by tp produced errors
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 8 during MAIN IMPORT
Process with ID 3528 terminated with status 8
Deleting file C:\usr\sap\put\log\SHD_FIX.ELG
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B20I8A1JJN.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B20I8A2NLM.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009743.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009755.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009759.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009760.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B4AI009780.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\B6AI005685.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\F8HI900010.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\RS6I900005.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI012127.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI022467.DEV
Moving file C:\usr\sap\put\log\PROT.TMP to C:\usr\sap\put\log\Y6DI042418.DEV
Moving file C:\usr\sap\put\log\SHD_FIX.ELG to C:\usr\sap\put\tmp\SHD_FIX.ELG
Deleting file C:\usr\sap\put\tmp\MSGIN.LST
Deleting file C:\usr\sap\put\tmp\MSGOUT.LST
Deleting file C:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file C:\usr\sap\put\tmp\SHD_FIX.ELGHello,
When you get this problem first thing down load the latest R3trans
then "uncar". Copy the uncar file into "/usr/sap/put/exe" after that
repet this phase again. After few seconds you get the error again then you do one thing Go to "/usr/sap/<SID>/SYS/exe/run" copy the all files resides in run directory and paste in "/usr/sap/put/exe"
then again repet the phase you get good output.
Thanks & Regards,
Sumanbabu.B -
Error at Phase SHDINST_OS in 4.71 upgrade
Hi,
I am getting the below error. i created a service SAPDEV_01 by using the below give syntax, it was created but when i am trying to start that service(SAPDEV_01) i am getting an error called " cannot start the service in the local computer. error1069: service could not start due to logon failure." so please help me in solving below error:
START OF PHASE SHDINST_OS
An error occurred during the installation of the
SAP service SAPDEV_01:
Possibly the password for user .\SAPServiceDEV entered in phase
INITPUT was wrong. You can reset it by calling 'R3up set stdpar'.
Try to execute SAPSTARTSRV.EXE manually using the following syntax:
C:\usr\sap\put\exe\sapstartsrv.exe -r
-p C:\usr\sap\put\DEV\SYS\profile\START_DVEBMGS01_home1 -s DEV -n 01
-U .\SAPServiceDEV -P <PASSWORD> -e HOME1\devadm
and check if the service SAPDEV_01 can be stopped and restarted.this post is duplciated at Re: Error at Phase SHDINST_OS in 4.71 upgrade
-
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,
AlokHi 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 -
Error at PHASE LOADCRE_TMP in 4.71 upgrade
hi
i am getting the below error in R/3 Upgrade:
UPGRADE/SWITCH: START OF PHASE LOADCRE_TMP
working ...
Creating empty ABAP load tables
ERROR: 1 error messages found in LOADCRT.ELG.
Analyze the log (refer to the upgrade
guide and the notes) and remove the problem(s)
that caused the error(s). After that,
repeat this phase until it is error free.
LOADCRT.ELG:
LOADCRE ERROR:, log file "EX000020.DPR": only 0 times "R3load.exe: job completed" found.
Analyze the log file EX000020.DPR for error messages or program abort.
EX000020.DPR:
C:\usr\sap\put\exe\R3load.exe: START OF LOG: 20090323182824
C:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_LO_REL/src/R3ld/R3load/R3ldmain.c#1 $ SAP
C:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4
C:\usr\sap\put\exe\R3load.exe -i C:\usr\sap\put\exchange\compack\EX000020.COD -p C:\usr\sap\put\log\EX000020.DPR -s C:\usr\sap\put\log\EX000020.DST -o d -datacodepage 1100 -dbcodepage auto
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: CO2MAP dropped
(DB) INFO: CO2MAP created
(DB) ERROR: DDL statement failed
(DROP INDEX "CO2MAP~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: CO2MAP~0 created
(DB) ERROR: DDL statement failed
(DROP INDEX "CO2MAP~IDX")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: CO2MAP~IDX created
(DB) INFO: CO2MAPINF dropped
(DB) INFO: CO2MAPINF created
(DB) ERROR: DDL statement failed
(DROP INDEX "CO2MAPINF~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: CO2MAPINF~0 created
(DB) INFO: DDFTX dropped
(DB) INFO: DDFTX created
(DB) ERROR: DDL statement failed
(DROP INDEX "DDFTX~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DDFTX~0 created
(DB) ERROR: DDL statement failed
(DROP INDEX "DDFTX~1")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DDFTX~1 created
(DB) INFO: DYNPLOAD dropped
(DB) INFO: DYNPLOAD created
(DB) ERROR: DDL statement failed
(DROP INDEX "DYNPLOAD~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DYNPLOAD~0 created
(DB) INFO: DYNPTXTLD dropped
(DB) INFO: DYNPTXTLD created
(DB) ERROR: DDL statement failed
(DROP INDEX "DYNPTXTLD~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: DYNPTXTLD~0 created
(DB) INFO: O2PAGINC dropped
(DB) INFO: O2PAGINC created
(DB) ERROR: DDL statement failed
(DROP INDEX "O2PAGINC~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: O2PAGINC~0 created
(DB) INFO: O2PAGRT dropped
(DB) INFO: O2PAGRT created
(DB) ERROR: DDL statement failed
(DROP INDEX "O2PAGRT~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: O2PAGRT~0 created
(DB) INFO: REPOLOAD dropped
(DB) INFO: REPOLOAD created
(DB) ERROR: DDL statement failed
(DROP INDEX "REPOLOAD~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: REPOLOAD~0 created
(DB) INFO: D010LINF dropped
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "D010LINF" ( "PROG" , "R3STATE" , "MACH" , "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJOR_VERS" ) AS SELECT T0001."PROGNAME", T0001."R3STATE", T0001."MACH", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."L_DATALG", T0001."Q_DATALG", T0001."SDAT", T0001."STIME", T0001."MINOR_VERS", T0001."MAJOR_VERS" FROM "REPOLOAD" T0001)
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) INFO: TCVIEW_P dropped
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "TCVIEW_P" ( "MANDANT" , "TCPROGRAM" , "TCCONTROL" , "DNUM" ) AS SELECT T0001."MANDANT", T0001."TCPROGRAM", T0001."TCCONTROL", T0002."DYNPNUMBER" FROM "TCVIEW" T0001, "DYNPLOAD" T0002 WHERE T0001."TCPROGRAM" = T0002."PROGNAME")
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) INFO: disconnected from DB
C:\usr\sap\put\exe\R3load.exe: job finished with 2 error(s)
C:\usr\sap\put\exe\R3load.exe: END OF LOG: 20090323182833
C:\usr\sap\put\exe\R3load.exe: START OF LOG: 20090323183205
C:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_LO_REL/src/R3ld/R3load/R3ldmain.c#1 $ SAP
C:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4
C:\usr\sap\put\exe\R3load.exe -i C:\usr\sap\put\exchange\compack\EX000020.COD -p C:\usr\sap\put\log\EX000020.DPR -s C:\usr\sap\put\log\EX000020.DST -o d -datacodepage 1100 -dbcodepage auto
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP VIEW "D010LINF")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "D010LINF" ( "PROG" , "R3STATE" , "MACH" , "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJOR_VERS" ) AS SELECT T0001."PROGNAME", T0001."R3STATE", T0001."MACH", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."L_DATALG", T0001."Q_DATALG", T0001."SDAT", T0001."STIME", T0001."MINOR_VERS", T0001."MAJOR_VERS" FROM "REPOLOAD" T0001)
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) ERROR: DDL statement failed
(DROP VIEW "TCVIEW_P")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "TCVIEW_P" ( "MANDANT" , "TCPROGRAM" , "TCCONTROL" , "DNUM" ) AS SELECT T0001."MANDANT", T0001."TCPROGRAM", T0001."TCCONTROL", T0002."DYNPNUMBER" FROM "TCVIEW" T0001, "DYNPLOAD" T0002 WHERE T0001."TCPROGRAM" = T0002."PROGNAME")
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) INFO: disconnected from DB
C:\usr\sap\put\exe\R3load.exe: job finished with 2 error(s)
C:\usr\sap\put\exe\R3load.exe: END OF LOG: 20090323183205
C:\usr\sap\put\exe\R3load.exe: START OF LOG: 20090323184248
C:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_LO_REL/src/R3ld/R3load/R3ldmain.c#1 $ SAP
C:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4
C:\usr\sap\put\exe\R3load.exe -i C:\usr\sap\put\exchange\compack\EX000020.COD -p C:\usr\sap\put\log\EX000020.DPR -s C:\usr\sap\put\log\EX000020.DST -o d -datacodepage 1100 -dbcodepage auto
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP VIEW "D010LINF")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "D010LINF" ( "PROG" , "R3STATE" , "MACH" , "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJOR_VERS" ) AS SELECT T0001."PROGNAME", T0001."R3STATE", T0001."MACH", T0001."UNAM", T0001."UDAT", T0001."UTIME", T0001."L_DATALG", T0001."Q_DATALG", T0001."SDAT", T0001."STIME", T0001."MINOR_VERS", T0001."MAJOR_VERS" FROM "REPOLOAD" T0001)
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) ERROR: DDL statement failed
(DROP VIEW "TCVIEW_P")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-1031 occured when executing SQL statement (parse error offset = 12)
(DB) ERROR: DDL statement failed
(CREATE VIEW "TCVIEW_P" ( "MANDANT" , "TCPROGRAM" , "TCCONTROL" , "DNUM" ) AS SELECT T0001."MANDANT", T0001."TCPROGRAM", T0001."TCCONTROL", T0002."DYNPNUMBER" FROM "TCVIEW" T0001, "DYNPLOAD" T0002 WHERE T0001."TCPROGRAM" = T0002."PROGNAME")
DbSlExecute: rc = 99
(SQL error 1031)
error message returned by DbSl:
ORA-01031: insufficient privileges
(DB) INFO: disconnected from DB
C:\usr\sap\put\exe\R3load.exe: job finished with 2 error(s)
C:\usr\sap\put\exe\R3load.exe: END OF LOG: 20090323184248ORA-01031: insufficient privileges
In most cases, the user receiving this error lacks a privilege to create an object (such as a table, view, procedure and the like). Grant the required privilege like so:
grant create table to user_lacking_privilege;
To add a user to the ora_dba group on Windows, net localgroup should help:
Startup
If someone receives this error while trying to startup the instance, the logged on user must belong to the ora_dba group on Windows. To add a user to the ora_dba group on Windows, net localgroup should help:
C:\> net localgroup ora_dba rene /add
Keep repeating this phase until the are errors are not minimised further. "failed DROP attempt is not necessarily a problem", and maybe you can ignore and continue the next phase. (check out)
Edited by: Shaji Jacob on Mar 24, 2008 7:27 AM -
Error at PHASE INTCHK_IMP in 4.71 upgrade
hi,
i am getting below error in 4.7 to ecc5 upgrade:
PREPARE: START OF PHASE INTCHK_IMP
running C:\usr\sap\DEV\SYS\exe\run\tp.exe pf=C:\usr\sap\put\bin\DEFAULT.TPP getddxttent DEV
running C:\usr\sap\DEV\SYS\exe\run\tp.exe pf=C:\usr\sap\put\bin\DEFAULT.TPP getddxtfent DEV
ERROR: 3 entries found in DDXTT.
All entries are listed in C:\usr\sap\put\log\DDXTTCHK.LOG.
ERROR: 52 entries found in DDXTF.
All entries are listed in C:\usr\sap\put\log\DDXTFCHK.LOG.
The entries in DDXTT and DDXTF have to be processed NOW.
Proceed as described in the upgrade manual.
LOG FILES:
DDXTTCHK.LOG:
DDXTT ENTRY /SDF/UMOD_COMP V
DDXTT ENTRY V_DDCPRO V
DDXTT ENTRY V_PAD_PATS V
DDXTFCHK.LOG:
DDXTF ENTRY /SDF/UMOD_COMP 0001
DDXTF ENTRY /SDF/UMOD_COMP 0002
DDXTF ENTRY /SDF/UMOD_COMP 0003
DDXTF ENTRY /SDF/UMOD_COMP 0004
DDXTF ENTRY /SDF/UMOD_COMP 0005
DDXTF ENTRY /SDF/UMOD_COMP 0006
DDXTF ENTRY /SDF/UMOD_COMP 0007
DDXTF ENTRY /SDF/UMOD_COMP 0008
DDXTF ENTRY /SDF/UMOD_COMP 0009
DDXTF ENTRY /SDF/UMOD_COMP 0010
DDXTF ENTRY /SDF/UMOD_COMP 0011
DDXTF ENTRY /SDF/UMOD_COMP 0012
DDXTF ENTRY /SDF/UMOD_COMP 0013
DDXTF ENTRY /SDF/UMOD_COMP 0014
DDXTF ENTRY /SDF/UMOD_COMP 0015
DDXTF ENTRY V_DDCPRO 0001
DDXTF ENTRY V_DDCPRO 0002
DDXTF ENTRY V_DDCPRO 0003
DDXTF ENTRY V_DDCPRO 0004
DDXTF ENTRY V_DDCPRO 0005
DDXTF ENTRY V_DDCPRO 0006
DDXTF ENTRY V_DDCPRO 0007
DDXTF ENTRY V_DDCPRO 0008
DDXTF ENTRY V_DDCPRO 0009
DDXTF ENTRY V_DDCPRO 0010
DDXTF ENTRY V_PAD_PATS 0001
DDXTF ENTRY V_PAD_PATS 0002
DDXTF ENTRY V_PAD_PATS 0003
DDXTF ENTRY V_PAD_PATS 0004
DDXTF ENTRY V_PAD_PATS 0005
DDXTF ENTRY V_PAD_PATS 0006
DDXTF ENTRY V_PAD_PATS 0007
DDXTF ENTRY V_PAD_PATS 0008
DDXTF ENTRY V_PAD_PATS 0009
DDXTF ENTRY V_PAD_PATS 0010
DDXTF ENTRY V_PAD_PATS 0011
DDXTF ENTRY V_PAD_PATS 0012
DDXTF ENTRY V_PAD_PATS 0013
DDXTF ENTRY V_PAD_PATS 0014
DDXTF ENTRY V_PAD_PATS 0015
DDXTF ENTRY V_PAD_PATS 0016
DDXTF ENTRY V_PAD_PATS 0017
DDXTF ENTRY V_PAD_PATS 0018
DDXTF ENTRY V_PAD_PATS 0019
DDXTF ENTRY V_PAD_PATS 0020
DDXTF ENTRY V_PAD_PATS 0021
DDXTF ENTRY V_PAD_PATS 0022
DDXTF ENTRY V_PAD_PATS 0023
DDXTF ENTRY V_PAD_PATS 0024
DDXTF ENTRY V_PAD_PATS 0025
DDXTF ENTRY V_PAD_PATS 0026
DDXTF ENTRY V_PAD_PATS 0027Hi,
Normally this error comes when you have incorrect entries created when you import Support Packages.
You can go thru the SAP Note 857276 which basically deals with a similar sort of a problem caused due to import of BI Content Support pack.
I had come across this error during my TEST upgrade and i had deleted the entries from the table and gone ahead. But do remember to take a backup of the tables before deleting the entries.
Also you can refer to the followink link
[DDXTF entries;
In case errors still exist, do reply back.
Regards,
Suhas -
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,
JuliaAfter 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 RamagowniHi 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 -
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 AdminHi,
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 -
EHP4 for ERP 6.0 upgrade phase MAIN_SHDRUN/DDIC_UPG running takes long time
Dear all,
I just tried to upgrade a fresh ERP 6.0 EHP4 ready (Linux X86_64 - Oracle) to EHP4 ERP 6.0.
I go through phase MAIN_SHDRUN/DDIC_UPG running, but it takes a very long times.
I checked the server resources usage, it 's very low.
I checked on my ERP 6.0 system and also the shadow system (background job, SM50), it seems no activities on both).
MAIN_SHDRUN/DDIC_UPG running - what is this phase about?
Its normal for this phase to takes about several hours??
What should i check to ensure that the upgrade process is still running?
How can i estimate time needed for this EHP4 upgrade?
I installed that freshERP 6.0 EHP4 ready system only on around 3-4 hours.
Regards,
Fendhy.Dear All,
I have same issue in ERP 6.0, EHP4 update, "MAIN_SHDRUN/DDIC_UPG" phase is still running, 24 hours passed. (only for this phase)
This is a NEW installation and on Production. I had no issues with DEV and QA and has taken only 50 minutes for the same phase.
Everything is same between DEV and PRD except, Production is on AIX HACMP cluster and using latest Ehpi installer + latest SPAM - version 41.
- There is no any error or warnings in /usr/sap/SID/EHPI/abap/log directory
- Phase is running, writing and reading files to installation directory
- No any automatic cluster fail-over mechanisms enabled
- Cluster has two nodes, DB+ASCS on one node and CI on other node.
- Shadow instance is running, can login, no errors in sm21, st22, no any running or canceled background jobs
- I can see 15% to 35% CPU "waits" in CI node where ehpi is running, but 50% of CPU is idle
- Also on same CI node, 70% to 100% disk busy waits can be seen on disks which mounted Ehpi installation directory
- On DB node CPU utilization and disk utilization is low
What could be the reason? Any idea ? How to diagnose.
Thanks,
P.D -
Error in phase XPRAS_AIMMRG for Upgrade from 4.7 to ERP6 ehp5 sps5
Hi All,
We are in process in upgrading our sandbox system from 4.7 to ERP6.0
EHP5 SPS5.
During the downtime step we are facing an error in phase XPRAS_AIMMRG
Upon investigation we found that there are short dumps in the system
due to this error.
Below is the extract of the short dumps generated by the job RDDEXECL
Category Internal Kernel Error
Runtime Errors DDIC_TYPE_INCONSISTENCY
Application Component BC-ABA-LA
Date and Time 05.12.2011 08:58:48
Short text
Inconsistency in the dictionary for the structure "KOMG".
What happened?
Error in the SAP kernel.
The current ABAP "SAPLF82V" program had to be terminated because
the
ABAP processor detected an internal system error.
Also, We I try to check the Table KOMG in SE11 is get the below messages.
Check table KOMG (DDIC/05.12.11/10:00)
Append structure OILKOMG appended to table KOMG
Append structure OIUKOMG appended to table KOMG
No customer or SAP include SI_KOMK_CM exists
No customer or SAP include SI_KOMP_CM exists
No customer or SAP include CI_PRS_CPILS_2 exists
Enhancement category 3 possible, but include or subty. not
yet classified
Field LGORT in table KOMG is specified twice. Please check
KOMG-ZZMVGR4: Table TVM1T in search help attachment differs
from table of search field
Check on table KOMG resulted in errors
Has anyone received the below message in XPRAS phase during the upggrade.
Any suggestion would be most welcome.
Regards,
Nilesh JagtapDear Nilesh,
The reason for this issue is that the component 'LGORT' is indeed specified twice in structure KOMG on your system.
It might be definied in the standard include as well as in your customer include.
Please bear in mind, that if you append customer own structures to SAP standad structures, that the component names should start with 'Z' or even better 'ZZ'.
That prevents the case which might have happened here, that the field you have added on customer side has also been delivered as part of an SAP standard include.
So you should change your structure accordingly.
Note 531835 describes how to add an own field to such structures. It might also be helpful for you.
After you have repaired your structure you can activate the structure KOMG and the issue should be solved.
Best Regards,
Abhishek -
Hello,
We have Installed Solman 7.1 SP4 and now trying to upgrade to SP10.
kernel release 721
kernel make variant 721_EXT_REL
OS windows 2008 R2
DB: Oracle 11.2.0.3
This seems to be stuck in Preprocessing Phase.
SAPup LOg
CURRENTPHASE MAIN_SHDRUN/CMDFILE_UPG
...started at 20140507212957
...begin processing at 20140507212959
..finished at 20140507213914 with status SUCCEEDED.
CURRENTPHASE MAIN_SHDRUN/DDIC_UPG
...started at 20140507213914
...begin processing at 20140507213916
SAPup.ECO
### Phase MAIN_SHDRUN/DDIC_UPG:
SAPup> Starting subprocess in phase 'DDIC_UPG' at 20140507213929
ENV: DBMS_TYPE=ora
ENV: JAVA_HOME=H:\usr\sap\SOL\DVEBMGS00\exe\sapjvm_4
ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
ENV: ORACLE_HOME=G:\oracle\SOL\11203
ENV: ORACLE_SID=SOL
ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ENV: PATH=H:\usr\sap\SOL\SUM\abap\exe;G:\oracle\SOL\11203\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;H:\usr\sap\SOL\SYS\exe\uc\NTAMD64
ENV: SAPDATA_HOME=G:\oracle\SOL
ENV: SAPSYSTEMNAME=SOL
ENV: auth_shadow_upgrade=1
ENV: dbs_ora_schema=SAPSR3
ENV: dbs_ora_tnsname=SOL
ENV: rsdb_ssfs_connect=0
EXECUTING H:\usr\sap\SOL\SUM\abap\exe\tp.EXE
"pf=H:\usr\sap\SOL\SUM\abap\var\DDICUPG.TPP" put SOL
"-Dmainimp_proc=1" "-Dparallel=3"
This is H:\usr\sap\SOL\SUM\abap\exe\tp.EXE version 380.13.51 (release
721, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps)
ULOG
### Phase MAIN_SHDRUN/DDIC_UPG:
soladm 20140507213919 : H:\usr\sap\SOL\SUM\abap\exe\tp.EXE
pf=H:\usr\sap\SOL\SUM\abap\var\SHADOW.TPP setstopmark buffer=SOL
before SAPK-70107INWEBCUIF (pid=9528)
soladm 20140507213929 : H:\usr\sap\SOL\SUM\abap\exe\tp.EXE
pf=H:\usr\sap\SOL\SUM\abap\var\DDICUPG.TPP put SOL -Dmainimp_proc=1
-Dparallel=3 (pid=14756)
Parameter Values
abap/heap_area_nondia 300000000
rsdb/obj/max_objects 20000
rsdb/obj/buffersize 50000
sap/bufdir_entries 10000
zcsa/presentation_buffer_area 20000000
zcsa/db_max_buftab 10000
zcsa/table_buffer_area 100000000
rsdb/cua/buffersize 10000
rtbb/buffer_length 60000
rsdb/ntab/irbdsize 15000
abap/shared_objects_size_MB 350
abap/buffersize 500000
rdisp/max_wprun_time 3600
ztta/roll_area 30000000
Please help.
RaghuI can see SAPupStat log as
2014/05/07 21:17:05: 39.08% LEFT: 258:43:48 END: 2014/05/18 16:00:53
2014/05/07 21:27:35: 39.14% LEFT: 258:23:47 END: 2014/05/18 15:51:22
2014/05/07 21:28:31: 39.64% LEFT: 253:02:17 END: 2014/05/18 10:30:48
2014/05/07 21:29:57: 39.81% LEFT: 251:18:37 END: 2014/05/18 08:48:34
2014/05/07 21:39:14: 39.87% LEFT: 250:57:32 END: 2014/05/18 08:36:46
Does it mean it will end on 2014/05/18 ? -
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,
NiklasHi 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
Maybe you are looking for
-
How to change default close maximize and minimize button in mac?
How can I change default close, maximize and minimize button in mac?
-
XMLForm problem with XSL Stylesheet
Hello all, I've been asked to have a look at a problem that a friend is having with XMLForms. They have recently upgraded to NW04 SP11 (from NW04 SP9) and now they cannot 'Create New' for each of the XML forms that they based on 'SAP Demo News'. They
-
Iphone App crashes since using Air 4.0
I have an APP called "Join Our Games Poker" into Itunes Store. It was generated using Flash Builder 4.7 with Air 3.9 SDK. But since Apple change the requirements in the store, the only way to get an APP approved is using the Air 4.0 SDK Build 1619
-
I had to dump my computer and reintall CS3 everything works but Photoshop. As long as I dont try to mess with the text it works. I have downloaded all the updates and it still doesnt help. Any ideas. Thanks for any h
-
I have relocated some photos using "Relocate Originals". When they are offline, meaning when the relocated photos are saved in an external hard drive and the drive is not connected, how should I work with those offline photos? For example, is it okay