General Upgrade Notes

This article contains upgrade information that is generally true for all versions of Oracle NoSQL Database.

When Oracle NoSQL Database is first installed, the software is placed in a $KVHOME directory. Such a directory can exist on each Storage Node, or be shared by multiple Storage Nodes (for example, using NFS). Here, you refer to this existing $KVHOME location, as $OLD_KVHOME.

Note:

It is recommended that installations adopt a naming convention for $KVHOME that includes the release number. If you always use a $KVHOME location such as /var/kv/kv-M.N.O, where M.N.O represents the release.major.minor numbers, the version is easily visible. You can achieve this naming by unzipping or untarring the distribution into a common directory, /var/kv in this example.

Installing new software requires that each replication node be restarted. Oracle NoSQL Database is a replicated system. To avoid excessive failover events, it is advised to restart any replication node that is running as a MASTER after all those marked as REPLICA. You can use the ping command to get the list of MASTER and REPLICA of Storage Nodes in your data store.

You can use the following command to understand the order of upgrade.
show upgrade-order

To make the upgrade process easy to debug when upgrading the software while the Storage Node is stopped, move the existing log files under $KVROOT and $KVROOT/<storename>/log to any other directory.

Use the host and registry port for any active replication node in the store. For example, if rg1-rn1 and rg2-rn1 are running as MASTER, restart those last.

When upgrading your data store, place the updated software in a new $KVHOME directory on a Storage Node running the admin service. Here you refer to the new $KVHOME directory as $NEW_KVHOME. If the $KVHOME and $NEW_KVHOME directories are shared by multiple Storage Nodes (for example, using NFS), maintain both directories while the upgrade is in progress. After the upgrade is complete, you no longer need the original $KVHOME directory. In this case, you must modify the start up procedure on each Storage node to refer to the $NEW_KVHOME directory so the Storage Node uses the new software.

Note:

In cases where each Storage Node has its own copy of the software installation, then it is possible to replace the installation in place and not modify the value of $KVHOME.

To add security after upgrading from a non-secure data store, see Adding Security to a New Installation in the Security Guide.

Upgrading the XRegion Service Agent

You should upgrade your data store first before upgrading the XRegion Service agent. If the agent is upgraded first before the data store is upgraded, the agent may get blocked when accessing the new system table and wait for the data store to be upgraded. To configure the XRegion Service agent See, Configure XRegion Service.