This is a limitation when the same short hostnames but different domains are used on the same host.
In this case the Host Agent is forced to leave IP and FQDN empty.
For these two IPs, only one SAP_ComputerSystem object with name “hostname2” will be found in the LMDB.
This object will not have IP and FQDN set because they are not unique with regards to the short name “hostname2”.
Verify the the Managed System have a real installation number (only numbers).
Go to R3 / System / Status and check that the Installation Number is correct
Set the windows environment variable $DIR_TEMP to c:\tmp and provide such a directory on all Windows based server nodes.
Note: to enable RLMDB_DS_DISPLAY_TRACES program -> VC_LMDB_SETT_L -> LDB -> New CIM Settings Entry -> DataSupplier.TraceIsActive -> Set Checkbox "Bool. val." to selected
If you have an SLDR:
If you have no SLDR:
You have upgraded the SHA to REL 721 ≥ SP29
If you have received an error: "Failed to open destination file "/usr/sap/hostctrl/exe/slddest.cfg" or "Failed to read connect file: /usr/sap/hostctrl/exe/slddest.cfg"
Outside discovery must be run again using the new method ConfigureOutsideDiscovery Discovery as described in page Preparing Outside Discovery.
This will regenerate the slddest.cfg as sapadm.
Further Troubleshooting: if you are still unable to execute the new method, you can change the ownership of the slddest.cfg file from root to sapadm
execute: chown sapadm:sapsys slddest.cfg
Check if the SAP Host Agent has the latest available version from SMP: SAP Host Agent 7.21 from http://support.sap.com/swdc -> Support Packages and Patches -> Browse Download Catalog -> SAP Technology Components -> SAP HOST AGENT -> SAP HOST AGENT 7.21 - if not, proceed with an upgrade: /usr/sap/hostctrl/exe/saphostexec -upgrade -archive /tmp/SAPHOSTAGENT1x_1x-xxx.SAR
Check first if the SM59 host destination has the same sapadm password than the one used for the SAP Host Agent installed on the host, and that the sapadm Password is also the as as declared in the Customer Network. the sapadm user is used for SDA Installation / Configuration / Restart / Agent Internals (logs) and any SAP Host Agent to Simple Diagnostics Agent communications.
Check also that you have successfully imported latest version of the Simple Diagnostics Agent Archive SIMDIAGAGNTxx_xxx.SAR and the latest JRE JRE81_xx-xxx.SAR archive using SRSM_AMA_UPLOAD_BINARY (SA38 transaction) like described in the Master Guide.
A-To Debug SDA Deployment Issues:
Check the On the File system (sapadm needed):
Execute from the Agent Administration:
B-To Debug the Simple Diagnostics Agent availability deployed successfully on the SAP Host Agent
Check the Simple Diagnostics Agent availability status and configuration:
Diagnostics Agent State is:
The configuration status is:
White: If the Diagnostics Agent is not configured. This should not be happen because there is always a default configuration at installation time. If you see a white configuration status.
Green: This means that the metrics are sent successfully from Focused Run for Solution Manager to the Diagnostics Agent. The status can have two different characteristics Confirmed or Up-to-date, If the status is Confirmed, then the agent has the configuration versions that it expected. If the status is up-to-date, the confirmation by metrics is still missing.
Yellow pending: Focused Run for Solution Management can’t send any metrics to the Diagnostics Agent, but it is assumed that it will be successfully sent later. For this reason, Focused Run for Solution Manager tries to send the configuration in an interval and the status is Pending. This happens, for example, if network problems occur, the authorization fails or the agent is not available for the moment.
Yellow Confirmation Outdated: This means that Focused Run for Solution Manager has sent metrics to the Simple Diagnostics Agent but the metric version is older than expected. The Focused Run for Solution Manager tries it later again (self-healing). You can identify this in the configuration information, looking for the "Send Count" > 1.
Check On the Agent Administration:
Check the On the File system (sapadm needed):
Log onto the system and check whether the following calls were successful.
The first call registers the sldds.xml at the SAP Host Agent: hostctrl/exe/saphostctrl-function ConfigureOutsideDiscoveryPath-register /usr/sap/ccms/apmintroscope/sap/sld/sldds.xml
The second call sends the data to the sldregtarget as defined when executed Outside discovery: saphostctrl: hostctrl/exe/saphostctrl-function ExecuteOutsideDiscovery-xmlfromconfig-sldreg
Check <SID>_ISMetricCollectionDefinition.xml on the ISEM (location is specified in /wily/apmintroscope/sap/ <SID>_srsm.e2emai.properties)
Check by executing ListDatabaseMetrics with the -format table option.
/usr/sap/hostctrl/exe/saphostctrl -function ListDatabaseMetrics -dbname <DBSID> -dbtype <DBTYPE> -format table
If the command produces output like shown below, metrics can be collected from the database.
Name |MetricID |Resource |SystemHost|SystemID |SystemType|Timestamp |Unit |Value |Rating|
DB.DB6.AutomaticStorage.AdHoc |DB.DB6.AutomaticStorage.AdHoc |DBPARTITIONNUM=0|PATH=/db2/HA5/sapdata1|db6xen023 |HA5/db2ha5|Database |2017-09-26 10:10:21.596505|Percent |75.43 |1 |
DB.DB6.AutomaticStorageFillRatio.AdHoc|DB.DB6.AutomaticStorageFillRatio.AdHoc|DBPARTITIONNUM=0|PATH=/db2/HA5/sapdata3|db6xen023 |HA5/db2ha5|Database |2017-09-26 10:10:21.596505|Percent |75.43 |1 |
DB.DB6.AutomaticStorageFreeMB.AdHoc |DB.DB6.AutomaticStorageFreeMB.AdHoc |DBPARTITIONNUM=0|PATH=/db2/HA5/sapdata1|db6xen023 |HA5/db2ha5|Database |2017-09-26 10:10:21.596505|Megabytes|14857.37|1 |
DB.DB6.BufferpoolCacheHitRatio.24h |DB.DB6.BufferpoolCacheHitRatio.24h |MEMBER=0|BUFFERPOOL=IBMDEFAULTBP |db6xen023 |db2ha5/0 |Instance |2017-09-26 10:00:00.439458|Percent |98.59 |1 |
DB.DB6.CatalogCacheHitRatio.24h |DB.DB6.CatalogCacheHitRatio.24h |MEMBER=0 |db6xen023 |db2ha5/0 |Instance |2017-09-26 10:00:00.440820|Percent |99.92 |1 |
DB.DB6.Deadlocks.24h |DB.DB6.Deadlocks.24h | |db6xen023 |HA5/db2ha5|Database |2017-09-26 10:00:00.440820|Count |0 |1 |
DB.DB6.ExclusiveLockEscalations.24h |DB.DB6.ExclusiveLockEscalations.24h | |db6xen023 |HA5/db2ha5|Database |2017-09-26 10:00:00.440820|Count |0 |1 |