2892102 - Shadow instance cannot start in START_SHDI_FIRST phase: ‘disp+work’ in “YELLOW: Server startup procedure running”

• During the upgrade, Shadow instance cannot be started; you’re getting an error on phase MAIN_SHDRUN/START_SHDI_FIRST:

  Severe error(s) occurred in phase MAIN_SHDRUN/START_SHDI_FIRST!
  Last error code set: Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process <path>/SUM/abap/exe/sapcontrol exited with 2, see '<path>/SUM/abap/log/SAPup.ECO' for details

•  On STARTSFI.LOG file, you find error about Shadow instance not starting (instance number $$):

  1EETQ399 SYSTEM MANAGER: START of mandatory instance $$ on server <server_name> has failed
  2EETQ399 Starting shadow instance failed
  1EETQ399 Last error code set is: Shadow instance
  1EETQ399Xcouldn't be started, check 'START_SHDI_FIRST.LOG' and 'DEVTRACE.LOG': Process <path>/SUM/abap/exe/sapcontrol exited with 2, see '<path>/SUM/abap/log/SAPup.ECO'
  1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("yyyymmddhhmmss").

• If you check the status from the processes on Shadow instance (this can also be seen on SAPup.ECO file):

  sapcontrol -nr $$ -function GetSystemInstanceList
 
  name, description, dispstatus, textstatus, starttime, elapsedtime, pid
  enserver, EnqueueServer, GREEN, Running, 20yy mm dd hh:mm:ss, 0:12:34, 786590
  msg_server, MessageServer, GREEN, Running, 20yy mm dd hh:mm:ss, 0:12:34, 768954
  disp+work, Dispatcher, YELLOW, Server startup procedure running, 20yy mm dd hh:mm:ss, 0:12:34, 642531
  gwrd, Gateway, YELLOW, Scheduled, , , -1
  icman, ICM, YELLOW, Scheduled, , , -1

SAP NetWeaver system

START_SHDI_FIRST, STARTSFI.LOG, Starting shadow instance failed
Server startup procedure running, DpRenameFile, DpWpSaveOldTraces , KBA , BC-CST-STS , Startup Service , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-OP-LNX , Linux , Problem