Upgrading from an Earlier SynxDB 2 Release

The upgrade path supported for this release is SynxDB 2.x to a newer SynxDB 2.x release.

Important Set the SynxDB timezone to a value that is compatible with your host systems. Setting the SynxDB timezone prevents SynxDB from selecting a timezone each time the cluster is restarted and sets the timezone for the SynxDB master and segment instances. After you upgrade to this release and if you have not set a SynxDB timezone value, verify that the selected SynxDB timezone is acceptable for your deployment. See Configuring Timezone and Localization Settings for more information.

Prerequisites

Before starting the upgrade process, perform the following checks.

Verify the health of the SynxDB host hardware, and verify that the hosts meet the requirements for running SynxDB. The SynxDB gpcheckperf utility can assist you in confirming the host requirements.

Note If you need to run the gpcheckcat utility, run it a few weeks before the upgrade during a maintenance period. If necessary, you can resolve any issues found by the utility before the scheduled upgrade.

The utility is in $GPHOME/bin. Place SynxDB in restricted mode when you run the gpcheckcat utility. See the SynxDB Utility Guide for information about the gpcheckcat utility.

If gpcheckcat reports catalog inconsistencies, you can run gpcheckcat with the -g option to generate SQL scripts to fix the inconsistencies.

After you run the SQL scripts, run gpcheckcat again. You might need to repeat the process of running gpcheckcat and creating SQL scripts to ensure that there are no inconsistencies. Run the SQL scripts generated by gpcheckcat on a quiescent system. The utility might report false alerts if there is activity on the system.

Important Synx Data Labs customers should contact Synx Data Labs Support if the gpcheckcat utility reports errors but does not generate a SQL script to fix the errors. Information for contacting Synx Data Labs Support is at https://www.synxdata.com/.
If you have configured the SynxDB Platform Extension Framework (PXF) in your previous SynxDB installation, you must stop the PXF service and back up PXF configuration files before upgrading to a new version of SynxDB.

If you have not yet configured PXF, no action is necessary.

Upgrading from 6.x to a Newer 6.x Release

An upgrade from SynxDB 2.x to a newer 6.x release involves stopping SynxDB, updating the SynxDB software binaries, and restarting SynxDB. If you are using SynxDB extension packages there are additional requirements. See Prerequisites in the previous section.

Log in to your SynxDB master host as the SynxDB administrative user:
```
$ su - gpadmin
```
Perform a smart shutdown of your SynxDB 2.x system (there can be no active connections to the database). This example uses the -a option to deactivate confirmation prompts:
```
$ gpstop -a
```
Copy the new SynxDB software installation package to the gpadmin user’s home directory on each master, standby, and segment host.
If you used yum or apt to install SynxDB to the default location, run these commands on each host to upgrade to the new software release.

For RHEL/CentOS systems:
```
$ sudo yum upgrade ./greenplum-db-<version>-<platform>.rpm
```
For Ubuntu systems:
```
# apt install ./greenplum-db-<version>-<platform>.deb
```
The yum or apt command installs the new SynxDB software files into a version-specific directory under /usr/local and updates the symbolic link /usr/local/greenplum-db to point to the new installation directory.
If you used rpm to install SynxDB to a non-default location on RHEL/CentOS systems, run rpm on each host to upgrade to the new software release and specify the same custom installation directory with the --prefix option. For example:
```
$ sudo rpm -U ./greenplum-db-<version>-<platform>.rpm --prefix=<directory>
```
The rpm command installs the new SynxDB software files into a version-specific directory under the <directory> you specify, and updates the symbolic link <directory>/greenplum-db to point to the new installation directory.
Update the permissions for the new installation. For example, run this command as root to change the user and group of the installed files to gpadmin.
```
$ sudo chown -R gpadmin:gpadmin /usr/local/greenplum*
```
If needed, update the synxdb_path.sh file on the master and standby master hosts for use with your specific installation. These are some examples.
- If SynxDB uses LDAP authentication, edit the synxdb_path.sh file to add the line:
```
export LDAPCONF=/etc/openldap/ldap.conf
```
- If SynxDB uses PL/Java, you might need to set or update the environment variables JAVA_HOME and LD_LIBRARY_PATH in synxdb_path.sh.
Note When comparing the previous and new synxdb_path.sh files, be aware that installing some SynxDB extensions also updates the synxdb_path.sh file. The synxdb_path.sh from the previous release might contain updates that were the result of installing those extensions.
Edit the environment of the SynxDB superuser (gpadmin) and make sure you are sourcing the synxdb_path.sh file for the new installation. For example change the following line in the .bashrc or your chosen profile file:
```
source /usr/local/greenplum-db-<current_version>/synxdb_path.sh
```
to:
```
source /usr/local/greenplum-db-<new_version>/synxdb_path.sh
```
Or if you are sourcing a symbolic link (/usr/local/greenplum-db) in your profile files, update the link to point to the newly installed version. For example:
```
$ sudo rm /usr/local/greenplum-db
$ sudo ln -s /usr/local/greenplum-db-<new_version> /usr/local/greenplum-db
```
Source the environment file you just edited. For example:
```
$ source ~/.bashrc
```
After all segment hosts have been upgraded, log in as the gpadmin user and restart your SynxDB system:
```
# su - gpadmin
$ gpstart
```
For SynxDB, use the gppkg utility to re-install SynxDB extensions. If you were previously using any SynxDB extensions such as pgcrypto, PL/R, PL/Java, or PostGIS, download the corresponding packages from Synx Data Labs, and install using this utility. See the extension documentation for details.

Also copy any files that are used by the extensions (such as JAR files, shared object files, and libraries) from the previous version installation directory to the new version installation directory on the master and segment host systems.
If you configured PXF in your previous SynxDB installation, install PXF in your new SynxDB installation.

After upgrading SynxDB, ensure that all features work as expected. For example, test that backup and restore perform as expected, and SynxDB features such as user-defined functions, and extensions such as MADlib and PostGIS perform as expected.

Troubleshooting a Failed Upgrade

If you experience issues during the migration process, contact Synx Data Labs Support. Information for contacting Synx Data Labs Support is at https://www.synxdata.com/.

Be prepared to provide the following information:

A completed Upgrade Procedure
Log output from gpcheckcat (located in ~/gpAdminLogs)

SynxDB 2 Documentation

Upgrading from an Earlier SynxDB 2 Release

Prerequisites

Upgrading from 6.x to a Newer 6.x Release

Troubleshooting a Failed Upgrade