Installing Vertica

This section describes how to install the Vertica software on a cluster. It assumes that you have already performed the tasks in the Before You Install section of this document.

Upgrade Installations

If you have previously installed Vertica on any cluster host:

• Vertica V1.0 and earlier must be uninstalled. Databases built with V1.0 are not compatible with newer versions of Vertica. You must rebuild the database using a later version.
• Vertica V1.1 can be upgraded to V1.2. Use the instructions in the V1.2 1-9 documentation.
• Vertica V1.2 can be upgraded to V1.3. Use the instructions in the V1.3.16-0 documentation.
• Vertica V1.3 can be upgraded to V2.0. (Use the instructions below.)

Downgrade Installations

Downgrade installations are not supported.

Installation Procedure

Do not skip any part of this procedure. You must run install_vertica for all installations, including upgrades and single-node installations.

1. Use a Web browser to download the Vertica rpm package from http://www.vertica.com/v-zone/download_vertica. Make sure that the package you download matches the operating system on which you intend to install it, not the machine architecture. The actual package names may be different than those shown here.

   vertica_2.1.GA.i386.RHEL4.rpm vertica_2.1.GA.x86_64.RHEL4.rpm vertica_2.1.GA.i386.RHEL5.rpm vertica_2.1.GA.x86_64.RHEL5.rpm vertica_2.1.GA.i386.SUSE10.rpm vertica_2.1.GA.x86_64.SUSE10.rpm vertica_2.1.GA.i386-FC6_32.rpm vertica_2.1.GA.x86-FC6_64.rpm

   Notes: Only 64-bit packages are supported for production databases. 32-bit packages are provided for testing and evaluation purposes only.

2. If necessary, copy the rpm package to the host on which you intend to install it and use the host's console device or a remote terminal window (xterm, PuTTY, etc.) to perform the installation procedure.

   A host is a computer system with a 32-bit or 64-bit Intel or AMD processor, RAM, hard disk, and TCP/IP network interface (IP address and hostname). Hosts share neither disk space nor main memory with each other.

3. If you have previously installed Vertica V1.3 on any of the hosts in the cluster, use the Administration Tools to shut down any running database. The database must stop normally. You cannot upgrade a database that requires recovery.

   The tools needed for administering a Vertica database are provided in the form of a graphical user interface that allows you to perform various tasks quickly and easily. The tools also provide a convenient way to connect to a database using vsql. Always run the Administration Tools on the Administration Host if possible.

   vsql is the Vertica implementation of psql, a character-based, interactive, front-end that is part of PostgreSQL and used by other database management systems. It allows you to type in SQL statements and see the results. It also provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide variety of tasks.

   $ /opt/vertica/bin/adminTools

   See the Administration Tools Reference for a complete description.

4. Choose a host machine and log in as root (or log in as another user and switch to root):

   $ su - root

   password: <root-password>

   #

   The host that you choose becomes the Administration Host for the purposes of using the Administration Tools.

   The tools needed for administering a Vertica database are provided in the form of a graphical user interface that allows you to perform various tasks quickly and easily. The tools also provide a convenient way to connect to a database using vsql. Always run the Administration Tools on the Administration Host if possible.

   vsql is the Vertica implementation of psql, a character-based, interactive, front-end that is part of PostgreSQL and used by other database management systems. It allows you to type in SQL statements and see the results. It also provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide variety of tasks.

   $ /opt/vertica/bin/adminTools

   See the Administration Tools Reference for a complete description.

   The host on which the Vertica rpm package was manually installed. Always run the Administration Tools on this host if possible.

   rpm is a powerful package manager, which can be used to build, install, query, verify, update, and erase individual software packages. A package consists of an archive of files and meta-data used to install and erase the archive files. The meta-data includes helper scripts, file attributes, and descriptive information about the package. Packages come in two varieties: binary packages, used to encapsulate software to be installed, and source packages, containing the source code and recipe necessary to produce binary packages.

5. Run the rpm package installer.

   # rpm -Uvh pathname

   where pathname is the Vertica package file you downloaded.

   If the rpm installer reports multiple dependency problems, you are probably trying to install the wrong package. Make sure that the machine architecture (32-bit or 64-bit) of the package you downloaded matches the operating system.

   Preparing... ########################################### [100%]

   1:vertica ########################################### [100%]

   Vertica® Analytic Database 2.1.GA successfully installed.

    

   The documentation files (HTML and PDF) are installed in: /opt/vertica/doc/

    

   To read the documentation:

   file:///opt/vertica/doc/HTML/Master/index.htm

    

   To try the Quick Start tutorial:

   file:///opt/vertica/doc/HTML/QuickStart/index.htm

    

   To download the latest documentation in zip or tar format:

   http://www.vertica.com/v-zone/product_documentation

    

   To complete installation and configuration of the cluster,

   run /opt/vertica/sbin/install_vertica

6. Run the installation script as shown:

   # /opt/vertica/sbin/install_vertica -s host_list -r rpm_package -u dba_username

     

   -s host_list	a comma-separated list of hostnames or IP addresses to include in the cluster; do not include space characters in the list. Examples: -s host01,host02,host03 -s 192.168.233.101,192.168.233.102,192.168.233.103 This parameter is required and has no default value.
   -r rpm_package	the pathname of the rpm package that you installed in the previous step. Example: -r vertica_2.1.GA.x86_64.RHEL5.rpm This parameter is required and has no default value.
   -u dba_username	the name of the Database Administrator Linux account to create. Only this account can run the Administration Tools. If you omit the -u parameter, the default database administrator account name is dbadmin. The database administrator (DBA) is the Linux user account that owns the database catalog and data storage on disk. The DBA can bypass all database authorization rules. However, the DBA must supply a password to connect to a running database and to use Administration Tools commands that affect a running database. The DBA can drop a stopped database without supplying a password. This parameter is optional for new installations only. If upgrading, use the -u parameter to specify the same DBA account name that you used previously. Otherwise you may encounter problems later.

   The complete set of installation parameters including optional parameters and example output are described in the next section.

   The install_vertica script creates a cluster of nodes on which you can create a database.

   A database is a cluster of nodes that, when active, can perform distributed data storage and SQL statement execution through administrative, interactive, and programmatic user interfaces.

   A cluster generally refers a collection of hosts or a collection of nodes bound to a database. A cluster is not part of a database definition and thus does not have a name.

   A node is a host configured to run an instance of Vertica. It is a member of a database cluster (see Node Definition). For a database to have the ability to recover from the failure of a node requires at least three nodes. Vertica Systems, Inc. recommends that you use a minimum of four nodes.

   A cluster generally refers a collection of hosts or a collection of nodes bound to a database. A cluster is not part of a database definition and thus does not have a name.

   An instance of Vertica consists of the running Vertica process and disk storage (catalog and data) on a host. There can be only one instance of Vertica running on a host at any time.

   A cluster generally refers a collection of hosts or a collection of nodes bound to a database. A cluster is not part of a database definition and thus does not have a name.

   Syntax

   /opt/vertica/sbin/install_vertica

   -s host_list

   -r rpm_package

   [ -u dba_username ]

   [ -p dba_password ]

   [ -l dba_home_directory ]

   [ -d data_directory ]

   [ -P root_password ]

   Semantics

    

   host_list	a comma-separated list of hostnames or IP addresses to include in the cluster; do not include space characters in the list. Example: -s host01,host02,host03 -s 192.168.233.101,192.168.233.102,192.168.233.103 This parameter is required and has no default value.
   rpm_package	the name of the rpm package that contained this script .Example: -r vertica_2.1.GA.x86_64.RHEL5.rpm This parameter is required and has no default value.
   dba_username	the name of the Database Administrator Linux account to create. Only this account can run the Administration Tools. If you omit the -u parameter, the default database administrator account name is dbadmin. The database administrator (DBA) is the Linux user account that owns the database catalog and data storage on disk. The DBA can bypass all database authorization rules. However, the DBA must supply a password to connect to a running database and to use Administration Tools commands that affect a running database. The DBA can drop a stopped database without supplying a password. This parameter is optional for new installations only. If upgrading, use the -u parameter to specify the same DBA account name that you used previously. Otherwise you may encounter problems later.
   dba_password	the password for the Database Administrator account; if not supplied, the script prompts for the password and does not echo the input
   dba_home_directory	the home directory for the Database Administrator; default is /home/dba_username
   data_directory	the default directory for database data and catalog files; default is /home/dba_home_directory
   root_password	the root password to use by default for each cluster host; if not supplied, the script prompts for the password if and when necessary and does not echo the input

   Notes

   • Do not be concerned by the message -- Checking ...Failed. It indicates that install_vertica found and is correcting an incorrect configuration parameter.

   Example

   # /opt/vertica/sbin/install_vertica -s host01,host02,host03 -r vertica_1.3.15-7.i386.RHEL4.rpm

   Vertica Database 1.3.15-7 Installation Tool

   Please enter password for root@host01:

   root@host01: Installation not performed on host01, same version already installed

   root@host01: -- Checking status of ntpd service -- ...Done

   root@host01: -- Checking vm.min_free_kbytes parameter in /sbin/sysctl -- ...Failed

   root@host01: Info! Parameter vm.min_free_kbytes is less than 4096

   root@host01: Setting vm.min_free_kbytes to 4096 ...

   root@host01: -- Checking maximum number of open file descriptors in /etc/security/limits.conf -- ...Failed

   root@host01: Info! The maximum number of open file descriptors is less than 65536

   root@host01: Setting open filehandle limit to 65536 ...

   root@host02: -- Checking status of ntpd service -- ...Done

   root@host02: -- Checking vm.min_free_kbytes parameter in /sbin/sysctl -- ...Failed

   root@host02: Info! Parameter vm.min_free_kbytes is less than 4096

   root@host02: Setting vm.min_free_kbytes to 4096 ...

   root@host02: -- Checking maximum number of open file descriptors in /etc/security/limits.conf -- ...Failed

   root@host02: Info! The maximum number of open file descriptors is less than 65536

   root@host02: Setting open filehandle limit to 65536 ...

   root@host03: -- Checking status of ntpd service -- ...Done

   root@host03: -- Checking vm.min_free_kbytes parameter in /sbin/sysctl -- ...Failed

   root@host03: Info! Parameter vm.min_free_kbytes is less than 4096

   root@host03: Setting vm.min_free_kbytes to 4096 ...

   root@host03: -- Checking maximum number of open file descriptors in /etc/security/limits.conf -- ...Failed

   root@host03: Info! The maximum number of open file descriptors is less than 65536

   root@host03: Setting open filehandle limit to 65536 ...

   root@host01: -- Checking dbadmin_ssh directory -- ...Done

   root@host01: -- Generating SSH keys for user dbadmin -- ...Done

   root@host01: -- Copying root@host01:dbadmin_ssh_keys.tgz file to /tmp/dbadmin_ssh_keys.tgz -- ...Done

   Enter password for new UNIX user dbadmin:

   Retype new UNIX password for user dbadmin:

   root@host01: -- Creating user dbadmin -- ...Done

   root@host01: -- Checking /home/dbadmin directory -- ...Done

   root@host01: -- Changing the owner of /home/dbadmin directory to dbadmin -- ...Done

   root@host01: -- Write check for /home/dbadmin directory -- ...Done

   root@host01: -- Copying /tmp/dbadmin_ssh_keys.tgz file to root@host01:dbadmin_ssh_keys.tgz -- ...Done

   root@host01: -- Installing ssh keys -- ...Done

   root@host02: -- Creating user dbadmin -- ...Done

   root@host02: -- Checking /home/dbadmin directory -- ...Done

   root@host02: -- Changing the owner of /home/dbadmin directory to dbadmin -- ...Done

   root@host02: -- Write check for /home/dbadmin directory -- ...Done

   root@host02: -- Copying /tmp/dbadmin_ssh_keys.tgz file to root@host02:dbadmin_ssh_keys.tgz -- ...Done

   root@host02: -- Installing ssh keys -- ...Done

   root@host03: -- Creating user dbadmin -- ...Done

   root@host03: -- Checking /home/dbadmin directory -- ...Done

   root@host03: -- Changing the owner of /home/dbadmin directory to dbadmin -- ...Done

   root@host03: -- Write check for /home/dbadmin directory -- ...Done

   root@host03: -- Copying /tmp/dbadmin_ssh_keys.tgz file to root@host03:dbadmin_ssh_keys.tgz -- ...Done

   root@host03: -- Installing ssh keys -- ...Done

   ===== Site Availability Test ====================================

   All sites are available ... ok

   ===== Testing host01 ============================================

   Site availability ... ok

   Passwordless SSH access ... ok

   Passwordless SSH access to other sites ... ok

   Getting various information about the site ... ok

   Python is installed ... ok

   Enough RAM per CPUs ... ok

   Getting information about the ports ... ok

   Port availability for Spread ... ok

   Port availability for Vertica ... ok

   Gathering information about the network ... ok

   Sanity of /etc/hosts ... ok

   Hostname resolution ... ok

   IP configuration ... ok

   ===== Testing host02 ============================================

   Site availability ... ok

   Passwordless SSH access ... ok

   Passwordless SSH access to other sites ... ok

   Getting various information about the site ... ok

   Python is installed ... ok

   Enough RAM per CPUs ... ok

   Getting information about the ports ... ok

   Port availability for Spread ... ok

   Port availability for Vertica ... ok

   Gathering information about the network ... ok

   Sanity of /etc/hosts ... ok

   Hostname resolution ... ok

   IP configuration ... ok

   ===== Testing host03 ============================================

   Site availability ... ok

   Passwordless SSH access ... ok

   Passwordless SSH access to other sites ... ok

   Getting various information about the site ... ok

   Python is installed ... ok

   Enough RAM per CPUs ... ok

   Getting information about the ports ... ok

   Port availability for Spread ... ok

   Port availability for Vertica ... ok

   Gathering information about the network ... ok

   Sanity of /etc/hosts ... ok

   Hostname resolution ... ok

   IP configuration ... ok

   ===== Consistency Test ==========================================

   IP and Netmask consistency ... ok

   All sites are on the same subnet ... ok

   LANG and TZ environment variables ... ok

   ===== Network Test ==============================================

   Network communication ... ok

   root@host03: Test of site host01 (ok)

   root@host03: ============================

   root@host03:

   root@host03: Test of site host02 (ok)

   root@host03: ============================

   root@host03:

   root@host03: Test of site host03 (ok)

   root@host03: ============================

   root@host03:

   root@host03: Consistency Test (ok)

   root@host03: =========================

   root@host03:

   root@host03: Info: The $TZ environment variable is not set on host01

   root@host03: Info: The $TZ environment variable is not set on host02

   root@host03: Info: The $TZ environment variable is not set on host03

   root@host03:

   root@host03: Network Test (ok)

   root@host03: =====================

   root@host03:

   root@host03: Network communication (ok)

   root@host03: ------------------------------

   root@host03:

   root@host01: -- Setting up spread daemon -- ...Done

   root@host01: -- Copying /opt/vertica/config/vspread.conf file to root@host01:/opt/vertica/config/vspread.conf -- ...Done

   root@host01: -- Checking /opt/vertica/config/clusters directory -- ...Done

   root@host01: -- Checking /opt/vertica/config directory -- ...Done

   root@host01: -- Checking /opt/vertica/config/configInfo directory -- ...Done

   root@host01: -- Checking /opt/vertica/config/share directory -- ...Done

   root@host01: -- Checking /opt/vertica/config/users directory -- ...Done

   root@host01: -- Checking /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host01: -- Changing the owner of /opt/vertica/config/users/dbadmin directory to dbadmin -- ...Done

   root@host01: -- Write check for /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host01: -- Starting spread daemon -- ...Done

   root@host01: Creating node node1_host01 definition for host host01 ...Done

   root@host02: -- Setting up spread daemon -- ...Done

   root@host02: -- Copying /opt/vertica/config/vspread.conf file to root@host02:/opt/vertica/config/vspread.conf -- ...Done

   root@host02: -- Checking /opt/vertica/config/clusters directory -- ...Done

   root@host02: -- Checking /opt/vertica/config directory -- ...Done

   root@host02: -- Checking /opt/vertica/config/configInfo directory -- ...Done

   root@host02: -- Checking /opt/vertica/config/share directory -- ...Done

   root@host02: -- Checking /opt/vertica/config/users directory -- ...Done

   root@host02: -- Checking /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host02: -- Changing the owner of /opt/vertica/config/users/dbadmin directory to dbadmin -- ...Done

   root@host02: -- Write check for /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host02: -- Starting spread daemon -- ...Done

   root@host02: Creating node node2_host02 definition for host host02 ...Done

   root@host03: -- Setting up spread daemon -- ...Done

   root@host03: -- Copying /opt/vertica/config/vspread.conf file to root@host03:/opt/vertica/config/vspread.conf -- ...Done

   root@host03: -- Checking /opt/vertica/config/clusters directory -- ...Done

   root@host03: -- Checking /opt/vertica/config directory -- ...Done

   root@host03: -- Checking /opt/vertica/config/configInfo directory -- ...Done

   root@host03: -- Checking /opt/vertica/config/share directory -- ...Done

   root@host03: -- Checking /opt/vertica/config/users directory -- ...Done

   root@host03: -- Checking /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host03: -- Changing the owner of /opt/vertica/config/users/dbadmin directory to dbadmin -- ...Done

   root@host03: -- Write check for /opt/vertica/config/users/dbadmin directory -- ...Done

   root@host03: -- Starting spread daemon -- ...Done

   root@host03: Creating node node3_host03 definition for host host03 ...Done

   root@host03: Verifying spread configuration

   Installation complete.

   To create a database:

   1. run /opt/vertica/bin/adminTools as dbadmin

   2. select Create Database from the Configuration menu

   #

7. Provide the root password when prompted. The password does not echo on the command line.

   Vertica Database 2.1.GA Installation Tool

   Please enter password for root@host01:password

8. Provide the database administrator account password when prompted:

   Enter password for new UNIX user dbadmin:password

   Retype new UNIX password for user dbadmin:password

   The installation script creates a new Linux user account (dbadmin by default) with the password that you provide.

9. Carefully examine any warnings produced by install_vertica and correct the problems if possible. For example, insufficient RAM, insufficient Network throughput and too high readahead settings on filesystem may cause performance problems later on.

   Ignore insufficient RAM warnings when installing on VMware.

10. Optionally perform the steps in the following sections:
    • Installing the JDBC Driver (Optional)
    • Installing the ODBC Driver (Optional)
    • Install vsql Client Application on Non-Cluster Hosts (Optional)
11. Disconnect from the Administration Host as instructed by the script. This is required in order to:
    • set certain system parameters correctly
    • function as the Vertica database administrator

    At this point, Linux root privileges are no longer needed. The remaining steps can be performed by the database administrator.

    Exception: when creating a new database, the database administrator may wish to use different data and/or catalog locations than those created by the installation script. In that case, a Linux administrator may need to create those directories and change their ownership to the database administrator.

12. Log in to the Database Administrator account on the administration host.

    The database administrator (DBA) is the Linux user account that owns the database catalog and data storage on disk. The DBA can bypass all database authorization rules. However, the DBA must supply a password to connect to a running database and to use Administration Tools commands that affect a running database. The DBA can drop a stopped database without supplying a password.

13. Install the license key you downloaded previously as described in Installing Your License Key.
14. If you have not already done so, proceed to the Tutorial Procedure in the Quick Start. Otherwise, proceed to Configuring the Database in the Database Administrator's Guide.