How to Upgrade Using RPM
The process for safely upgrading any Vector release using RPM is as follows.
1. Make sure the instance you want to upgrade is completely shut down and that you have taken a backup.
Note: Files that you have customized may be lost during the upgrade. Copy your customized files to a safe place. For more information, see the Ingres Upgrade Guide.
2. Run rpm -Uvh to install the new RPM packages over the existing instance.
If the instance was originally installed using --prefix to change II_SYSTEM from the default, then this parameter must also be used for the upgrade.
For default instance location:
rpm -Uvh --nopreun --nopostun \complete list of RPM files to be installed
For any other instance location:
rpm -Uvh --nopreun --nopostun --prefix II_SYSTEM \complete list of RPM files to be installed
Note: If you are upgrading an instance that was installed using RPMs that were renamed to embed an instance ID, then use "actian-vector-XX" or "actian-vector-pkgname-XX" instead.
Note: All packages must be upgraded at once. Any attempt to perform an upgrade on a single or smaller group of packages will fail.
3. Run the systemd service to configure and start the instance:
% systemctl start actian-vectorXX
where XX is the instance ID.
Upgrade User Databases
After upgrading to a new release, user databases may need to be upgraded manually before you can connect. (The system databases iidbdb and imadb are upgraded during the installation process.)
If the user databases are not upgraded after the upgrade completes, errors such as the following may occur when trying to connect to the database. It may not be immediately obvious from the errors that the database needs to be upgraded.
E_VW1099_SERVER_START Cannot start Vector server.
E_US16D5 Table specified no longer exists.
E_OP0004_RDF_GETDESC request for relation information failed - possibly because table was modified or deleted
E_RD0025 error by caller, error has been reported or logged by RDF
If you have trouble connecting to your database after upgrading run the following commands.
To upgrade a Vector database
upgradedb dbname
To upgrade all Vector databases
upgradedb ‑all
After upgradedb completes, you can access Vector tables.
If any errors occur during the upgradedb, contact Actian Support.
Last modified date: 03/21/2024