SAP Knowledge Base Article - Preview

2564209 - SYSTEM MANAGER: instance list does not contain SUM central instance

Symptom

Error during SUM run in step PREP_PRE_CHECK INSTANCELIST_INIT:

SAPup.log
CURRENTPHASE PREP_PRE_CHECK/INSTANCELIST_INIT
...started at 20171115120525
# Using phase log file 'INSTANCELIST_INIT.LOG'.
...finished at 20171115120531 with status ABORTED.
# Error message set: 'SYSTEM MANAGER: instance list does not contain SUM central instance.'
...begin dialog at 20171115120532
 
INSTANCELIST_INIT.LOG
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1EETQ399 SYSTEM MANAGER: initialize instance list has failed.
1EETQ399 SYSTEM MANAGER: instance list does not contain SUM central instance.
1EETQ399 Last error code set is: SYSTEM MANAGER: instance list does not contain SUM central instance.
  • The SAP system consists of several instances on different servers

Case 1

When running the command

  • sapcontrol -nr <instance number> -function GetSystemInstanceList 

the instance list is only partially returned, with some instances missing. 
For example, in SM51, three instances appear, but the GetSystemInstanceList webmethod only returns two of them, with the third one missing:

SM51
<host1>_<SID>_<NR> <host1> Dialog Batch Update Upd2 Spool ICM Active
<host2>_<SID>_<NR> <host2> Dialog Batch Update Upd2 Spool ICM Active
<host3>_<SID>_<NR> <host3> Dialog Batch Update Upd2 Spool ICM VMC Active
 
GetSystemInstanceList

sapcontrol -nr 0 -function GetSystemInstanceList

15.11.2017 14:06:09
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
<host1>, 0, 5<NR>13, 5<NR>14, 3, ABAP GATEWAY ICMAN IGS, GREEN
<host2>, 0, 5<NR>13, 5<NR>14, 3, ABAP GATEWAY ICMAN IGS, GREEN

Case 2

It can also happen that all available instances are recognized by SUM, but none of them is handled as the 'central instance'.
For example, INSTANCELIST_INIT.LOG and INSTANCELIST.DAT display errors, and in SM51, three ABAP instances appear, but SUM recognizes the host differently and uses the physical name instead of the virtual one.

INSTANCELIST_INIT.LOG
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: <NR>, Instance Host: <virtualhost2>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: <NR>, Instance Host: <anotherhost4>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: <NR>, Instance Host: <virtualhost1>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: <NR>, Instance Host: <anotherhost5>
1 ETQ399 SYSTEM MANAGER: enhance instance list for Instance Number: <NR>, Instance Host: <virtualhost3>
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO ENQREP.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_YES.
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_NO DIAG_NO.
 
INSTANCELIST.DAT
<virtualhost2>,<NR>,5<NR>13,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<anotherhost4>,<NR>,5<NR>13,0,0.5,ENQREP,GREEN,,,CI_NO ENQREP,START STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,
<virtualhost1>,<NR>,5<NR>13,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<anotherhost5>,<NR>,51213,0,3,ABAP GATEWAY ICMAN IGS,GREEN,,,CI_NO DIAG_YES,STOP BOOTSTRAP,,,NO_INFO,NO_INFO,0,NO_INFO,SINGLE_ABAP
<virtualhost3>,<NR>,5<NR>13,0,1,MESSAGESERVER ENQUE,GREEN,,,CI_NO DIAG_NO,STOP MANDATORY,,,NO_INFO,NO_INFO,0,NO_INFO,
 
SM51
<virtualhost1>_<SID>_<NR> <virtualhost1> Dialog Batch Update Upd2 Spool ICM Active
<virtualhost2>_<SID>_<NR> <virtualhost2> Dialog Batch Update Upd2 Spool ICM Active
<virtualhost3>_<SID>_<NR> <virtualhost3> Dialog Batch Update Upd2 Spool ICM Active
 
SAPup_troubleticket.log

Summary of host system details 

SID:###<SID>
Host:###<physicalhost>
MS Host:##
GW Host:##
Start Path:###
Kernel Path:##

<physicalhost> does not match any of the virtual host names in SM51 or instancelist.


Read more...

Keywords

UID GID, nslookup, loopback, /etc/hosts, 127.0.0.2 , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-CST-STS , Startup Service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.