Error During The Phase Main Shdrun
Error During The Phase Main Shdrun
Page 1 of 7
Hello,
During the upgrade of our ERP system (from R/3 4.7 to ERP 6.0 EHP5) the SAPup
stopped with the following error during the phase MAIN_SHDRUN/ACT_UPG:
**************************************************
******* LIST OF ERRORS AND RETURN CODES *******
**************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Related
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG702.DEV
Discussions
EhP5 Upgrade: Pre-Processing Phase Very Slow
1EEDO519X"Data Element" "ZESTIMATI" could not be activated Error Upgrade sap R3 4.6C to ECC 6 electricy was gone
1EEDO519 "Table" "VFAGL_GCDVC_VER_C" could not be activated in phase
Upgrading process of ECC 5.0 to ECC6 ACT_700 phase
1EEDO519 "Table" "ZCONSUMO_SEMANA_STRUCT" could not be activated
erro:
1EEDO519 "Table" "ZMIGO_EDICAO_STRUCT" could not be activated Unicode Conversion Preparations - TP Unlock Shadow
1EEDO519 "Table Type" "ZMIGO_EDICAO_TABLE" could not be activated Instance
DDIC activation error when applying SP13 on ERP 6.0
1EEDO519 "Table" "VFAGL_GCDVC_VER_C" could not be activated
IDES
1EEDO519 "Table" "ZCONSUMO_SEMANA_STRUCT" could not be activated Upgrade error MAIN_SHDCRE/SQLDB_DDNTT_UUID
1EEDO519 "Table" "ZMIGO_EDICAO_STRUCT" could not be activated ORA-08103: Object no Longer Exists
1 ETP111 exit code : "8" spam DDIC_ACTIVATION error
MAIN_SHDRUN/ACT_UPG Take Long Time
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 2 of 7
Environment: dbs_mss_schema=dev
This is E:\usr\sap\DEV\upg\abap\exe\tp.exe version 380.08.41 (release 720)
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
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Process with ID 2460 terminated with status 8
Kind regards,
Onorio
Hello to all,
For data element ZESTIMATI there is a domain 'CHA10' maintained, which does
not exist, to solve this error I maintain a valid domain for that data element
--'CHA11'.
The same occurs for ZMIGO_EDICAO_STRUCT, so I did the same that I did in
table ZCONSUMO_SEMANA_STRUCT.
Then I log on in system with a different user than DDIC user and I solved all the
errors with this user!
Kind regards,
Onorio
Contributors:
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 3 of 7
Hi,
Regards
Hi,
You may need to check the table or data element in shadow system, the check will
show details, the table name you have posted seems all customizing tables instead of
SAP standard table. You may need to check the version and ask your company's
developer to fix up the error.
I have already solved some issue like that in this phase,hope it helps.
Hello David,
The file SAPACCG702.DEV is big! It contains a lot of information about the tables
activation and the result of that...!
Any tip?!
Thank you,
Onorio
Every thing you need is in the log that you provided and you have been given the
proper hint. The tables displayed as errored need to be reviewed in the shadow and
activated in order to continue. once you can successfully activate the objects then you
can move on...The system offers you some choice on whether to ignore non critical
errors and continue or to restart the phase. if you restart the phase and the same
errors occur then fix and activate the objects and then choose to continue with the
ignore but do this only after you have tried the restart....take good notes...you should
be discovering these types of errors in your sandbox upgrade (which should be a copy
of production) and ironing out all the issues before performing the upgrade in
production. In essence build a logical and tested script as you will for the actual
production upgrade
Related
Evolution of End User Computing--Evolving to Better Meet ...
Business VoIP Comparison Guide
Simplified Enterprise Phone Systems
Hello
Connect to the shadow system and activate these tables manually by calling the Tx
SE11.
If you get any errors during the activation check the logs and come back with them.
Regards
RB x
We have updated our Privacy Policy and encourage you to read it by clicking here.
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 4 of 7
Hello,
I need to access to the shadow instance with other user than DDIC but the system
show me a message "Upgrade still running: Logon not possible". I searched for a
solution, a command to unlock it, and I found it in "Troubleshooting and Administration
on Windows" but the commands didn't work!
Thank you,
Onorio
Hello David,
But I need to logon with other user in other clients of the shadow instance!
Thank you,
Onorio
Hi Onirio,
If I was you I would not unlock the shadow system unless SAP say you should.
Regards
Hello
And the other command is: SAPup tp unlock <SAPSID>
This is wrong.
You need to go to the bin directory in the upgrade file system and unlock it like I have
shown below.
cd <upgrade directory>/bin
./SAPup unlockshd <SAPSID>
Regards
RB
x
We have updated our Privacy
David Caddick Policy
replied and
Jul 31, encourage you to read it by clicking here.
2013 0
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 5 of 7
Hi Onirio,
It is not a good idea to unlock the shadow system during the upgrade, unless SAP has
specifically instructed you do this.
Regards
Hello,
Paste the last contents of the log files so that we know what problem are you facing.
Regards,
Sanket K
Hello
Unlocking the shadow system and also the primary system during the upgrade is done
when you encounter an issue during the upgrade process.
You don't unlock an instance when the upgrade is in progress.
There are few SAP notes that speak about unlocking the SAP system during upgrade.
Regards
RB
HELLO,
It is still not recommended to unlock a system during an upgrade, unless SAP have
recommended for your issue. This recommendation can come via a SAP note for
known problems or to solve a problem you have reported to SAP.
As there are no notes for this specific problem you need to get SAP to look.
Regards
Good evening
I disagree with you.
The DDIC ACTIVATION ERRORS are common during upgrade activities.
I have faced numerous times these issues.
To find out more about the activation issue you will need to analyse the dumps in the
SAP system. For that you need to connect to the SAP system and check it.
DDIC user will let you login to the system without unlocking the system from the OS
level.
If there is a need to implement some changes then you will have to unlock the system.
There is no where written that you are NOT supposed to unlock the system without the
permission of SAP.
Regards,
RB
Hello to all,
For data element ZESTIMATI there is a domain 'CHA10' maintained, which does not x
We have updated our Privacy Policy and encourage you to read it by clicking here.
exist, to solve this error I maintain a valid domain for that data element --'CHA11'.
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 6 of 7
The same occurs for ZMIGO_EDICAO_STRUCT, so I did the same that I did in table
ZCONSUMO_SEMANA_STRUCT.
Then I log on in system with a different user than DDIC user and I solved all the errors
with this user!
Kind regards,
Onorio
Hi Onorio,
Thank you for letting the group know that you solved the problem, and that you
followed SAPs advice.
Regards
My Home Data Center Enterprise Architecture & EAI Networking & Infrastructure About
Topics Data Center Enterprise Architecture & EAI Hardware News
People Networking Privacy
Companies Development Information Management Communications Technology Terms of Use
Jobs C Languages Business Intelligence Work at Toolbox.com
White Paper Library Java Database Operating Systems Advertise
Visual Basic Data Warehouse Linux Contact us
Collaboration Tools Web Design & Development Knowledge Management UNIX Provide Feedback
Discussion Groups Oracle Windows
Blogs Help Topics
Enterprise Applications Technical Support
Follow Toolbox.com CRM IT Management & Strategy Security PCMag Digital Group
Toolbox for IT on ERP Emerging Technology & Trends Security
Twitter PeopleSoft IT Management & Strategy
Toolbox.com on Twitter SAP Project & Portfolio Management Storage Other Communities
Toolbox.com on SCM Storage
Facebook Siebel Cloud Computing Toolbox for HR
Cloud Computing Toolbox for Finance
Copyright ©1998-2017 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective
companies. Toolbox.com is not affiliated with or endorsed by any company listed at this site.
AdChoices x
We have updated our Privacy Policy and encourage you to read it by clicking here.
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017
Error during the phase MAIN_SHDRUN/ACT_UPG [SOLV... Page 7 of 7
x
We have updated our Privacy Policy and encourage you to read it by clicking here.
http://sap.ittoolbox.com/groups/technical-functional/sap-basi... 23-11-2017