After adding new data directory, how do I upgrade Vertica?
Article ID: 10330
Updated On:
Products
Issue/Introduction
Using the directions in:
we added a new data directory.
So we now have 2 data directories for each node, instead of just one:
Storage location list:
============================================================================
dradmin=> select node_name, location_path, location_usage ,location_label from storage_locations;
node_name | location_path | location_usage | location_label
-------------------+----------------------------------------------+----------------+----------------
v_drdata_node0001 | /opt/ca/data/drdata/v_drdata_node0001_data | DATA,TEMP |
v_drdata_node0001 | /opt/ca1/data1/drdata/v_drdata_node0001_data | DATA,TEMP |
v_drdata_node0002 | /opt/ca/data/drdata/v_drdata_node0002_data | DATA,TEMP |
v_drdata_node0002 | /opt/ca1/data1/drdata/v_drdata_node0002_data | DATA,TEMP |
v_drdata_node0003 | /opt/ca/data/drdata/v_drdata_node0003_data | DATA,TEMP |
v_drdata_node0003 | /opt/ca1/data1/drdata/v_drdata_node0003_data | DATA,TEMP |
what path should I put in the drinstall.properties before we do an upgrade?
Environment
Resolution
Use the original PATH.
# Location of Vertica's data directory
DbDataDir=/opt/ca/data
In an upgrade, it will upgrade vertica s/w on the current node. Then it will run install_vertica to upgrade rpm on each node. It will attempt to create the DB, but already see it exists.
So it should really just be upgrading the vertica tools and confirming all the config files are correct.
The extra locations are only stored in the DB, not in the config files.
Additional Information
How to add an additional data location to the Data Repository
Feedback
