Problem: I cannot use HLM to register HANA in SLD.
The most common reason why you cannot use HLM to register HANA in SLD is because HANA wasn't installed using the unified installer. The registration with SLD exists only with unfied installer. You can register HANA manually in SLD. To do this the first step is to check that the parameter sld is set to "enable" in HANA. The parameters in the group 'sld' are usually only maintained if you perform a standard HANA installation. If you didn't chances are good that they are not OK.
Check the parameter in HANA Studio. You might have to add this parameter and also other parameters. For details on the SLD parameters refer to the HANA Administration Guide page 46ff.
After setting this parameter log on to OS level with the user <sid>adm. Change to the global directory (command cdglo) and create the slddest.cfg file for the SLD registration.
Run the SLD registration using the created connectfile.
Problem: The SLD registration file sldreg.xml is not created successfully.
The file sldreg.xml is the basis for the SLD registration. If this file isn't created correctly the SLD registration will fail. The file is usually created in the HANA trace directory.
A known reason for this file failing, could be a missing or inconsistent lm_structure. You will find a corresponding error message in the HANA nameserver trace file.
A possible error message could be: Error during CIM model load: Error while parsing XML file landscapeDescription.xml in /hana/shared/<SID>/lm_structure/
With HANA SP 06 the lm_structure moved into the HLM. If you HANA wasn't installed using the unified installer this information might not be known to HANA and it searched for the lm_structure under /usr/sap/SID/lm_structure.
Please refer to the SAP note 2270093 for solution.
To address the issue, another possible solution could be, to create a sym-link to the actual lm_structure location e.g. /sapmnt/<SID>/lm_structure.
Problem: You want to activate the new Embedded Statistics Server for SAP HANA and want to know if this is supported by SAP Solution Manager Monitoring
With SAP HANA SPS 7 (rev 74) a new embedded statistics server is available. The new statistics service replaces the old statistics server, it provides the same functions but is no longer implemented as a separate server process. The data held in the persistence of the statistics server is transferred to the persistence of the master index server. The migration procedure is described in SAP note 1917938.
In terms of monitoring SAP HANA with SAP Solution Manager the following things have to be considered:
- DBACockpit or SAP Solution Manager Monitoring are supported with at least SAP_BASIS 13 (which is part of SAP Solution Manager 7.1 SP10 or higher)
- For SAP_BASIS 13 and 14 (Solution Manager SP10+11) you need to implement SAP note 1925684
- Solution Manager database user needs additional rights to execute the necessary procedures in the _SYS_STATISTICS schema. See SAP note 1917938 for details.
Problem: SLD Registration for SAP HANA seems incomplete
You try to register SAP HANA in SLD. The sldreg.xml is created successfully and the sldreg.log doesn't show error. However the entry for the system in SLD seems to be incomplete (e.g. missing associations for the HANA Database Services. You check the SLD log and you find entries like this:
This means that even if your sldreg.xml is created successfully in HANA it is not completely readable for the SLD. In the example about the sldreg.xml contained an entry for a TestProduct1 which was manually created in HANA Application Lifecycle Management. The SLD log will usually tell you what the problem is.
In this case the problem could be fixed by opening the HANA Application Lifecycle Management tool and delete the manually created product. Open the URL http://<WebServerHost>:80<SAPHANAinstance>/sap/hana/xs/lm and switch to the PRODUCTS tab. Here you see the TestProduct1.
Delete it and also delete the sldreg.xml. Retrigger the SLD data transfer (e.g. by toggling the parameter sld -> enable in HANA Studio.
Problem: The activity "Extractor Setup" in the Managed System Setup fails
You try to run the activity "Extractor Setup" in the Managed System Setup step "Configure Automatically" (or "Finalize Configuration" as of SP12). The activity ends with the following error:
- No Extractor was activated for <SID>. Please check if the Technical System has been defined as described in SAP Note 1472465.
The following screenshot describes the error message in the log details:
Solution: Refer to SAP note 2053866 and apply its solution.
Problem: The section "check prerequisites" in the Managed System Setup shows errors
1) When checking the section "Check Prerequisites" in the managed system configuration for the technical system, the following errors are visible:
| The definition of Technical System '<SID>~ABAP' is not correct: '<SID>~ABAP': Database 'BDH' must have at least one Host. |
| '<SID>~ABAP': Database '<SID>' must have at least one Host. |
| Technical System definition issue: check LMDB and SLD |
2) When checking the section "Check Prerequisites" in the managed system configuration for the HANA DB, the following errors are visible:
| The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': Technical System must be installed on at least one Host. |
| The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': Database 'BDH' must have at least one Host. |
| The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': No Software Component Version found. |
| The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': No Product Version found. |
This issue happens when not all data related to the HANA DB is reported to the SLD. The following KBA describes this issue in details:
2201640 - The definition of Technical System '<SID>~HANADB' is not correct: '<SID>~HANADB': Technical System must be installed on at least one Host.
Solution: Perform the HANA DB registration in SLD as described under the section 'Register HANA in SLD' in this wiki page.
Problem: After upgrading SAP HANA to rev. 97 or higher the metrics in Solution Manager turn grey
With the upgrade to SAP HANA to rev 97 or higher the embedded statistics server is activated automatically. This requires additional privileges for the monitoring user for SAP Solution Manager in SAP HANA. These privileges cannot be added automatically during the upgrade but have to be added manually after the upgrade of SAP HANA, after the embedded statistics server is activated. Please add additional rights to execute the necessary procedures in the _SYS_STATISTICS schema. See SAP note 1917938 for details.
Problem: Solution Manager system log (SM21) shows 'Error => SQL PREPARE on connection 1, rc=258 (insufficient privilege: Not authorized)' after the Managed System Configuration for the HANA DB
After perform the Managed System Configuration for the HANA Database the System Log (SM21) shows the errors:
- Error => prepare() of C_0018, rc=1, rcSQL=258 (insufficient privilege: Not authorized)
- Error => SQL PREPARE on connection 1, rc=258 (insufficient privilege: Not authorized)
Check note 1917938 for the solution, grant described authorizations for the _SYS_STATISTICS schema for the HANA DB user.
Problem: Multi-host Multi-tenant HANA DB misses HDB instances in LMDB
When you register your multi-tenant HANA DB that runs on multiple hosts in SLD you notice that only one HDB instance is visible in LMDB even though the HANA DB runs on more than one host. Also in SLD you see that only one HDB Instance is associated with the SYSTEMDB and the tenants.
The reason is an error during the creation of the sldreg.xml file. This error is fixed but not shipped yet. Until it can be shipped you have to correct this error manually.
After the first SLD registration of your multi-tenant HANA system please turn of the automatic SLD registration but setting the sld-enable parameter to "no" in the SYSTEMDB.
Now you have to adjust the sldreg.xml and correct the entry property merge_roots for each HDBServer_SubDatabase section. Set it from FALSE to TRUE.
The file is usually located in the trace directory of the host that runs that master nameserver, e.g. /usr/sap/AS1/HDB21/ls80012/trace. As <sid>adm you can use command cdtrace to jump there.
After you have placed the changed file in the trace folder you have to run sldreg manually to trigger the re-registration in SLD. You cannot do it via HANA Studio, because this would automatically trigger the creation of a new sldreg.xml which again would contain the error you just fixed.
The sldreg executable is known to <sid>adm and the slddest.cfg is usually located in the /usr/sap/<SID>/SYS/global directory. As <sid>adm use command cdglo to jump there.
Run the command: sldreg -connectfile /usr/sap/AS1/SYS/global/slddest.cfg -file /usr/sap/AS1/HDB21/ls80012/trace/sldreg.xml -usekeyfile
Now the system should have both instances in SLD.
After the next LMDB sync (or after you force a resync for the system) you should see both instances for the SYSTEMDB and the tenants as well.
It is important that you leave the automatic SLD data transfer turned off until the fix is shipped. Otherwise the next automatic data transfer will overwrite the correction 
Problem: Wrong DB name in System Landscape Directory
You run SAP HANA database Revision 110 - 122.01 and notice that the DB name in the SLD in not correct. Or you run a HANA SR cluster and notice that the SLD association SAPIdenticalDatabaseSystem is not created as expected. The reason for this is that the sldreg.xml is created with an incorrect entry. Please refer to SAP note 2303938 for a manual workaround.