[Solved] Troubleshooting note for SAP HANA platform lifecycle management tool hdblcm

An error has occured in SAP HANA platform lifecycle management tool hdblcm

This note describes some common problems, which could possibly occur and the steps you can do to troubleshoot and resolve them.
You could also first check the SAP note, describing known problems with hdblcm Also see – hdblcm not installed
– http://service.sap.com/sap/support/notes/2082466

1. You are using the SAP HANA database lifecycle manager (hdblcm) Web UI from the SAP HANA Studio.

1.1. The Web UI does not open and you get error: Error occurred while trying to start SAP HANA lifecycle manager
1.1.1. In SAP HANA Studio, in the view “Systems”, when you mouse over the system you get error: SAPControl request failed. Bad response: (503Service Unavailable or you are able to open the Web UI via standalone browser at URL https://<hostname>:1129/lmsl/HDBLCM/<SID>/index.html
      1.1.1.1. Make sure that there is connection to the host
1.1.1.2. Check your Network proxy settings
1.1.2. Try to open the Web UI via standalone browser via http at URL http://<hostname>:1128/lmsl/HDBLCM/<SID>/index.html. Use this URL just for troubleshooting purposes, because the communication channel with the HANA server is not secured.
1.1.2.1. It works – see Resolving problems with SAP Host Agent integration
1.1.2.2. You don’t get any response from the server – see Resolving problems with access to the SAP Host Agent
1.1.2.3. You get a page not found message (404 Not Found) or some other strange error message – see Resolving problems with hdblcm installation
1.2. You see only blank editor or the loading screen and nothing else happens – see Resolving problems with SAP HANA Studio integration and Browser compatibility
1.3.1. Make sure that your browser is supported – see Browser compatibility
1.3.2. See section How to trace errors and collect log files for instructions on how to collect the needed logs, so that your problem gets resolved faster
1.4. The main page opens, but when you click on a tile, an error dialog occurs – see Resolving problems with hdblcm installation
1.5. Other problem – see How to trace errors and collect log files

2. You are using the SAP HANA database lifecycle manager (hdblcm) Web UI from standalone web browser

2.1. You don’t get any response from the server
2.1.1. Try to open the Web UI via HTTP at URL http://<hostname>:1128/lmsl/HDBLCM/<SID>/index.html. Use this URL just for troubleshooting purposes, because the communication channel with the HANA server is not secured.
2.1.1.1. It works – see Resolving problems with SAP Host Agent integration
2.1.1.2. You don’t get any response from the server – see Resolving problems with access to the SAP Host Agent
2.1.1.3. You get a page not found message (404 Not Found) or some other strange error message – see Resolving problems with hdblcm installation
2.2. You get a page not found message (404 Not Found) or some other strange error message – see Resolving problems with hdblcm installation
2.3. You see only the loading screen and nothing else happens
2.3.1. Make sure that your browser is supported – see Browser compatibility
2.3.2. See section How to trace errors and collect log files for instructions on how to collect the needed logs, so that your problem gets resolved faster
2.4. The main page opens, but when you click on a tile, an error dialog occurs – see Resolving problems with hdblcm installation
2.5. Other problem – see How to trace errors and collect log files

3. You are using the SAP HANA database lifecycle manager (hdblcm) in console or native GUI mode

See How to trace errors and collect log files

If you did not find a solution for your problem in this note, please open a new incident on HAN-LM-PLT component. Read the section How to trace errors and collect log files to see where to collect the needed log files from.

Other Terms

hdblcm troubleshooting, hdblcm WEB UI troubleshooting, SAP HANA platform lifecycle management tool, SAP HANA installation, update, and configuration, SAP HANA DB, SAP HANA Database, SAP Host Agent, NewDB, in-memory database, Hybrid database

 

Solution

 

Resolving problems with SAP HANA Studio integration

  • HANA Studio is installed on a Microsoft Windows operating system
On Microsoft Windows the SAP HANA Studio uses Internet Explorer as a rendering engine. Check theBrowser compatibility section of this note and make sure that your Internet Explorer meets the minimal required version.
  • HANA Studio is installed on a SUSE or RedHat 6.5 Linux operating system
1. Install (extract) XULRunner version 10.0.4esr into a local directory
2. Edit the file hdbstudio.ini and add the following two JAVA VM arguments:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
-Dorg.eclipse.swt.browser.XULRunnerPath=<path to xul runner>

Resolving problems with SAP Host Agent integration

Resolving problems with access to the SAP Host Agent
For some reason you don’t have access to the SAP Host Agent, which serves the Web UI of SAP HANA database lifecycle manager (hdblcm). There might be several reasons for this:
1. Make sure that you have typed the HANA host name correctly in hdblcm Web UI url
2. Make sure that port 1129 is open and that there is no installed software which prevents access to this port
3. Make sure that there is a SAP Host Agent installed and running on the HANA host.
SAP HANA database lifecycle manager’s Web UI requires SAP Host Agent to be able to operate. Log on to the HANA host via SSH and type in the console: /usr/sap/hostctrl/exe/saphostexec -status
3.1. If SAP Host Agent is not running, start it using the command /usr/sap/hostctrl/exe/saphostexec -restart and make sure it has started using the -status option again
3.2. If the path /usr/sap/hostctrl/exe/saphostexec does not exist, this means that there is no SAP Host Agent installed on the system. In order to install it, use the following command:
/usr/sap/<SID>/SYS/global/hdb/saphostagent_setup/saphostexec -install
After the installation you need to configure HTTPS access. See section Configuring HTTPS for SAP Host Agent
You need also to configure the SAP Host Agent to serve the hdblcm’s Web UI. See section Resolving problems with the hdblcm installation
4. Try to restart the SAP Host Agent with the following command: /usr/sap/hostctrl/exe/saphostexec -restart
Configuring HTTPS for SAP Host Agent
If the Web UI cannot be open via HTTPS, but opens via HTTP, this means that the SAP Host Agent on the HANA host is not configured to use HTTPS.
In order to enable secure communication with the SAP Host Agent over HTTPS, the SAP Host Agent needs to have a secure sockets layer (SSL) certificate in its security directory.
This certificate is also used by the SAP HANA database lifecycle manager (hdblcm) Web user interface, because the web pages are served by the SAP Host Agent. The SAP HANA database lifecycle manager automates this process and during installation, update, or rename of a system, or during addition of new hosts it generates a self-signed certificate.
In order to use hdblcm to automatically generate a self-signed SSL certificate, execute the following command. The owner of the certificate by default is the SAP HANA host name. If you would like to change it, you can use the –certificate_hostname call option.
<sapmnt>/<SID>/hdblcm/hdblcm –action=update_host [–certificate_hostname=<certificate_hostname>]
If you want to use your own SSL certificates, see SSL Configuration for the SAP Host Agent

Resolving problems with the hdblcm installation

You have access to the SAP Host Agent, but for some reason the SAP HANA database lifecycle manager’s Web UI cannot be opened or you get errors when you click on a tile. Follow the steps below to be able to identify the root cause for the problem.
1. Make sure that you SAP HANA database is on revision 90 or newer.
2. Make sure that hdblcm is installed on the system
By default, during installation or update of a SAP HANA system with hdblcm, the tool installs itself together with the system. It might be the case that your SAP HANA system was installed and/or updated directly with hdbinst or hdbupd. As a result, there might be no hdblcm on the system or its version might be older than the SAP HANA server’s version. Check if the following path exists: <sapmnt>/<SID>/hdblcm
2.1 If it does not exist, this means that hdblcm is not installed.
In order to install it, you need the SAP HANA server installation kit, which was last used to install or update the SAP HANA system. Make sure that the version in the installation kit manifest matches the version of the installed HANA system. Run the following command from the installation kit:
./hdblcm –sid=<SID> –action=update –components=hdblcm
2.2 If it exists, make sure that its version matches the SAP HANA database version. If the versions differ, follow the instruction in step 2.1 to update hdblcm.
Check hdblcm version: cat <sapmnt>/<SID>/hdblcm/instruntime/manifest | grep fullversion
Check SAP HANA Database version: cat <sapmnt>/<SID>/HDB<instance_number>/exe/manifest | grep fullversion
3. Make sure that you have the correct SAP Host Agent version
Make sure that you have the correct SAP Host Agent version. The minimal required version of the SAP Host Agent is 197. You can check the version of your SAP Host Agent via the following command:
/usr/sap/hostctrl/exe/saphostexec -version
If the version is lower than 197, upgrade you SAP Host Agent using the following command:
/usr/sap/<SID>/SYS/global/hdb/saphostagent_setup/saphostexec -upgrade
By default, and if it is not explicitly switched off, during update of a SAP HANA system, the SAP Host Agent will be updated as well.
4. Check that there is a correct signature file in hdblcm installation directory
If several SAP HANA component SAR archives have been downloaded and extracted into a single directory, it might happen that the SIGNATURE.SMF file of the SAP HANA Database archive gets overriden by some other component’s signature. As a result, the wrong SIGNATURE.SMF gets copied to the <sapmnt>/<SID>/hdblcm directory, hence SAP Host Agent is not able to verify and deploy the hdblcm tool.
Open the file <sapmnt>/<SID>/hdblcm/SIGNATURE.SMF and check if there are entries inside for file paths, starting with SAP_HANA_DATABASE/server/* (for example SAP_HANA_DATABASE/server/manifest). If there are no such entries or there is no SIGNATURE.SMF file at all, see the section Repairing installations with missing signature. The problem is most probably caused by improper extraction of the SAP HANA compoennt archives before installation or upgrade. See section How to prepare SAP HANA packages for installation or update for the correct preparation procedure.
5. Configure SAP Host Agent to serve the Web UI
By default, during installation or update of the SAP HANA system, hdblcm configures the SAP Host Agent to serve its Web UI. For some reason this might have not happened, for example because of a failure during the installation/update procedure or if the SAP Host Agent had been manually reinstalled afterwards.
To update the integration of hdblcm on the SAP HANA host, run the following command:
<sapmnt>/<SID>/hdblcm/hdblcm –action=update_host
6. Restart SAP Host Agent
/usr/sap/hostctrl/exe/saphostexec -restart

Browser compatibility

Make sure that you are using one of the following browsers, depending on the operating system:
  • Microsoft Windows
    • Internet Explorer – Version 9 or higher. If you are running Internet Explorer version 9, make sure that your browser is not running in compatibility mode with your SAP HANA host. You can check this in your browser by choosing  Tools  Compatibility View Settings.
    • Mozilla Firefox – Latest version and Extended Support Release
    • Google Chrome – Latest version
  • SUSE Linux – Mozilla Firefox with XULRunner 10.0.4 ESR
  • Mac OS – Safari 5.1 or higher
For more information about supported Web browsers for the SAP HANA database lifecycle manager Web interface, see the browser support for sap.m library in the SAPUI5 Developer Guide.

How to trace errors and collect log files

This section describes how to collect the information, needed by the SAP support to root cause and fix your problem.
1. If the problem is in the Web user interface, like:
  • You see the loading page and it never loads
  • The user interface freezes and you don’t see any progress updates
  • The content is not rendered correctly
In such situations it would be very helpful for the support if you could open an (error) console of your browser and check for error there. If you see any errors in the console, please attach them to the incident.
Another very helpful information for the root cause analisys would be look at the server requests that your Web browser performs and if there are any failed requests – attach them to the incident as well. Usually this can be monitored via the browser developer tools.
2. If you are using the Web user interface and you get an error, which does not report any meaningful information you can log on to the system via SSH and check the following log files for any meaningful information, which could help you find the root cause and resolve the the issue:
a. Check the hdblcmweb trace file (hdblcmweb.trc), located at /var/tmp/hdb_<SID>_hdblcmweb_*
b. Check the SAP Host Agent trace file, located at /usr/sap/hostctrl/work/sapstartsrv.log
In order to enable the traces of the SAP Host Agent, edit the host profile /usr/sap/hostctrl/exe/host_profile and add the following lines:
hostexec/trace = 3
service/trace = 3
Restart the SAP Host Agent with the following command: /usr/sap/hostctrl/exe/saphostexec -restart
Reproduce the error and check the trace file
3. If you get an error during the execution of a process, you could check the error logs of the different hdb* lifecycle management tools, located in /var/tmp. In general, the user interface should have indicated the exact log file, containing the error, but sometimes these logs are located on the remote hosts and are not directly accessible from the Web/Native GUI interface.
When analyzing the logs we recommend that you start with the log file of the step/component, indicated in the UI as failed. If you don’t find the reason for the failure there, check the hdblcm log. It contains the output of all orchestrated component tools and there it is easy to spot where the problem for the failure is. If any of the orchestrated tools has failed, it must have reported the location of its own log file in a line, starting with “Log file writtern to …”. Pay attention that some of the log files will be located on the other hosts of the system. The same applies to the component tools, because some of them also orchestrate other tools. So in general, starting from the hdblcm log, you should be able to get to all other log files.
4. If you are using the SAP HANA database lifecycle manager (hdblcm) in console or native GUI mode and you don’t find a log file, please enable the traces and reproduce the problem. The traces can be enabled by setting the environment variable HDB_INSTALLER_TRACE_FILE=<file>.
5. Check the troubleshooting note for known problems with hdblcm -http://service.sap.com/sap/support/notes/2082466

Repairing installations with missing signature

1. Find the original SAR archive for the SAP HANA Server component, which was used for the system installation or update. It must match the revision of the SAP HANA Database
2. Extract the .SAR archive to a temporary location
3. Go to this temporary directory. Inside you should find:
  • file SIGNATURE.SMF
  • directory SAP_HANA_DATABASE
4. Copy the SIGNATURE.SMF file to:
  • /<sapmnt>/<SID>/hdblcm/SIGNATURE.SMF
  • /<sapmnt>/<SID>/global/hdb/SIGNATURE.SMF
  • /<sapmnt>/<SID>/global/hdb/install/bin/SIGNATURE.SMF
5. Adjust file permissions and ownership:
  • chmod 644 /<sapmnt>/<SID>/hdblcm/SIGNATURE.SMF
  • chown <sid>adm:sapsys /<sapmnt>/<SID>/hdblcm/SIGNATURE.SMF
  • chmod 644 /<sapmnt>/<SID>/global/hdb/SIGNATURE.SMF
  • chown <sid>adm:sapsys /<sapmnt>/<SID>/global/hdb/SIGNATURE.SMF
  • chmod 644 /<sapmnt>/<SID>/global/hdb/install/bin/SIGNATURE.SMF
  • chown root:root /<sapmnt>/<SID>/global/hdb/install/bin/SIGNATURE.SMF
6. Execute as root the following command on all hosts of the system: /<sapmnt>/<SID>/hdblcm/hdblcm –action=update_host
7. Remove the not needed contents of the extracted .SAR archive from the temporary directory

How to prepare SAP HANA packages for installation or update

In order to ensure security during its operation, SAP HANA database lifecycle manager (hdblcm) needs to work with SAP HANA database component, officially signed by SAP. The signature of the component contents is contained in a file, called SIGNATURE.SMF, which is produced by SAPCAR during extraction of the archive.
If for some reason you cannot get this signature file or the SAP HANA database component, which you use had not been signed with the official SAP signature, you can still perform the installation or update. The database itself will not be affected by the missing signature. To do so, you need to use hdblcm or hdblcmgui as root user and pass the parameter –ignore=check_signature_file on the command line. If you do so, the following features of the database lifecycle management tools (hdblcm, hdbinst, hdbupd, etc.) cannot be used afterwards until the next database update with valid signature.
  • Web user interface
  • Execution as <sid>adm user
  • Remote execution via SAP Host Agent
The easiest way to prepare for update is to use the attached shell script (hdblcm_prepare.sh). Just place it in the directory with the downloaded .SAR packages, give it execute permissions and run it.
If you want to prepare the packages manually, please follow the procedure below:
1. Create a local directory for the downloaded packages. Example: /hana/local/downloads
2. Copy the SAP HANA packages to the local directory
3. Create a directory, in to which the package contents can be unpacked (referred to below “extraction directory”). Example: /hana/local/downloads/extracted
4. For each archive do the following:
4.1 Unpack the archive in to the extraction directory, passing the option -manifest SIGNATURE.SMF to SAPCAR
4.2 If there is a SIGNATURE.SMF file in the extraction directory, move it to the component subfolder (e.g. SAP_HANA_DATABASE, SAP_HANA_CLIENT, etc.)
5. You can now update the SAP HANA system with the SAP HANA database lifecycle manager (hdblcm)

Leave a Reply