Installing the Vertica Database at the Command Line
The packaging script should contain commands to execute the Vertica installation procedure.
Important: Vertica must be installed separately for each user. Do not create a system image for subsequent installations, which may cause all users to use the same SSH keys. This situation can result in serious security issues.
The commands in the packaging script should perform the following tasks:
- Login as the root user.
- Create a properties file that enables non-interactive setup by supplying the parameters you want the Vertica database to use. The properties file is described inInstalling Vertica Silently in Installing Vertica.
- Install the database by running the
install_vertica
script, as described in Installing Vertica Silently in Installing Vertica. - Make sure to run the scripts with the
-y
parameter to avoid the script asking for EULA agreement. - On a single-node installation, consider using the host name or IP address instead of localhost or 127.0.0.1 because of the following limitations:
- The
-s
parameter is required for multi-node installations. On single-node installations the parameter is optional, and the default islocalhost
. However, if you plan to expand to additional hosts later, you must use the-s
parameter. If you do not use the-s
parameter, your Vertica installation cannot be upgraded to a multi-node deployment. - On a single-node localhost installation, the installer does not set up a passwordless ssh. Vertica's backup scripts require that the administrator be able to log into the node via ssh without a password. Consequently, if you want to use the backup scripts, you must manually enable passwordless ssh logins for any single-node installation.
-
If either side of a connection is a single-node cluster installed to localhost, importing and exporting data fails. Failure also occurs if you do not specify a host name or IP address for your single-node cluster.
- To save any warnings that the
install_vertica
script returns, redirect any warning messages to a separate file. To do so, specify theredirect_output = filename
parameter in the properties file. After the installation completes, review the warnings and correct any problems that are critical. - If you need to access the Vertica database from a client application, follow the steps in Installing the Client Drivers in Connecting to Vertica.
- If you need to use the Vertica vsql executable image on a non-cluster Linux host to connect to an Vertica database, follow the steps in Optionally Install the vsql Client Application on Non-Cluster Hosts in Installing Vertica.
-
Disconnect from the Administration Host.
- Unless you used the
-L
parameter in the properties file, install the license key you downloaded.
install_vertica
script creates, create those directories, and make sure that dbadmin owns them.