OpenText Analytics Database 26.2.x – Set up Vertica on-premises

Setup: Installation overview and checklist

Mon, 01 Jan 0001 00:00:00 +0000

Carefully review and complete the installation tasks in all sections of this topic.

Important notes

Vertica supports only one running database per cluster.
Vertica supports installation on one, two, or multiple nodes. The steps for Installing Vertica are the same, no matter how many nodes are in the cluster.
Prerequisites listed in Before You Install Vertica are required for all Vertica configurations.
Only one instance of Vertica can be running on a host at any time.
To run the install_vertica script, as well as adding, updating, or deleting nodes, you must be logged in as root, or sudo as a user with all privileges. You must run the script for all installations, including upgrades and single-node installations.

Installation scenarios

The three main scenarios for installing Vertica on hosts are:

A single node install, where Vertica is installed on a single host as a localhost process. This form of install cannot be expanded to more hosts later on and is typically used for development or evaluation purposes.
Installing to a cluster of physical host hardware. This is the most common scenario when deploying Vertica in a testing or production environment.
Installing to a local cluster of virtual host hardware. This is similar to installing on physical hosts, but with network configuration differences.

Before you install

Before You Install Vertica describes how to construct a hardware platform and prepare Linux for Vertica installation.

These preliminary steps are broken into two categories:

Configuring Hardware and Installing Linux
Configuring the Network

Install or upgrade Vertica

Once you have completed the steps in the Before You Install Vertica section, you are ready to run the install script.

Installing Vertica describes how to:

Back up any existing databases.
Download and install the Vertica RPM package.
Install a cluster using the install_vertica script.
[Optional] Create a properties file that lets you install Vertica silently.

Post-installation tasks

After You Install Vertica describes subsequent steps to take after you've run the installation script. Some of the steps can be skipped based on your needs:

Install the license key.
Verify that kernel and user parameters are correctly set.
Install the vsql client application on non-cluster hosts.
Resolve any SLES 11.3 issues during spread configuration.
Use the Vertica documentation online, or download and install Vertica documentation. Find the online documentation and documentation packages to download at https://docs.vertica.com/latest.
Install client drivers.
Extend your installation with Vertica packages.
Install or upgrade the Management Console.

Setup: Before you install Vertica

Mon, 01 Jan 0001 00:00:00 +0000

Complete all of the tasks in this section before you install Vertica. When you have completed this section, proceed to Install Vertica using the command line.

Setup: Install Vertica using the command line

Mon, 01 Jan 0001 00:00:00 +0000

This section describes how to install the Vertica software on a cluster of nodes. It assumes that you have already performed the tasks in Before You Install Vertica, and that you have a Vertica license key.

To install Vertica, complete the following tasks:

Special notes

Downgrade installations are not supported.
Be sure that you download the RPM for the correct operating system and architecture.
Vertica supports two-node clusters with zero fault tolerance (K=0 safety). This means that you can add a node to a single-node cluster, as long as the installation node (the node upon which you build) is not the loopback node (localhost/127.0.0.1).
The installer performs platform verification tests that prevent the install from continuing if the platform requirements are not met. These tests ensure that your platform meets the hardware and software requirements for Vertica. You can simply run the installer and view a list of the failures and warnings to determine which configuration changes you must make.

Setup: After you install Vertica

Mon, 01 Jan 0001 00:00:00 +0000

The tasks described in this section are optional and are provided for your convenience. When you have completed this section, proceed to one of the following:

Install client drivers

After you install Vertica, install drivers on the client systems from which you plan to access your databases. Vertica supplies drivers for ADO.NET, JDBC, ODBC, OLE DB, Perl, and Python. For instructions on installing these drivers, see Client drivers.

Install the license key

If you did not supply the -L parameter during setup, or if you did not bypass the -L parameter for a silent install, the first time you log in as the Database Superuser and run the VerticaAdministration tools or Management Console, Vertica requires you to install a license key.

Follow the instructions in Managing licenses in the Administrator's Guide.

Create a database

To get started using Vertica immediately after installation, create a database. You can use either the Administration Tools or the Management Console. To create a database using MC, refer to Creating a database using MC. For instructions on creating a database with admintools, see Creating a database.

Install vsql client application on non-cluster hosts

You can use the Vertica vsql executable image on a non-cluster Linux host to connect to a Vertica database.

On Red Hat, CentOS, and SUSE systems, you can install the client driver RPM, which includes the vsql executable. See Installing the vsql client for details.
If the non-cluster host is running the same version of Linux as the cluster, copy the image file to the remote system. For example:
```
$ scp host01:/opt/vertica/bin/vsql .$ ./vsql
```
If the non-cluster host is running a different distribution or version of Linux than your cluster hosts, you must install the Vertica server RPM in order to get vsql:
1. Download the appropriate RPM package by browsing to Vertica website. On the Support tab, select Customer Downloads.
2. If the system you used to download the RPM is not the non-cluster host, transfer the file to the non-cluster host.
3. Log into the non-cluster host as root and install the RPM package using the command:
```
# rpm -Uvh filename
```
  Where filename is the package you downloaded. Note that you do not have to run the install_vertica script on the non-cluster host to use vsql.

Notes

Use the same Command-line options that you would on a cluster host.
You cannot run vsql on a Cygwin bash shell (Windows). Use ssh to connect to a cluster host, then run vsql.

vsql is also available for additional platforms. See Installing the vsql client.