solman_setup - Database hosts when connecting a managed system

[symon_braunbaer]

Dear Experts,

our systems are running on Hana database. We have 2 or 3 servers per SID as we have configured HSR. When connecting newly installed systems to the Solution Manager, I observe very seldom behavior that defies any logic in the steps Assign Product and Assign Diagnostics Agent. 

Sometimes I only see one database host in the step Assign Product. This is usually due to missing SLD data and when I make sure all DB servers have correctly transferred SLD data, it is fixed and the servers are present there. However, when I see all DB servers correctly in this point, my expectation is to see them also in the step Assign Diagnostics Agent! However, I see all application servers and all DB servers very rarely in this point! It seems to be independent from the point Assign Product and I did not find anything specific, that makes DB Servers appear or disappear from the point Assign Diagnostics Agent!

Could you please kindly explain how this works and most importantly - provide me an answer what exactly do I have to do, in order to see the DB Servers also in the point Assign Diagnostics Agent.

Many thanks for your help and advice!

[Vera_Jiang]

We helped you to accept the answer, since there were no updates after 7 days. You can unaccept it anytime if the answer provided was not helpful enough and you have further questions.

[Vera_Jiang · Accepted solution]

Dear Customer, 

You are correct that in order to view the DB servers in Managed System Configuration, the LMDB must have complete information about the DB, including the "Technical Instances" and "Hosts," unless it is a virtual type of DB. In certain cases, like ORACLE RAC, HANA SR, HANA MDC, etc., there are specific associations that control the behavior, such as SAP_IdenticalDatabaseSystem and SAP_DatabaseReplicationDependency and so on. 

Useful KBA to send DB to SOLMAN: 3232202 - Guided Answer for Troubleshooting for missing or outdated LMDB data suppliers in SAP Solution Manager and SAP Focused Run.

Best regards,
Vera Jiang 

[Vera_Jiang · Accepted solution]

Dear Customer, could you please double check if the JAVA HANA was really sent to the DEV SLD? Please check it via the following trace /usr/sap/<SID>/HDB<nn>/<host>/trace/sldreg.log.

[HakanHaslaman]

Please ensure all hosts are identified and assigned a Diagnostics Agent.

[symon_braunbaer]

Hello Vera, many thanks for your reply! I have to say a lot about our setup, obviously you don't have all necessary input. We have 2 Solution Managers - DEV and PRD. I am connecting all systems to both Solution Managers. Every system is sending SLD data to the DEV SLD and this is then forwarding the data to the productive SLD. I have checked other systems which I recently connected. They ALL have all Hana servers listed under "Assign Diagnostics Agent" in both Solution Managers and they are ABAP systems. Just the last Java system which I have connected is listing the Hana DB servers correctly in the productive Solution Manager and is not listing them in the DEV Solution Manager. This shouldn't be possible, as the DEV SLD is the one getting the SLD data first and they are obviously correct, if it's giving them further to the productive SLD where things are fine! Regarding KBA 3232202 which you recommended: I have checked the SLD definitions for the Hanas of the Java system and of the other previously mentioned ABAP systems. They are absolutely the same having 4 associations: 3 for each of the Hana servers involved in the HSR setup and one for the virtual Hostname that the SAP system is using to contact the DB. I hope I have explained it clear enough, otherwise please feel free to ask as many questions as you need 😉 Many thanks!