Library Version 12.1.3.0

General Upgrade Notes
Prev | Chapter 6. Upgrading an Existing Oracle NoSQL Database Deployment | Next

## General Upgrade Notes

This section contains upgrade information that is generally true for all versions of Oracle NoSQL Database. Upgrade instructions and notes for specific releases are given in sections following this one.

When Oracle NoSQL Database is first installed, it is placed in a KVHOME directory, which may be per-machine, or optionally be shared by multiple Storage Nodes (for example, using NFS). Here, we call this existing KVHOME location, `OLD_KVHOME`.

### Note

It is useful for installations to adopt a convention for KVHOME that includes the release number. That is, always use a KVHOME location such as `/var/kv/kv-M.N.O`, where `M.N.O` are the release.major.minor numbers. This can be easily achieved by simply unzip/untarring the distribution into a common directory (/var/kv in this example).

Installing new software requires that each node be restarted. Oracle NoSQL Database is a replicated system, so to avoid excessive failover events it is recommended that any node that is running as a MASTER be restarted after all those marked REPLICA. This command tells you which nodes are MASTER and REPLICA:

    java -Xmx256m -Xms256m \
    -jar KVHOME/lib/kvstore.jar ping -host <hostname> -port <port>

Use the host and registry port for any active node in the store. For example, in the following example, rg1-rn1 and rg2-rn1 are running as MASTER and should be restarted last (note that only part of the `ping` output is presented here so as to allow it to fit in the available space):

    java -Xmx256m -Xms256m \
    -jar KVHOME/lib/kvstore.jar ping -port 5000 -host node01
    Pinging components of store mystore based upon topology sequence #315
    mystore comprises 300 partitions and 6 Storage Nodes
    Storage Node [sn1] on node01:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg1-rn1]  Status: RUNNING,MASTER at ....
    Storage Node [sn2] on node02:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg1-rn2]  Status: RUNNING,REPLICA at ....
    Storage Node [sn3] on node03:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg1-rn3]  Status: RUNNING,REPLICA at ....
    Storage Node [sn4] on node04:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg2-rn1]  Status: RUNNING,MASTER at ....
    Storage Node [sn5] on node05:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg2-rn2]  Status: RUNNING,REPLICA at ....
    Storage Node [sn6] on node06:5000  Zone: [name=Boston id=zn1 type=PRIMARY]
        Status: RUNNING   Ver: 12cR1.3.0.1 2013-12-18 06:35:02 UTC  ....
        Rep Node [rg2-rn3]  Status: RUNNING,REPLICA at ....

Prev | Up | Next
Chapter 6. Upgrading an Existing Oracle NoSQL Database Deployment | Home | Upgrade from Release 2.0 to Release 3.0