Upgrading the Database in AWS

The upgrade process is irreversible. Before beginning this procedure, ensure that you back up the database. Also, be patient as the Database upgrade might take time to complete. The Database might need time to create indexes and complete upgrade tasks. The Database upgrade might appear to be complete; however, if you start the product before the Database upgrade is complete, you might experience errors and performance issues.

Follow the Checklist: Upgrading Your On-premises Environment to ensure a successful upgrade.

If the installation is passwordless, you need to generate the ssh public key using the command- ssh-keygen.

Log in to the bastion where you downloaded the files.
Copy the db-installer_x.x.x-x.tar.gz file to the Database cluster node 1.
Log in to Database cluster node 1.
Create a directory to extract the db-installer_x.x.x-x.tar.gz file into. We will refer to this directory as {unzipped-db-installer-dir}.

Do not use the directories /root, /opt/vertica, or the existing database installer directory (default is /opt/arcsight-db-tools). The files in /opt/arcsight-db-tools will be upgraded by the database upgrade tool.

Change to the directory.
```
cd {unzipped-db-installer-dir}
```
Extract (untar) the db-installer_x.x.x-x.tar.gz file into the directory using the following command:
```
tar xvfz  db-installer_x.x.x-x.tar.gz
```

Execute the following command to start the upgrade of the schema and database tools.

./db_upgrade -c upgrade-utilities

The output of the command will look similar to the following:

Stopping cronjob. Please wait. 
All cronjobs are stopped.
Upgrade related changes cannot be rolled back, do you want to continue with the upgrade (Y/N): Y
Starting upgrade... *********************
Start of Database Upgrade ******************
Enter previous installed location (/opt/arcsight-db-tools):
Running Pre-Upgrade checks
Checking all database nodes are UPAll database nodes are UP
Replacing files in installed location
Upgrading script and config files.
Creating backup directory: /opt/arcsight-db-tools/oldVersion
Backing up: /opt/arcsight-db-tools/db_installer
Backing up: /opt/arcsight-db-tools/scriptsBacking up: /opt/arcsight-db-tools/data
Backing up: /opt/arcsight-db-tools/upgradeBacking up: /opt/arcsight-db-tools/lib
Backing up: /opt/arcsight-db-tools/udfs
Backing up: /opt/arcsight-db-tools/db.properties
Backing up: /opt/arcsight-db-tools/kafka_scheduler
Backing up: /opt/arcsight-db-tools/sched_ssl_setup
Backing up: /opt/arcsight-db-tools/schema_registry_setupBacking up: /opt/arcsight-db-tools/db_ssl_setup
Backing up: /opt/arcsight-db-tools/db_upgrade.py
Backing up: /opt/arcsight-db-tools/db_upgrade
Backing up: /opt/arcsight-db-tools/copyright.txt
Upgrading: /opt/arcsight-db-tools/db-installer_upgrade-12.0.2-1-6.tar.gz
Upgrading: /opt/arcsight-db-tools/db_installerUpgrading: /opt/arcsight-db-tools/scriptsUpgrading: /opt/arcsight-db-tools/data
Upgrading: /opt/arcsight-db-tools/upgrade
Upgrading: /opt/arcsight-db-tools/libUpgrading: /opt/arcsight-db-tools/udfs
Upgrading: /opt/arcsight-db-tools/db.properties
Upgrading: /opt/arcsight-db-tools/kafka_scheduler
Upgrading: /opt/arcsight-db-tools/sched_ssl_setup
Upgrading: /opt/arcsight-db-tools/schema_registry_setup
Upgrading: /opt/arcsight-db-tools/db_ssl_setup
Upgrading: /opt/arcsight-db-tools/db_upgrade.py
Upgrading: /opt/arcsight-db-tools/db_upgrade
Upgrading: /opt/arcsight-db-tools/copyright.txtUpgrading: /opt/arcsight-db-tools/db-upgrade.log
Add new fields for event integrity
Successfully added new fields for event integrity.
Checking if Logger Event Table exists
Successfully updated Logger Events Table.
Version specific upgrade methods
********************* Database Upgraded Complete. Version is 3.7.1 ******************

Execute the following command to start the database binaries upgrade:

[root@ip-10-0-1-142 db]# ./db_upgrade -c upgrade-db-rpm

Database server's root password may be asked during the process.

Stopping cronjob. Please wait.
All cronjobs are stopped.
Upgrade related changes cannot be rolled back, do you want to continue with the upgrade (Y/N): Y
Starting upgrade... *********************
Start of Database Upgrade ******************
Enter previous installed location (/opt/arcsight-db-tools):
Running Pre-Upgrade checks
Checking all database nodes are UP
All database nodes are UP
********************* Start of db rpm Upgrade ******************
Pre Upgrade check for 11.1.1-4
Current database rpm version is: 11.0.2-2
database can be upgraded to 11.1.1-4
Stopping firewall before db rpm upgrade.
Stopping scheduler before db rpm upgrade.
Stopping DB before db rpm upgrade.
Upgrading db RPM: vertica-11.1.1-4.x86_64.RHEL6.rpm
Starting DB after db rpm upgrade.
*********************Start of db rpm Upgrade
******************Pre Upgrade check for 12.0.2-1
Current database rpm version is: 11.1.1-4
database can be upgraded to 12.0.2-1
Stopping firewall before db rpm upgrade.
Stopping scheduler before db rpm upgrade.
Stopping DB before db rpm upgrade.
Upgrading db RPM: vertica-12.0.2-1.x86_64.RHEL6.rpm
Starting DB after db rpm upgrade.
Upgrading UDX function to 12.0.2-1
UDX function upgraded to 12.0.2-1
Refer to the documentation for post upgrade steps.

Change to the directory you provided when answering the prompt Enter previous installed location (/opt/arcsight-db-tools): in the previous step:

cd /opt/arcsight-db-tools

If OS has been upgraded, the file /etc/pki/tls/cert.pem will be reset during the upgrade, requiring the schema registry setup to be invalidated.

To correct this, run the following command:

If you need help locating the issue_ca.crt file for your database node, see Completing the Database and Kafka Scheduler Setups - AWS.

./schema_registry_setup <FQDN of ArcSight Platform Virtual IP for HA or single master node> issue_ca.crt

Database server's root password may be asked during the process.

Start the database event consumer:

/opt/arcsight-db-tools/kafka_scheduler start

Start watchdog:

/opt/arcsight-db-tools/scripts/watchdog.sh enable

(Optional) Start the firewall service.