GBase 8a V86 has been widely deployed for years. As of early 2024, a direct upgrade to the latest V953 is not yet supported; you must first transition through V952. This article documents the complete process of stopping a V86 cluster, upgrading to V952.43, and then moving to V953, using a single‑node cluster as an example.
Environment
A single‑node 862 Build43 cluster running on IP 10.0.2.181. All cluster components are in OPEN state.
Phase 1: Upgrade to V952.43
1. Stop the V86 Cluster
Gracefully shut down all services with the legacy stop command.
[root@anolios86-1 ~]# service gcware stop
Stopping GCMonit success!
...
Waiting for gcware services to unload:. [ OK ]
2. Prepare the V952 Upgrade Configuration
Create a demo.options file specifying the installation prefix, coordinator host, data host, and DBA credentials.
installPrefix= /opt
coordinateHost = 10.0.2.181
coordinateHostNodeID = 234,235,237
dataHost = 10.0.2.181
dbaUser = gbase
dbaGroup = gbase
dbaPwd = 'gbase1234'
rootPwd = '111111'
3. Run the Upgrade
Execute the silent upgrade script as the gbase user.
[gbase@anolios86-1 gcinstall_95243.5]$ ./gcinstall.py -U --silent=demo.options
After accepting the licence and confirming the target hosts, the installer completes the upgrade automatically. Once finished, source the environment profile and verify the cluster:
[gbase@anolios86-1 gcinstall_95243.5]$ source /home/gbase/.gbase_profile
[gbase@anolios86-1 gcinstall_95243.5]$ gcadmin
CLUSTER STATE: ACTIVE
...
[gbase@anolios86-1 gcinstall_95243.5]$ gccli
GBase client 9.5.2.43.5124aede18e. Copyright (c) 2004-2024, GBase. All Rights Reserved.
gbase> select version();
+----------------------+
| version() |
+----------------------+
| 9.5.2.43.5124aede18e |
+----------------------+
Data integrity is preserved: querying a sample table returns expected results.
Phase 2: Upgrade to V953
1. Stop the V952 Cluster
[gbase@anolios86-1 gcinstall_95243.5]$ gcluster_services all stop
Stopping GCMonit success!
...
2. Configure and Execute the V953 Upgrade
Create a new demo.options file that includes the V953‑required parameters (such as gcwareHost). Then run the silent upgrade.
[gbase@anolios86-1 gcinstall_95328.12]$ ./gcinstall.py --silent=demo.options -U --generalDBUser=root --generalDBPwd=''
The installer refreshes snapshots, checks the environment, and performs the upgrade. After it finishes, re‑source the profile and verify the cluster and version:
[gbase@anolios86-1 gcinstall_95328.12]$ source /home/gbase/.gbase_profile
[gbase@anolios86-1 gcinstall_95328.12]$ gcadmin
CLUSTER STATE: ACTIVE
...
[gbase@anolios86-1 gcinstall_95328.12]$ gccli
GBase client 9.5.3.28.12509af275af. Copyright (c) 2004-2024, GBase. All Rights Reserved.
gbase> select version();
+-----------------------+
| version() |
+-----------------------+
| 9.5.3.28.12509af275af |
+-----------------------+
A query on the test table confirms the business data remains intact.
Summary
The upgrade path from GBase 8a V86 to V953 is: V86 → V952 (version ≥ 9.5.2.41) → V953. With properly prepared configuration files and the silent installation scripts, the entire migration is smooth and preserves all existing data. Once a direct V86‑to‑V953 upgrade becomes available, this guide will be updated accordingly.
This hands‑on record demonstrates how to keep your gbase database cluster current, taking advantage of the performance and stability improvements in GBASE's latest MPP releases.
Top comments (0)