Note: this blog is part of Prepare a HANA System for Lumira Server Install.
When: Installing a SAP HANA Lifecycle Manager.
Cause: The SAP HANA Lifecycle Manager software package folder is not well prepared. The SAP HANA Lifecycle Manager .SAR file is also required to be copied into the extracted folder.
Action: Copied the .SAR into the extracted folder and retry. See the example in part 2 of Prepare a HANA System for Lumira Server Install.
When: During the installation phase of SAP SAL AFL.
Cause: Most likely the software package files were extracted at Windows and transferred to Linux thus losing all permission information.
Action: Run "chmod -R 777" on the SAP SAL AFL software package folder and retry.
When: Launching SAP HANA Lifecycle Manager from HANA Studio.
Cause: There is no SAP HANA Lifecycle Manager installed or SAP Host Agent is not running properly.
Action: Check if SAP HANA Lifecycle Manager is installed. Also check SAP Host Agent's TCP port 1128 (for HTTP) and 1129 (for HTTPS) are listening. If 1129 is not listening, one must properly configure SSL for SAP Host Agent.
When: Deploying Lumira Server.
Cause: SAP SAL AFL is not installed. Do not confuse by SAP HANA AFL - it is a different component from SAP SAL AFL.
Action: Install SAP SAL AFL and retry.
When: Deploying Lumira Server.
Cause: The SAP HANA Lifecycle Manager is an old version.
Action: Upgrade SAP HANA Lifecycle Manager to the required or the latest version/SP/patch level and retry.
When: Installing required components for Lumira Server through upgrade install.
Cause: The existing old HANA system has a SAP AFL plugin installed but not upgraded yet.
Action: Upgrade the SAP AFL plugin to the target level together with the required components. See the example in part 3.2 of Prepare a HANA System for Lumira Server Install.
When: Installing SAP HANA Lifecycle Manager through hdbinst.
Cause: No SAP HOST AGENT exists.
Action: Install SAP HOST AGENT at the same installation: ./hdbinst --hlm_archive=/IMDB/SAPHANALM07_10-10012745/SAPHANALM07_10-10012745.SAR --host_agent_package=/IMDB/saphostagentrpm_182-20005731.rpm
When: Installing SAP HANA Lifecycle Manager through hdblcmgui and enter path of HOSTAGENT.TGZ as parameter as shown above.
Cause: TGZ is not recognized by the installer.
Action: Download and use the .rpm version of SAP HOST AGENT.
When: Installing SAP HANA Lifecycle Manager through hdblcmgui and enter a correct path of .rpm version of SAP HOST AGENT as parameter.
Cause: To be investigated
Action: A workaround is to use hdbinst instead of hdblcmgui.
When: The SAP HANA Lifecycle Manager is installed successfully but throws this error when clicking Deploy HANA Content or View Installed Products and Software Components. This is observed in HANA rev. 81.
Cause: The signed signature in SIGNATURE.SMF (located in the extracted folder when installing SAP HANA Lifecycle Manager) is bad. One possible reason is that during the preparation phase for installing, an old version of SAPCAR (e.g. release 700) is used to extract the .SAR file which couldn't handle the SIGNATURE.SMF file properly.
Action: Check the version of SAPCAR used and the file size of SIGNATURE.SMF (zero file size is a bad sign) in the extracted folder. Upgrade SAPCAR to the latest version (e.g. release 720) and re-extract the .SAR file then update/reinstall SAP HANA Lifecycle Manager.
When: Deploying SAP Lumira Server (e.g. v1.21) with the "hdbalm" tool.
Cause: The HANA user specified by -u option (e.g. user "SYSTEM") doesn't have sufficient right to perform the operation.
Action: In HANA Studio, assign role 'sap.hana.xs.lm.roles::Administrator' to the user and then retry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
24 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
6 | |
6 | |
6 |