Skip to main content
Question

Upgrade path v6 to v9

  • August 22, 2019
  • 3 replies
  • 6 views

Bryan_H
Forum|alt.badge.img+2

Hello all, we had a customer normalize support and report that they have a v6 cluster that needs to be upgraded. What's the safest way to do this? Upgrading incrementally will likely be time-consuming and risky. Could we mirror the v6 database with odb or connect to avoid having to step through three major versions of upgrade? What issues might we have either way?

3 replies

Bryan_H
Forum|alt.badge.img+2
  • Author
  • Participating Frequently
  • August 22, 2019

I searched Confluence for "planning objects" and got a lot of hits for "plan" and "objects" but probably not what I need. Could you link to a specific Confluence page? I also asked if it is a small DB so it might be possible to copy to a test environment in their infrastructure or on the cloud.


marcothesane
Forum|alt.badge.img+1
  • Participating Frequently
  • August 22, 2019

Could be a candidate / guinea pig for Vertica-to-Vertica using odb .... thoughts?


mosheg
Forum|alt.badge.img+2
  • Participating Frequently
  • August 23, 2019

To collect planning objects in 7 and above use: /opt/vertica/bin/scrutinize -t profiling
Planning Objects Eugenia mentioned is explained here:
http://confluence.verticacorp.com:8080/display/TechSupport/Planning_Objects
Here is a brief
1) /opt/vertica/scripts/collect_diag_dump.sh
This will run the export_planning_objects function and will create a file diag_dump_running_time.tar.gz
Note also that it produce a warning: DB branching has been deprecated and will be removed in a later version
2) To import the planning_objects, you need to have a target with the same size.
To find out the number of nodes in source cluster do: grep siteUniqueID planning_objects | wc -l
3) To avoid statistics import, disable automatic row counts: select disable_service('TM','AnalyzeRowCount');
To check status do: select list_services('TM');
4) Import all objects stored in the file in phase (1) that are used for query planning:
select import_planning_objects ('filename', 'password');
filename is the name of the file to read objects from, and was created by the collect_diag_dump.sh script.
password is OptimizerPeeps - Please do NOT give this out to customers.
For example: select import_planning_objects ('./tmp/Out_20190823073444/planning_objects','OptimizerPeeps');
5) To see which objects were imported: select set_debug_log('Catalog','BASIC'); and check vertica.log
6) Re-enable the AnalyzeRowCount: select enable_service('TM','AnalyzeRowCount');