Checks after phase MAIN_SHDRUN/RUN_RADTBUCACT were negative!

Hi Experts,
        I have installed ECC 6.0 system ( OS400/V7R1)and curently i am upgrading to EhP4 SP06. Right now Preprocessing- Shadow System Installation stage and got the error.
Checks after phase MAIN_SHDRUN/RUN_RADTBUCACT were negative!
Last error code set: BATCH JOB RADTBUCACT FAILED: Error(s) found in the
log(s), accumulated in "PADTBUC.ELG".
PADTBUC.ELG log
Pool adaptions for UNICODE ERRORS and RETURN CODE in RADTBUCACT.NID
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EDDA479    Fehler bei Alter - Table Generierung für Tabelle "GLSP"
Long text:
    Cause
      This error message indicates that internal inconsistencies exist.
    System Response
    What to do
      Please consult SAP.
1EDDT066 Tabelle "GLSP" (Statements konnten nicht generiert werden)
Long text:
    Cause
      A requested database action could not be carried out.
    System Response
    What to do
      First try to repeat the action which caused this message. If the
      database action again cannot be carried out, find out the cause of the
      error using the analysis tool in the database utility. There might be
      an inconsistency between the table definition in the ABAP Dictionary
      and the existing nametab (runtime object for the table).
1EDD0319 Returncode...............: "8"
A2EEDDU 309XActivation ends with return code: "8""123341"
A trouble ticket and an archive with all relevant log files have been
generated. Trouble ticket: "/usr/sap/NID/EHPI/abap/log/SAPehpi_troubleticket.log"
I found OSS note 1449201 - Index becomes extension index: Index is deleted...And followed the manual steps. Once update the trans file and ran the report i was able to see the changes, Still i am not able to continue with the process.
Thanks.
Vel.

Hi All,
SAP development proposed below details...
While checking your system we saw that table GLSP did not have any column defined at the database level.
Since it is a freshly installed system, I recreated the table in the database via transaction SE14.
I check the other tables process in the current phase and the other tables are consistent.
Please continue with this phase.
I am able to continue with the next phase.
Thanks.
Vel.

Similar Messages

Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

Dear Guys,
We are facing issue during the upgrade from 4.6c to ECC 6.0 EHP4 in pre-processing phase,
Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
Last error code set: Detected 257 errors summarizes in 'ACTUPG.ELG' Check logfiles 'ACTUPG.ELG' and 'I:\usr\sap\DV1\upg\abap\log\SAPup.ECO'
ACTUPG.ELG:
******* LIST OF ERRORS AND RETURN CODES ******* ************************************************** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INECCDIMP.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INERECRUIT.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INFICA.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INFICAX.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INFINBASIS.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016ININSURANC.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INISM.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INISOIL.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INISPSCA.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60016INISUT.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60017INECCDIMP.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 ETP111 exit code : "8" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60017INERECRUIT.DV1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
......... Please help us to resolve the problem.
Regards,
Bharathi

Hi Bharathi,
Can you please provide the contents of the activation log SAPA-60016INECCDIMP.DV1 which provides the information about the error.
Please check the activation log SAPAAA*.DV1 to know which tables are not activated.
Thank You.
Regards,
Deepika

Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative

Hi Gurus,
am upgrading from ecc 6.0 to ehp5 on dual stack system OS:Windows 2003 DB:oracle 10.2.0.2
i got below error in the MAIN_NEWBAS/XPRAS_UPG phase
XPRASUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-500AGINCPRXRPM.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14152200")
Long text:
    Cause
      Program "&V#&", which was started in the background, was terminated
      abnormally.
    System Response
      The system created a job log for the terminated program.
    What to do
      Proceed as follows:
      Log onto the system in which the program was executed. The system is
      specified at the beginning of the transport log.
      Then call transaction SM37 to display the job log.
      Enter "&V#&" as job name and "DDIC" as user name.
      Restrict the starting date to the starting date specified in the
      transport log.
      For the other selection criteria, select only jobs with the status
      "cancelled". Then press <LS>Execute</>.
      A list of the jobs satisfying the selection criteria is displayed.
      You can display the log by pressing <LS>Job log</>.
      If the list contains several jobs, you can select the job with the ID "
      &V#&" with <LS>Display</> -> <LS>Job details</> or define further
      details for the selection criteria in the initial screen of transaction
      SM37.
      If the ABAP processor reports cancellation, double-clicking on the
      corresponding message in the job log branches to the display of the
      corresponding short dump.
1AEPU320 See job log"RDDEXECL""14152200""IJE"
1 ETP111 exit code           : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server admin0001 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
Dump at ST22:
Error analysis
    The following syntax error was found in the program
     CL_DPR_TASK_O=================CP :
    "Formal parameter "IV_PLANSTART" does not exist."
please help me solve
Thanks,
Venkat

Hi Sunny,
here is dump details..
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           CL_DPR_TASK_O=================CP
Application Component PPM-PRO-STR
Date and Time          06.12.2011 16:34:41
User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transaction ID...... "04FA1FE12F6DF16DB7E400145E69764F"
    EPP Whole Context ID.... 34454438393637453445443839363745
    EPP Connection ID....... 34454442374143323445444237414332
    EPP Caller Counter...... 1
    Program............. "CL_DPR_STATUS_CHANGE_OBSERVER=CP"
    Screen.............. "SAPMSSY0 1000"
    Screen Line......... 6
    Debugger Active..... "none"
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
     "CL_DPR_TASK_O=================CP " in include
     "CL_DPR_TASK_O=================CM021 " in
    line 74:
    "Formal parameter "IV_PLANSTART" does not exist."
    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 "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
     The following syntax error was found in the program
      CL_DPR_TASK_O=================CP :
     "Formal parameter "IV_PLANSTART" does not exist."
Information on where terminated
    Termination occurred in the ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" -
     in "SET_HANDLER".
    The main program was "R_DPR_PROJECT_ROLES_XPRA ".
    In the source code you have the termination point in line 12
    of the (Include) program "CL_DPR_STATUS_CHANGE_OBSERVER=CM00A".
    The program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
Thanks in advance
Venkat

Installing EHP4 on ERP 6.0: Checks after Phase SHD_RUN/ACT_UPG were negativ

hi
I'm installing the EHP4 on an ERP 6.0 System and get the following error:
Checks after phase MAIN_SHDRUN/ACT_UPG were negative!
Last error code set: Unresolved requests in buffer EH4 Check logfiles 'ACTUPG.ELG' and 'C:\usr\sap\EH4\upg\abap\log\SAPehpi.ECO'
Here is a part of SAPEhpi.EH4:
SAPehpi> Starting subprocess tp.exe with id 5208 at 20090727150713
EXECUTING C:\usr\sap\EH4\upg\abap\exe\tp.exe pf=C:\usr\sap\EH4\upg\abap\bin\ACTUPG.TPP put EH4
Environment: JAVA_HOME=C:\j2sdk1.4.2_16-x64
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Environment: Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\j2sdk1.4.2_16-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\usr\sap\EH4\DVEBMGS00\exe
Environment: dbs_mss_schema=eh4
This is C:\usr\sap\EH4\upg\abap\exe\tp.exe version 372.04.65 (release 701, unicode enabled)
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)
stopping on error 12 during DD ACTIVATION
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
ERROR: stopping on error 12 during DD ACTIVATION
Process with ID 17820 terminated with status 12
Part of ACTUPG.EH4:
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-40401INEAIPPE.EH4
1 ETP111 exit code           : "12"
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-603DDINEAAPPL.EH4
1 ETP111 exit code           : "12"
I applied the note 1306559 but it didn't help.
someone has an idea?
thank you

now i got some data from the shadow instance
JOB:
RDDMASGL                            DDIC         Canceled
JOB LOG:
Job started
Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)
Start of mass activation 10:37:39
ABAP/4 processor: TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Job cancelled
Runtime Error Short Text
    No roll storage space of length 638992 available for internal storage.
Error Analysis
Error analysis
    The internal table "\FUNCTION=DD_MASS_ACT_C3\DATA=DEPTAB" could not be enlarged
     further.
    Memory location: "Session memory"
    You attempted to extend the data structure for the management of the
    memory blocks for table "\FUNCTION=DD_MASS_ACT_C3\DATA=DEPTAB". However, the
     638992 bytes required for
    this were no longer available in the specified memory area.
    The amount of memory requested is no longer available.
should i also apply the note 1306559 in the shadow instance?
thx
Edited by: Joachim Knittl on Jul 29, 2009 3:30 PM

MAIN_SHDRUN/PARDIST_SHD were negative in Preprocessing phase of Upgrade

Hello All,
We are doing an upgrade in our landscape and getting in to errors in the preprocessing phase
Landscape Details : R/3 4.6C to ECC 6.0 EHP4 with DB2 database in AIX.
The error at the phase is MAIN_SHDRUN/PARDIST_SHD
Checks after phase MAIN_SHDRUN/PARDIST_SHD were negative!
Last error code set: Single errors (code <= 8) found in logfile 'PARDSHD.ELG'
The logs which i got in the PARDSHD.LOG is pasted below
4 ETQ359 RFC Login to: System="HMD", Nr="01", GwHost="devccp01", GwService="sapg
w01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ263 Batchjob "RDDGENBB_7" finished successfully
3 ETQ399 log analyse: search for '.[WT ]' in '^DS......\.HMD$'
4 ETQ399 2009/12/12 12:22:14: put_execute: (tp) forkpid:1110020
4 ETQ399 Set environment for standard connect:
4 ETQ399 ENV: dbs_db6_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=0
4 ETQ399 Set RFC variables for standard connect:
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Set tool parameters for standard connect:
4 ETQ399   default TPPARAM: DEFAULT.TPP
4 ETQ399 Set environment for shadow connect:
4 ETQ399 ENV: dbs_db6_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=1
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399   default TPPARAM: SHADOW.TPP
4 ETQ010 Date & Time: 20091212122214
I have tried to repeat the phase and searched in SDN and in SMP. What I am getting is that its more related to SQL database and DB trigger of the table.
Its nothing related to my issues, If you anyone have any view on this please suggest me
Regards
Vijay

Hi
Thanks for the Reply
Herewith I have attached the log files of PARSHD.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISTRIBUTION ERRORS and RETURN CODE in DS091212.HMD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "OGV1_VAPMA_WSOP"
Long text:
    Cause
      This error message indicates that internal inconsistencies exist.
       System Response
    What to do
      Please consult SAP.
2EEDA471    Result   "OGV1_VAPMA_WSOP":    Action: "MDF"      Mode flag: "V"
Return code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "ROG_VBAPUP")
Long text: see above
2EEDA471    Result   "ROG_VBAPUP":    Action: "MDF"      Mode flag: "V"    Retur
n code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "OGV1_VAPMA_WSOP"
Long text: see above
2EEDA471    Result   "OGV1_VAPMA_WSOP":    Action: "MDF"      Mode flag: "V"
Return code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "ROG_VBAPUP")
Long text: see above
2EEDA471    Result   "ROG_VBAPUP":    Action: "MDF"      Mode flag: "V"    Retur
n code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "OGV1_VAPMA_WSOP"
Long text: see above
2EEDA471    Result   "OGV1_VAPMA_WSOP":    Action: "MDF"      Mode flag: "V"
Return code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "ROG_VBAPUP")
Long text: see above
2EEDA471    Result   "ROG_VBAPUP":    Action: "MDF"      Mode flag: "V"    Retur
n code: "0"
2EEDA480   Update fails (mode flag "M" to "V" in DDXTT. Table: "OGV1_VAPMA_WSOP"
Long text: see above
I can see thre are no entries in sm13 or problem in ST22.
Regards
Vijay

EHP4 upgrade Error - phase MAIN_SHDINST/RUN_RSVWSCPY were negative

Hello
Currently I am doing EHP4 upgrade on Oracle 10g with Sun Solaris 5.10 , During preprocessing phase ( The EhP Installation program builds the shadow system from the original one.)
I am getting following error
Checks after phase MAIN_SHDINST/RUN_RSVWSCPY were negative!
Last error code set: BATCH JOB RSUPG_COPY_SHD_VIEWS FAILED: Error(s) found in the log(s), accumulated in "RSVWSCPY.ELG".
Log file for RSVWSCPY.ELG as below
cat RSVWSCPY.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Clone shadow views ERRORS and RETURN CODE in RSVWSCPY.<SID>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETGCLN ORA-12154: TNS:could not resolve the connect identifier specified
1EETGCLN Unable to open connection to shadow system.
1EETGCLN Use function module CREATE_SHDDBCON to adjust the settings for connection UPGSHD.
cat sqlnet.ora
===========
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
NAMES.DEFAULT_DOMAIN = WORLD
05.01.06 unsorported parameter now
#NAME.DEFAULT_ZONE = WORLD
05.01.06 set the default to 10
SQLNET.EXPIRE_TIME = 10
05.01.06 set to default
#TCP.NODELAY=YES
05.01.06 set to 32768
DEFAULT_SDU_SIZE=32768
cat tnsnames.ora
=============
<SID>.WORLD=
(DESCRIPTION =
    (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = SAP.WORLD)
          (PROTOCOL = TCP)
          (HOST = <hostname>)
          (PORT = 1527)
    (CONNECT_DATA =
       (SID = <SID>)
       (GLOBAL_NAME = <SID>.WORLD)
===
Could you please help me to fix the issue.
Thanks , BM

Hello Orkur,
Like bharath reddy and others, I´m facing with the same error, but in my case the platform is OS/400 (V7R1M0) database DB4!
I´m doing an EHP5 upgrade and it stopped in phase MAIN_SHDINST/RUN_RSVWSCPY, the following error is show me:
Checks after phase MAIN_SHDINST/RUN_RSVWSCPY were negative!
Last error code set: BATCH JOB RSUPG_COPY_SHD_VIEWS FAILED: Error(s)
found in the log(s), accumulated in "RSVWSCPY.ELG".
In that RSVWSCPY.ELG file it have the following details:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Clone shadow views ERRORS and RETURN CODE in RSVWSCPY.PRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EETGCLN
1EETGCLN Unable to open connection to shadow system.
1EETGCLN Use function module CREATE_SHDDBCON to adjust the settings for connection UPGSHD.
I performed what you mentioned, I execute "Create_SHDDBCON" function module on SE37... but I didn´t continue this execution because I´m not sure what I have to fill in that parameters: DBUSER ; DBPASS and CONENV. You recommended some values to that fields/parameters... but where you have been seeking this values/information? How you know that?
Can you help me/us?
Thank you
JC project

Phase MAIN_NEWBAS/XPRAS_AIMMRG were negative!sta

Dear Expert,         we are upgrade my system from ERP 6.0 to ERP 6.0 EHP 7. we are now in stage of execution phase MAIN_NEWBAS/XPRAS_AIMMRG but we received the following error:-
Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative!
Last error code set: Detected 3 aborted activities in 'XPRASUPG.ELG'<br/> Calling 'E:\usr\sap\UPG\DVEBMGS00\exe/tp' failed with return code 12, check E:\SUM\abap\log\SAPup.ECO for details
ERROR: Detected the following errors:
# E:\SUM\abap\log\SAPR740XPRA90000135.UPG:
          2 EPU114XXPRA "RS_PERS_XPRA_1" has already been executed in a previous step
          3 ETP000
          3 ETP000 **************************************************
          3 ETP000
          2 EPU115XReport "RS_TCO_ACTIVATION_XPRA" started: "20140417071810"
          1AETR012XProgram canceled (job "RDDEXECL", number "07180600")
          1AEPU320 See job log"RDDEXECL""07180600""UPG"
Trouble Ticket Generation
A trouble ticket and an archive with all relevant log files have been generated. Trouble ticket: "E:\SUM\abap\log\SAPup_troubleticket.log" Log archive: "E:\SUM\abap\log\SAPup_troubleticket_logs.sar"
and we received option as in the picture:
Kindly aid us to fix this issue.
Regards
Said Shepl

Dear Gaurav,
        Thanks about reply.
this is the log file XPRASUPG.ELG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR740XPRA90000135.UPG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 EPU114XXPRA "RS_PERS_XPRA_1" has already been executed in a previous step
3 ETP000
3 ETP000 **************************************************
3 ETP000
2 EPU115XReport "RS_TCO_ACTIVATION_XPRA" started: "20140417071810"
1AETR012XProgram canceled (job "RDDEXECL", number "07180600")
1AEPU320 See job log"RDDEXECL""07180600""UPG"
1 ETP111 exit code           : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
and this is the picture for Upgrade selection:-

Upgrade to ECC 6.04 PHASE: MAIN_SHDIMP/SHADOW_IMPORT_INC were negative

Hello!
We are busy upgrading from ERP 2004 to ECC 604 SR1.
Error:
Checks after phase MAIN_SHDIMP/SHADOW_IMPORT_INC were negative!
Last error code set: Unresolved requests in buffer TST Check logfiles
'SHDALLIMP.ELG' and '/binaries/sap/TST/upg/abap/log/SAPup.ECO'
tp and r3trance updated to new versions.
Error in file SHDALLIMP.ELG
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-60403INCCEE.TST
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
1 ETP111 exit code           : "8"
Error in file SAPK-60403INCCEE.TST
3 ETW674Xstart import of "R3TRTABU/ATL/AT086" ...
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
4 ETW000   0 entries from /ATL/AT086 (%) deleted.
2EETW000 key field /ATL/AT086-MANDT contained the value '205': key field /ATL/AT086-MANDT missing, key is truncated.
4 ETW000   0 entries from /ATL/AT086 (%) deleted.
4 ETW000 "E071~"-LOCKFLAGs 000002 - 000136 updated ('3', 135 entries).
4 ETW000 date&time: 16.05.2011 - 17:08:33
3 ETW676 end import of "R3TRTABU/ATL/AT086" (warnings).
4 ETW000 "E071~"-LOCKFLAGs 002009 - 002009 updated ('1', 1 entries).
4 ETW690 COMMIT "17460" "35048"
Error in file SAPup.ECO
Phase SHADOW_IMPORT_INC:
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 13063 at 20110516170633
ENV: DIR_LIBRARY=/binaries/sap/TST/upg/abap/exenew
ENV: JAVA_HOME=/usr/j2se
ENV: LD_LIBRARY_PATH=/binaries/sap/TST/upg/abap/exenew:/binaries/sap/TST/upg/jvm/jre/lib/sparcv9/server:/binaries/sap/TST/upg/jvm/jre/lib/sparcv9:/binaries/sap/TST/upg/jvm/jre/../lib/sparcv9:/etc/emc/rsa/cst/lib:/usr/sap/TST/SYS/exe/run
ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/TST/102_64
ENV: ORACLE_PSRV=TST
ENV: ORACLE_SID=TST
ENV: ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data
ENV: PATH=/binaries/sap/TST/upg/abap/exenew:/oracle/TST/102_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/opt/EMCpower/bin:/etc/emc/bin:/etc:/usr/ccs/bin:/usr/ucb
ENV: SAPSYSTEMNAME=TST
ENV: auth_shadow_upgrade=0
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPR3Q
ENV: dbs_ora_tnsname=TST
EXECUTING /binaries/sap/TST/upg/abap/exenew/tp (/binaries/sap/TST/upg/abap/exenew/tp) pf=/binaries/sap/TST/upg/abap/bin/SHDALLIMP.TPP put TST
This is /binaries/sap/TST/upg/abap/exenew/tp version 376.01.25 (release 701, unicode enabled)
ERROR: stopping on error 8 during SHADOW IMPORT
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
SWARNS: Highest tp internal severe warning was: 0151
tp finished with return code: 151
meaning:
Some warning regarding buffer entries
Process with ID 13063 terminated with status 151
Any idea for helpme,
thanks in advise.
Roman.

Hi,
Check SAP Note 1293059 - C-CEE 110_604: Add-On Support Packages. Your problem is documented in this note.
Thanks
Sunny

Upgrade issue in phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative

Hello Team,
Got hanged at the phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative,.
Error:
Checks after phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE were negative!
Last error code set: Detected 1 aborted activities in 'PHASES.ELG'<br/> Calling 'D:\usr\sap\XXX\DVEBMGS00\exe/tp' failed with return code 13, check D:\Software\SUM\abap\log\SAPup.ECO for details
Log file says:
EXECUTING D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all XXX
This is D:\usr\sap\XXX\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
Could not open the ICU common library.
The following files must be in the path described by
the environment variable "PATH":
icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 12148
PATH is currently set to D:\usr\sap\XXX\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\XXX\SYS\exe\uc\NTAMD64 [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 12148
stopping on error 13 during MAIN IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 13
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 13
meaning:A tool used by tp got a signal from operating system
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 13 during MAIN IMPORT
SAPup> Process with PID 12212 terminated with status 13 at 20140515155156!
### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
Please help me out,..
Thank you,
Mohan Karamala.

I have cancelled the upgrade and tried again,..but got hanged with the same problem,..
Please help me,. or can i raise a ticket with SAP.???
Log details:
### Phase PREP_IMPORT/TOOLIMP_TOOLDEL_PRE:
SAPup> Starting subprocess in phase 'TOOLIMP_TOOLDEL_PRE' at 20140519045354
    ENV: DBMS_TYPE=mss
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64
    ENV: SAPSYSTEMNAME=PS1
    ENV: dbs_mss_schema=ps1
    ENV: rsdb_ssfs_connect=0
EXECUTING D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE "pf=D:\Software\SUM\abap\var\DEFAULT.TPP" import all PS1
This is D:\usr\sap\PS1\DVEBMGS00\exe\tp.EXE version 380.03.95 (release 738, unicode enabled)
Could not open the ICU common library.
   The following files must be in the path described by
   the environment variable "PATH":
   icuuc50.dll, icudt50.dll, icuin50.dll [D:/depot/bas/741_REL/src/flat/nlsui0.c 1535] pid = 2560
PATH is currently set to D:\usr\sap\PS1\DVEBMGS00\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\j2sdk1.4.2_24-x64\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PS1\SYS\exe\uc\NTAMD64 [D:/depot/bas/741_REL/src/flat/nlsui0.c 1538] pid = 2560
stopping on error 13 during MAIN IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 13
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 13
meaning:
A tool used by tp got a signal from operating system
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 13 during MAIN IMPORT
SAPup> Process with PID 7332 terminated with status 13 at 20140519045404!
Thank you,
Mohan Karamala.

Checks after phase PREP_IMPORT/TOOLIMPD

Hi All
We are installing EHP4 SP6 in our ECC 6.0 system. Weu2019ve created a .xml file in our solution manager and calculated a download queue with the MOPZ. The installation is on a Windows 2003 32 Bit platform with a SQL server 2005 SP2 DB.
In roadmap step 2 (Extraction) the installation stops with the message: u201CChecks after phase PREP_IMPORT/TOOLIMPD were negative! Last error code set: Unresolved requests in buffer <SID> Check logfiles 'TOOLIMPD.ELG' and 'H:\EHPI\abap\log\SAPehpi.ECO'
During executing this job RDDMASGL a shortdump is generated:
What happened?
Error in the ABAP Application Program
The current ABAP program "RADMASG0_C3" had to be terminated because it
Has come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSDMP " in include
"RADMASUTC " in line 4146: "The data object "DELTAB" does not have a component called "MAINOBJEX"."Note 1449201 - Index becomes extension index: Index is deleted
discripes the error/solution.
I think the error arise after implementing note: 1449201, but Iu2019m not sure.
In the note:
"Make sure that you note the manual prerequisites. If these are required in your system, you may not under any circumstances implement this note without adjusting the structure DDGENTAB. Otherwise, syntax errors would occur in the report RADMASUTC and then Dictionary activation would no longer be possible.
If errors occur when you implement the correction instructions or when you perform the manual pre-implementation steps, open a message under the component BC-DWB-DIC and refer to this note. Allow SAP Support to have access to your system."
For about the solution we have to contact SAP. Iu2019ve created a SAP message and Iu2019m still waiting for a solution. Did anyone had this problem before and what was the solution?
Thanks in advance for your reply.
Kind Regards,
Rik Hut

Hi Rik,
I've just had a near-identical problem whilst trying to install support packs onto our BI 7.00 Test system. I found that my problem was because someone had performed a TP IMPORT ALL into the BI Test system, which imported all the modification adjustment transports from the SP import in the BI Development system too early.
I fixed the problem by logging onto the BI Development system and looking at the version management for the object that was generating the syntax errors. I found a reference to the original transport for the object and re-imported it into the BI Test system to overwrite the latest version, which shouldn't have been in the Test system in the first place!
I don't know whether SAP would recommend this approach because I don't know what side-effects 'downgrading' the objects in that request could have. However, I do know that it has fixed the Support Package problem, and I can now run SPAM quite happily once again.
I hope this helps,
Arwel Owen
Enterprise Systems Manager,
Princes Ltd.

ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
Thanks

Hi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

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?

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,

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

Seagate external drive: Partition map check failed because no slices were found

I have a 3TB Seagate Expansion external backup drive connected to my Retina Macbook Pro via USB. The disk will not eject from a regular Finder window - it will only eject from Disk Utility. Backups seem to otherwise be running fine. I tried to verify/repair the disk in Disk Utility, and I got the following error: "Partition map check failed because no slices were found." I am able to verify/repair the partition without any problem, and no errors are found.
I'm concerned about relying on a backup drive that may be heading south. Here is the output from diskutil info:
diskutil info disk3
   Device Identifier:        disk3
   Device Node:              /dev/disk3
   Part of Whole:            disk3
   Device / Media Name:      Seagate Expansion Desk Media
   Volume Name:              Not applicable (no file system)
   Mounted:                  Not applicable (no file system)
   File System:              None
   Content (IOContent):      GUID_partition_scheme
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 USB
   SMART Status:             Not Supported
   Total Size:               3.0 TB (3000592977920 Bytes) (exactly 5860533160 512-Byte-Units)
   Volume Free Space:        Not applicable (no file system)
   Device Block Size:        4096 Bytes
   Read-Only Media:          No
   Read-Only Volume:         Not applicable (no file system)
   Ejectable:                Yes
   Whole:                    Yes
   Internal:                 No
   OS 9 Drivers:             No
   Low Level Format:         Not supported

@ Allan Eckert: Unfortunately, reformatting is out of the question, I have 5 years of work on this!
@ Loner T: Yes, the firmware did successfully upgrade after router reboot and a bit of troubleshoot.
Thanks for the quick replies. Keep 'em coming!

Checks after phase MAIN_SHDRUN/RUN_RADTBUCACT were negative!

Similar Messages

Maybe you are looking for