Vertica Upgrade from version 8.0.x to 9.0.x on CentOS 6.5 – 3N Cluster

With release of version 9.0.x release in October 2017, Vertica is dropping support of 7.x and 8.x. Upgrading to 9.0 is highly recommended and very useful, as many great features have been added in version 9.x.

HPE recommended path is as follows, as upgrades are increments:

  • Vertica 7.0 to 7.1
  • Vertica 7.1 to 7.2
  • Vertica 7.2 to 8.0
  • Vertica 8.0 to 8.1
  • Vertica 8.1 to 9.0

Steps for Upgrade are highlighted below:

  1. Download the proper rpm or packages from Vertica site.
  2. Upload the same to one of the node in the cluster.
  3. MAke the RPM readable by root.

Download the proper rpm or packages from Vertica site

 sbalas002c@PAWAYL-31V7HC2 MINGW64 ~
$ ll Documents/Comcast/Vertica/
total 1874052
-rw-r--r-- 1 sbalas002c 1049089 111308961 Jul  3 14:26 vertica-7.1.2-21.x86_64.RHEL5.rpm
-rw-r--r-- 1 sbalas002c 1049089 127762372 Jul  3 14:34 vertica-7.2.3-18.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 182716988 Jul  3 14:44 vertica-8.0.1-6.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 190290480 Jul  3 09:25 vertica-8.1.0-1.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 216379376 Jul 20 14:23 vertica-8.1.1-0.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 216444664 Nov  3 09:53 vertica-8.1.1-8.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 222390092 Oct 23 18:41 vertica-9.0.0-0.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 222353492 Nov  3 10:03 vertica-9.0.0-1.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 129505950 Jul  3 14:18 vertica-console-7.1.2-0.x86_64.RHEL5.rpm
-rw-r--r-- 1 sbalas002c 1049089 118424276 Jul  3 14:39 vertica-console-7.2.3-0.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c 1049089 181432556 Jul 18 11:18 vertica-console-8.1.1-0.x86_64.RHEL6.rpm
sbalas002c@PAWAYL-31V7HC2 MINGW64 ~

Upload the same to the node in cluster

 sbalas002c@PAWAYL-31V7HC2 MINGW64 ~
$ sftp sbalas002c@COENGS-VRTS01
sbalas002c@coengs-vrts01's password:
Connected to COENGS-VRTS01.
sftp> put Documents/Comcast/Vertica/vertica-8.1.1-8.x86_64.RHEL6.rpm /tmp/.
Uploading Documents/Comcast/Vertica/vertica-8.1.1-8.x86_64.RHEL6.rpm to /tmp/./vertica-8.1.1-8.x86_64.RHEL6.rpm
Documents/Comcast/Vertica/vertica-8.1.1-8.x86_64.RHEL6.rpm                                                                            100%  206MB 590.8KB/s   05:57
sftp> put Documents/Comcast/Vertica/vertica-9.0.0-1.x86_64.RHEL6.rpm /tmp/.
Uploading Documents/Comcast/Vertica/vertica-9.0.0-1.x86_64.RHEL6.rpm to /tmp/./vertica-9.0.0-1.x86_64.RHEL6.rpm
Documents/Comcast/Vertica/vertica-9.0.0-1.x86_64.RHEL6.rpm                                                                            100%  212MB 889.3KB/s   04:04
sftp> quit
sbalas002c@PAWAYL-31V7HC2 MINGW64 ~

Save the rpm files into proper directory, as root.

[root@COENGS-VRTS01 ~]# ll vertica
total 840424
-rw-r--r-- 1 sbalas002c linux-users 111308961 Jul  3 14:36 vertica-7.1.2-21.x86_64.RHEL5.rpm
-rw-r--r-- 1 sbalas002c linux-users 127762372 Jul  3 14:41 vertica-7.2.3-18.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c linux-users 182716988 Jul  3 14:47 vertica-8.0.1-6.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        216444664 Nov  4 09:50 vertica-8.1.1-8.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        222353492 Nov  4 09:50 vertica-9.0.0-1.x86_64.RHEL6.rpm
[root@COENGS-VRTS01 ~]#

Check the Catalog storage

[dbadmin@COENGS-VRTS01 ~]$ ll /catalog/comcast/v_comcast_node0001_catalog/Catalog/
total 1696
drwxrwx--- 4 dbadmin verticadba    4096 Nov  4 15:38 Checkpoints
-rw-rw-rw- 1 dbadmin verticadba 1717135 Nov  4 11:48 config.cat
-rw-rw-rw- 1 dbadmin verticadba     152 Nov  4 16:55 globalsequence.cat
-rw-rw-rw- 1 dbadmin verticadba     151 Nov  4 16:56 sequencegenerator.cat
-rw-rw---- 1 dbadmin verticadba       0 Sep 12  2014 tiered_catalog.cat
drwxrwx--- 2 dbadmin verticadba    4096 Nov  4 16:48 Txnlogs
[dbadmin@COENGS-VRTS01 ~]$ du -s -BG /catalog/comcast/v_comcast_node0001_catalog/Catalog/
1G      /catalog/comcast/v_comcast_node0001_catalog/Catalog/
[dbadmin@COENGS-VRTS01 ~]$ df -BG /catalog/comcast/v_comcast_node0001_catalog/Catalog/
Filesystem     1G-blocks  Used Available Use% Mounted on
/dev/sda3           271G  113G      145G  44% /
[dbadmin@COENGS-VRTS01 ~]$

Create a FULL Hard Link backup of the Database

On node one as dbadmin run the vbr script from a terminal using the database administrator account from a node in your database cluster. You cannot run the utility as root.

[dbadmin@COENGS-VRTS01 ~]$ cd VerticaBR/
[dbadmin@COENGS-VRTS01 VerticaBR]$ /opt/vertica/bin/vbr --task backup --config HLfullackup01_8016.ini
Starting backup of database comcast.
Participating nodes: v_comcast_node0001, v_comcast_node0002, v_comcast_node0003.
Snapshotting database.
Snapshot complete.
Approximate bytes to copy: 96313419886 of 2063717381751 total.
[==================================================] 100%
Copying backup metadata.
Finalizing backup.
Backup complete!
[dbadmin@COENGS-VRTS01 VerticaBR]$

As dbadmin STOP the database using admintools

[dbadmin@COENGS-VRTS01 VerticaBR]$ admintools -t stop_db -d comcast
Info: no password specified, using none
        Connecting to database
        Issuing shutdown command to database
Database comcast not stopped successfully for the following reason:
Error: NOTICE 2519:  Cannot shut down while users are connected
[dbadmin@COENGS-VRTS01 VerticaBR]$ admintools -t stop_db -d comcast -F
Info: no password specified, using none
        Connecting to database
        Issuing shutdown command to database
Database comcast stopped successfully
[dbadmin@COENGS-VRTS01 VerticaBR]$
[dbadmin@COENGS-VRTS01 VerticaBR]$ vsql
vsql: could not connect to server: Connection refused
        Is the server running on host "???" and accepting
        TCP/IP connections on port 5433?
[dbadmin@COENGS-VRTS01 VerticaBR]$

As root install the rpm in the cluster.

[root@COENGS-VRTS01 ~]# cd vertica
[root@COENGS-VRTS01 vertica]# ll
total 840424
-rw-r--r-- 1 sbalas002c linux-users 111308961 Jul  3 14:36 vertica-7.1.2-21.x86_64.RHEL5.rpm
-rw-r--r-- 1 sbalas002c linux-users 127762372 Jul  3 14:41 vertica-7.2.3-18.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c linux-users 182716988 Jul  3 14:47 vertica-8.0.1-6.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        216444664 Nov  4 09:50 vertica-8.1.1-8.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        222353492 Nov  4 09:50 vertica-9.0.0-1.x86_64.RHEL6.rpm
[root@COENGS-VRTS01 vertica]# rpm -Uvh vertica-8.1.1-8.x86_64.RHEL6.rpm
Preparing...                ########################################### [100%]
   1:vertica                ########################################### [100%]
Shutting down vertica services for upgrade
Stopping vertica
Shutting down vertica agent daemon
Stopping vertica agent:
Vertica Analytic Database V8.1.1-8 successfully installed on host COENGS-VRTS01
To complete your NEW installation and configure the cluster, run:
 /opt/vertica/sbin/install_vertica
To complete your Vertica UPGRADE, run:
 /opt/vertica/sbin/update_vertica
----------------------------------------------------------------------------------
Important
----------------------------------------------------------------------------------
Before upgrading Vertica, you must backup your database.  After you restart your
database after upgrading, you cannot revert to a previous Vertica software version.
----------------------------------------------------------------------------------
View the latest Vertica documentation at http://my.vertica.com/docs/
[root@COENGS-VRTS01 vertica]#

On the same node on which you just installed the RPM, run update_vertica as root or sudo. This installs the RPM on all the hosts in the cluster.

[root@COENGS-VRTS01 vertica]#  /opt/vertica/sbin/update_vertica --rpm  vertica-8.1.1-8.x86_64.RHEL6.rpm  --dba-user dbadmin
Vertica Analytic Database 8.1.1-8 Installation Tool
>> Validating options...
>> Starting installation tasks.
>> Getting system information for cluster (this may take a while)...
Default shell on nodes:
192.168.10.1 /bin/bash
192.168.10.2 /bin/bash
192.168.10.3 /bin/bash
>> Validating software versions (rpm or deb)...
>> Beginning new cluster creation...
successfully backed up admintools.conf on 192.168.10.1
successfully backed up admintools.conf on 192.168.10.2
successfully backed up admintools.conf on 192.168.10.3
>> Installing software (rpm or deb)...
Installing rpm on 2 hosts....
installing node....  192.168.10.2
        installing node....  192.168.10.3
>> Creating or validating DB Admin user/group...
Successful on hosts (3): 192.168.10.1 192.168.10.2 192.168.10.3
    Provided DB Admin account details: user = dbadmin, group = verticadba, home = /home/dbadmin
    Creating group... Group already exists
    Validating group... Okay
    Creating user... User already exists
    Validating user... Okay
>> Validating node and cluster prerequisites...
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.1.xml:
    HINT (S0305): https://my.vertica.com/docs/8.1.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.3.xml:
    HINT (S0305): https://my.vertica.com/docs/8.1.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.2.xml:
    HINT (S0305): https://my.vertica.com/docs/8.1.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
System prerequisites passed.  Threshold = WARN
>> Establishing DB Admin SSH connectivity...
Installing/Repairing SSH keys for dbadmin
>> Setting up each node and modifying cluster...
Creating Vertica Data Directory...
Updating agent...
>> Sending new cluster configuration to all nodes...
Starting agent...
>> Completing installation...
Running upgrade logic
No spread upgrade required: /opt/vertica/config/vspread.conf not found on any node
Installation complete.
Please evaluate your hardware using Vertica's validation tools:
    https://my.vertica.com/docs/8.1.x/HTML/index.htm#cshid=VALSCRIPT
To create a database:
  1. Logout and login as dbadmin. (see note below)
  2. Run /opt/vertica/bin/adminTools as dbadmin
  3. Select Create Database from the Configuration Menu
  Note: Installation may have made configuration changes to dbadmin
  that do not take effect until the next session (logout and login).
To add or remove hosts, select Cluster Management from the Advanced Menu.
[root@COENGS-VRTS01 vertica]#

As dbadmin re-login and start the database

[sbalas002c@COENGS-VRTS01 ~]$ su – dbadmin
Password:
[dbadmin@COENGS-VRTS01 ~]$

Using admintools start the DB. Depending on catalog size this step may long time. This step will re-install all the required packages.

*** Starting database: comcast ***
        Starting nodes:
                v_comcast_node0002 (192.168.10.2)
                v_comcast_node0001 (192.168.10.1)
                v_comcast_node0003 (192.168.10.3)
        Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize.
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (DOWN) v_comcast_node0002: (DOWN) v_comcast_node0003: (DOWN)
        Node Status: v_comcast_node0001: (UP) v_comcast_node0002: (UP) v_comcast_node0003: (UP)
        Vertica version upgrade detected. Running package upgrade tasks.
        Running upgrade hooks
Upgrading (re-installing) extension packages:
Package: approximate
        Installing approximate
        Success: package approximate installed
Package: idol
        Installing idol
        Success: package idol installed
Package: place
        Installing place
        Success: package place installed
Package: ParquetExport
        Installing ParquetExport
        Success: package ParquetExport installed
Package: txtindex
        Installing txtindex
        Success: package txtindex installed
Package: hdfsconnector
        Installing hdfsconnector
        Success: package hdfsconnector installed
Package: kafka
        Installing kafka
        Success: package kafka installed
Package: flextable
        Installing flextable
        Success: package flextable installed
Package: AWS
        Installing AWS
        Success: package AWS installed
Package: MachineLearning
        Installing MachineLearning
        Success: package MachineLearning installed
Package: logsearch
        Installing logsearch
        Success: package logsearch installed

DB upgrade completed. Re-install the optional packages if required.

Check the DB Version.

[dbadmin@COENGS-VRTS01 ~]$ vsql
Welcome to vsql, the Vertica Analytic Database interactive terminal.
Type:  \h or \? for help with vsql commands
       \g or terminate with semicolon to execute query
       \q to quit
dbadmin=> select version();
              version
------------------------------------
 Vertica Analytic Database v8.1.1-8
(1 row)
dbadmin=> \q
[dbadmin@COENGS-VRTS01 ~]$

Continue UPGRADE to 9.0.x

Stop the database

[dbadmin@COENGS-VRTS01 ~]$ admintools -t stop_db -d comcast -F
Info: no password specified, using none
        Connecting to database
        Issuing shutdown command to database
Database comcast stopped successfully
[dbadmin@COENGS-VRTS01 ~]$

As root install the rpm

 

[root@COENGS-VRTS01 vertica]# ll
total 840424
-rw-r--r-- 1 sbalas002c linux-users 111308961 Jul  3 14:36 vertica-7.1.2-21.x86_64.RHEL5.rpm
-rw-r--r-- 1 sbalas002c linux-users 127762372 Jul  3 14:41 vertica-7.2.3-18.x86_64.RHEL6.rpm
-rw-r--r-- 1 sbalas002c linux-users 182716988 Jul  3 14:47 vertica-8.0.1-6.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        216444664 Nov  4 09:50 vertica-8.1.1-8.x86_64.RHEL6.rpm
-rw-r--r-- 1 root       root        222353492 Nov  4 09:50 vertica-9.0.0-1.x86_64.RHEL6.rpm
[root@COENGS-VRTS01 vertica]# rpm -Uvh vertica-9.0.0-1.x86_64.RHEL6.rpm
Preparing...                ########################################### [100%]
   1:vertica                ########################################### [100%]
Shutting down vertica services for upgrade
Stopping vertica
Shutting down vertica agent daemon
Stopping vertica agent:
Vertica Analytic Database V9.0.0-1 successfully installed on host COENGS-VRTS01
To complete your NEW installation and configure the cluster, run:
 /opt/vertica/sbin/install_vertica
To complete your Vertica UPGRADE, run:
 /opt/vertica/sbin/update_vertica
----------------------------------------------------------------------------------
Important
----------------------------------------------------------------------------------
Before upgrading Vertica, you must backup your database.  After you restart your
database after upgrading, you cannot revert to a previous Vertica software version.
----------------------------------------------------------------------------------
View the latest Vertica documentation at http://my.vertica.com/docs/
[root@COENGS-VRTS01 vertica]#

On the same node on which you just installed the RPM, run update_vertica as root or sudo. This installs the RPM on all the hosts in the cluster.

 [root@COENGS-VRTS01 vertica]#  /opt/vertica/sbin/update_vertica --rpm vertica-9.0.0-1.x86_64.RHEL6.rpm  --dba-user dbadmin
Vertica Analytic Database 9.0.0-1 Installation Tool
>> Validating options...
>> Starting installation tasks.
>> Getting system information for cluster (this may take a while)...
Default shell on nodes:
192.168.10.1 /bin/bash
192.168.10.2 /bin/bash
192.168.10.3 /bin/bash
>> Validating software versions (rpm or deb)...
>> Beginning new cluster creation...
successfully backed up admintools.conf on 192.168.10.1
successfully backed up admintools.conf on 192.168.10.2
successfully backed up admintools.conf on 192.168.10.3
>> Installing software (rpm or deb)...
Installing rpm on 2 hosts....
installing node....  192.168.10.2
installing node....  192.168.10.3
>> Creating or validating DB Admin user/group...
Successful on hosts (3): 192.168.10.1 192.168.10.2 192.168.10.3
    Provided DB Admin account details: user = dbadmin, group = verticadba, home = /home/dbadmin
    Creating group... Group already exists
    Validating group... Okay
    Creating user... User already exists
    Validating user... Okay
>> Validating node and cluster prerequisites...
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.2.xml:
    HINT (S0305): https://my.vertica.com/docs/9.0.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.3.xml:
    HINT (S0305): https://my.vertica.com/docs/9.0.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
Prerequisites not fully met during local (OS) configuration for
verify-192.168.10.1.xml:
    HINT (S0305): https://my.vertica.com/docs/9.0.x/HTML/index.htm#cshid=S0305
        TZ is unset for dbadmin. Consider updating .profile or .bashrc
System prerequisites passed.  Threshold = WARN
>> Establishing DB Admin SSH connectivity...
Installing/Repairing SSH keys for dbadmin
>> Setting up each node and modifying cluster...
Creating Vertica Data Directory...
Updating agent...
>> Sending new cluster configuration to all nodes...
Starting agent...
>> Completing installation...
Running upgrade logic
No spread upgrade required: /opt/vertica/config/vspread.conf not found on any node
Installation complete.
Please evaluate your hardware using Vertica's validation tools:
    https://my.vertica.com/docs/9.0.x/HTML/index.htm#cshid=VALSCRIPT
To create a database:
  1. Logout and login as dbadmin. (see note below)
  2. Run /opt/vertica/bin/adminTools as dbadmin
  3. Select Create Database from the Configuration Menu
  Note: Installation may have made configuration changes to dbadmin
  that do not take effect until the next session (logout and login).
To add or remove hosts, select Cluster Management from the Advanced Menu.
[root@COENGS-VRTS01 vertica]#

As dbadmin accept EULA and start the database. and check the version.

 

[dbadmin@COENGS-VRTS01 ~]$ vsql
Welcome to vsql, the Vertica Analytic Database interactive terminal.
Type: \h or \? for help with vsql commands
 \g or terminate with semicolon to execute query
 \q to quit
dbadmin=> select version();
 version
------------------------------------
 Vertica Analytic Database v9.0.0-1
(1 row)
dbadmin=> \q
[dbadmin@COENGS-VRTS01 ~]$

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s