You're performing an upgrade with DMO/SLT scenario (which is the downtime-minimized version of DMO which is currently only available on request), or using option nZDM (near Zero Downtime) in a dual stack system. You hit an error in one of the phases where SUM tries to start the SAP system (usually START_SHDI_SHD3) with the following error message:
1EETQ399 Last error code set is: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': instance numbers are identical '79' == '79'
1EETQ204 Upgrade phase "START_SHDI_SHD3" aborted with severe errors ("20150411113428")
Similar to the following:
You're not able to proceed.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
tp, connect, shadow, system, TPPARAM, STARTSSC.LOG, DEVTRACE.LOG, fatal, error, START_SHDI_SHD3, proceed, Java, roadmap, step, upgrade, update , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-UPG-DTM-TLA , Downtime Minimization for ABAP , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.