Skip to end of metadata
Go to start of metadata
  

Always verify the most up-to-date procedures by checking the SUM guide . Always have it on hand while performing the upgrade.

 

Purpose

During update we have various situations when an instance will be started/stopped by the update tool and troubleshooting is needed.

Follow this guide to find symptoms and solutions.

Solution

1. Identify the upgrade phase

It is shown on the SUM GUI or can be found at the end of the upgrade log file

UNIX: <update directory>/log/SAPupConsole.log or <update directory>/log/SAPup.log

WINDOWS: <update directory>\log\SAPupConsole.log or <update directory>\log\SAPup.log

2. Select the upgrade phase where the start/stop situation should be checked:

Typical upgrade phases, where the shadow instance is used:

START_SHDI_PREPUT

START_SHDI_FIRST

ACT_UPG

START_SHDI_SHD2

STOP_SHDI_RES

Typical upgrade phases where the standard instance is used:

STARTSAP_TRANS

STOPSAP_TRANS

STARTSAP_NBAS

STARTSAP_PUPG or STARTSAP_TBUPG

3. If the instance needs to be started or stopped manually

please follow the steps on the pages

Starting and stopping the shadow instance manually

Starting and stopping the standard instance during update manually

 

Start/stop the instance manually only, if it is really requested, unwanted start/stop can impact the whole update.

Related documents

SAP Startup Troubleshooting Guide for Netweaver Application Server    

 

 

  • No labels