Describing Advanced Installation Options

The hdblcm tool on the command line can be used in the two different ways. Both methods can be used in a batch mode, which does not require any user interaction, as the following options show:

• Command line options (in batch mode)

• Configuration file (in batch mode)

When using the option --batch, the parameters specified on the command line are used and the default parameters are accepted without conformation. As shown in the figure, it is even possible to provide the mandatory parameters for the passwords on the command line. However, avoid providing the password on the command line like this because the statement is stored in the history file on Linux. Instead, create a configuration file that holds all the required parameters and values, including passwords. Alternatively, there are safeguarding options to store the passwords in an explicit xml-file and start the installation in batch mode with a parameter, which reads the passwords from this file.

If you do not use the --batch option, the SAP HANA installation is performed semi-automatically. The parameters specified on the command line are used, but the installer must still confirm the default parameter values.

The SAP HANA database lifecycle manager (HDBLCM) uses default values during installation, unless you decide to change them via the command line options, or via a configuration file that contains the parameters you want to change.

To generate a configuration file template using the SAP HANA platform lifecycle management tool, execute the following command:

1
./hdblcm --dump_configfile_template=/root/hdblcmTemp.cfg

The parameter template file lists parameters in sections like General, Server, Client, and some others. Within those sections, the corresponding parameters can be found with a short description and possible values, which is useful as a kind of value help. For some generic use cases, this function might be sufficient. Nevertheless, the parameters are described in the SAP HANA Server Installation and Update Guide.

To perform an automated installation with the SAP HANA lifecycle management hdblcm tool, you must combine the configuration file and the batch mode.

Note that until now, you had to enter passwords interactively or specify them on the command line. Batch mode is designed to automate the installation process.

Batch mode runs the installer without asking for any confirmation or parameter entry. This allows the installation to run to completion without any user interaction. It can be started from the command line with the use of a configuration file.

With the configuration file and batch mode, the SAP HANA installation is installed completely without user interaction. This is useful if you want to set up many systems with a standard setup, or if you want to redeploy a system on a weekly basis because of system copies.

Because hdblcm and hdblcmgui are wrapper tools, in some troubleshooting cases, you can pass component options on to the underlying component tools (hdbinst or hdbupd) in combination with the call to the hdblcm or hdblcmgui SAP HANA lifecycle management tools. This might be helpful in case there is a problem with the installation and detailed information from involved components is needed.

By using this function, various use cases are supported:

• Get more detailed information about the component(s), which caused the failed installation or update

• Use parameters to overcome the problem caused by a component (for example skip a step or set a port via a parameter)

• Stop or deactivate a specific step or task executed by a underlying component in the installation or update procedure (for example no start of SAP HANA at the end of an update procedure or skip a specific check)

To view the available underlying component parameters as extended help output, use the pass_through_help parameter. Specify the action parameter and --help or -h in combination with pass_through_help.

To view the help output for the installation or the update pass_through_help parameters, use the following syntax:

123
--action=[install|update] --pass_through_help --help
or
--action=[install|update] --pass_through_help -h

These operating system commands can be used to identify the wide range of parameters, which are used in the installation and update procedure, including the syntax, a description, and the use case (install, update, product-specific usage) of an involved component, as well as the XML tags used for the password input stream. At the end of the output environment variables are mentioned to enable the tracer or to create a copy of the log directory.

In addition to the main components installed in the default file systems, you can also locate the temporary files from the SAP HANA system. They can be found in the directories shown in the figure, SAP HANA Temporary Files Location.

If the installer crashes or loops, it may make sense to trace the installer until the problem occurs, open a CSS ticket, and attach the trace file for further analysis. You can switch on the installer trace by setting the environment variable HDB_INSTALLER_TRACE_FILE to <tracefilename>. The directory containing the trace file must already exist.

The SAP HANA lifecycle management tools hdblcm and hdblcmgui write log files during installation. The most recent log file is always available under /var/tmp/hdblcm.log or /var/tmp/hdblcmgui.log. Additionally, a copy of the log files is archived in the directory hdb_<SID>_hdblcm_<action>_<timestamp>.

Since the SAP HANA lifecycle management tools hdblcm and hdblcmgui are wrappers for underlying component installers, it is also possible to check the component logs. It is recommended to review and analyze the SAP HANA lifecycle management tools hdblcm and hdblcmgui logs first. Once the source of the problem is narrowed down to a specific component, then the component logs can be further analyzed.

The component log files are stored in the following path:

12
/var/tmp/hdb_<SID>_hdblcm_<action>_<timestamp> 
where <action> :: = install | update | addhost | uninstall | and so on.

The following log files are written while performing the <action>:

• <hdbcommand>.log: Can be read using a text editor

• <hdbcommand>.msg: XML format for the display in the installation tool with the GUI

• <hostname>_tracediff.tgz: Provides a delta analysis of the original trace files, and makes a detailed analysis easier

After the trace is generated, you can open it and check the trace file for error messages. If needed, open an SAP support ticket and attach the trace file for further analysis.