aggregate kv [-count] [-sum <field[,field,..]>] [-avg <field[,field,..]>]
              [-key <key>] [-schema <name>]
              [-start <prefixString>] [-end <prefixString>] 

Performs simple data aggregation operations using the specified key.

where:

For example, a simple count of all records in the store:

kv-> aggregate kv -count
count: 33508 

Sum and average operate on specific field names in matching records which means that only Avro records containing the named fields are used. Sum and average only operate on numeric fields of Avro types INT, LONG, FLOAT, and DOUBLE.

For example, with the following schema:

{
   "type" : "record",
   "name" : "Cookie",
   "fields" : [ {
   "name" : "id",
   "type" : "string",
   "default" : ""
   }, {
     "name" : "frequency",
     "type" : "int",
     "default" : 0
   }, {
     "name" : "lastVisit",
     "type" : "string",
     "default" : ""
   }, {
     "name" : "segments",
     "type" : {
        "type" : "array",
     "items" : "string"
     },
     "default" : [ ]
   } ]
} 

An example of sum on a field named frequency:

kv-> aggregate kv -sum frequency -key /visits/charitable_donors/date
sum(frequency): 2068 

An example of average on a field named frequency:

kv -> aggregate kv -avg frequency -key /visits/charitable_donors/date
avg(frequency): 2.494571773220748 

aggregate table -name <name>
              [-count] [-sum <field[,field,..]>]
              [-avg <field[,field,..]>]
              [-index <name>]
              [-field <name> -value <value>]*
              [-field <name> [-start <value>] [-end <value>]]
              [-json <string>] 

Performs simple data aggregation operations on numeric fields of the table.

where:

See the example below:

# Create a table 'user_test' with an index on user_test(age):
kv-> execute 'CREATE TABLE user_test (id INTEGER,
firstName STRING, lastName STRING, age INTEGER, PRIMARY KEY (id))'
Statement completed successfully

kv-> execute 'CREATE INDEX idx1 on user_test (age)'
Statement completed successfully

# Insert 3 rows:
kv-> put table -name user_test -json 
'{"id":1,"firstName":"joe","lastName":"wang","age":21}'
Operation successful, row inserted.
kv-> put table -name user_test -json
'{"id":2,"firstName":"jack","lastName":"zhao","age":32}'
Operation successful, row inserted.
kv-> put table -name user_test -json
'{"id":3,"firstName":"john","lastName":"gu","age":43}'
Operation successful, row inserted.

# Get count(*), sum(age) and avg(age) of rows in table:
kv-> aggregate table -name user_test -count -sum age -avg age
Row count: 3
Sum:
        age(3 values): 96
Average:
        age(3 values): 32.00

# Get count(*), sum(age) and avg(age) of rows where
age >= 30, idx1 is utilized to filter the rows:
kv-> aggregate table -name user_test -count -sum age
-avg age -index idx1 -field age -start 30
Row count: 2
Sum:
        age(2 values): 75
Average:
        age(2 values): 37.50

connect admin -host <hostname> -port <registry port> [-username <user>]
[-security <security-file-path>] 

Connects to the specified host and registry port to perform administrative functions. An Admin service must be active on the target host. If the instance is secured, you may need to provide login credentials.

connect store -host <hostname> -port <port> -store <storename> [-username
<user>] [-security <security-file-path>] 

Connects to a KVStore to perform data access functions. If the instance is secured, you may need to provide login credentials.

delete kv [-key <key>] [-start prefixString] [-end prefixString] [-all] 

Deletes one or more keys. If -all is specified, delete all keys starting at the specified key. If no key is specified, delete all keys in the store. The -start and -end flags can be used for restricting the range used for deleting.

For example, to delete all keys in the store starting at root:

kv -> delete kv -all
301 Keys deleted starting at root 

delete table -name <name>
 [-field <name> -value <value>]*
 [-field <name> [-start <value>] [-end <value>]]
 [-ancestor <name>]* [-child <name>]*
 [-json <string>] [-delete-all] 

Deletes one or multiple rows from the named table. The table name is a dot-separated name with the format tableName[.childTableName]*.

ddl add-schema <-file <file> | -string <schema string>>
[-evolve] [-force] 

Adds a new schema or changes (evolves) an existing schema with the same name. Use the -evolve flag to indicate that the schema is changing. Use the -force flag to add the schema in spite of evolution warnings.

ddl enable-schema -name <name>.<ID> 

Enables an existing, previously disabled schema.

ddl disable-schema -name <name>.<ID> 

Disables an existing schema.

get kv [-key <keyString>] [-json] [-file <output>] [-all] [-keyonly]
[-valueonly] [-start <prefixString>] [-end <prefixString>] 

Perform a simple get operation using the specified key. The obtained value is printed out if it contains displayable characters, otherwise the bytes array is encoded using Base64 for display purposes. "[Base64]" is appended to indicate this transformation. The arguments for the get command are:

See the subcommand get table

get table -name <name> [-index <name>]
[-field <name> -value <value>]*
[-field <name> [-start <value>] [-end <value>]]
[-ancestor <name>]* [-child <name>]*
[-json <string>] [-file <output>] [-pretty] 

Performs a get operation to retrieve row(s) from a named table. The table name is a dot-separated name with the format tableName[.childTableName]* .

plan add-index -name <name> -table <name> [-field <name>]*
[-desc <description>]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Adds an index to a table in the store. The table name is a dot-separated name with the format tableName[.childTableName]*.

plan add-table -name <name>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Adds a new table to the store. The table name is a dot-separated name with the format tableName[.childTableName]*.

Before adding a table, first use the table create command to create the named table. The following example defines a table (creates a table by name, adds fields and other table metadata).

## Enter into table creation mode
table create -name user -desc "A sample user table"
user->
user-> help
Usage: add-array-field |
add-field |
add-map-field |
add-record-field |
add-schema |
cancel |
exit |
primary-key |
remove-field |
set-description |
shard-key |
show 

## Now add the fields
user-> help add-field
Usage: add-field -type <type> [-name <field-name> ] [-not-required]
[-nullable] [-default <value>] [-max <value>] [-min <value>]
[-max-exclusive] [-min-exclusive] [-desc <description>]
[-size <size>] [-enum-values <value[,value[,...]]
<type>: INTEGER, LONG, DOUBLE, FLOAT, STRING, BOOLEAN, DATE, BINARY, FIX
ED_BINARY, ENUM 

## Adds a field. Ranges are inclusive with the exception of String,
## which will be set to exclusive.
user-> add-field -type Integer -name id
user-> add-field -type String -name firstName
user-> add-field -type String -name lastName
user-> help primary-key
Usage: primary-key -field <field-name> [-field <field-name>]*
## Sets primary key.
user-> primary-key -field id
## Exit table creation mode
user-> exit
## Table User built. 

Use table list -create to see the list of tables that can be added. The following example lists and displays tables that are ready for deployment.

kv-> table list
## Tables to be added:
## User -- A sample user table
kv-> table list -name user
## Add table User:
{
  "type" : "table",
  "name" : "User",
  "id" : "User",
  "description" : "A sample user table",
  "shardKey" : [ "id" ],
  "primaryKey" : [ "id" ],
  "fields" : [ {
    "name" : "id",
    "type" : "INTEGER"
  }, {
    "name" : "firstName",
    "type" : "STRING"
  }, {
    "name" : "lastName",
    "type" : "STRING"
  } ]
} 

The following example adds the table to the store.

## Add the table to the store.
kv-> help plan add-table
kv-> plan add-table -name user -wait
Executed plan 5, waiting for completion...
Plan 5 ended successfully
kv-> show tables -name user
{
  "type" : "table",
  "name" : "User",
  "id" : "r",
  "description" : "A sample user table",
  "shardKey" : [ "id" ],
  "primaryKey" : [ "id" ],
  "fields" : [ {
    "name" : "id",
    "type" : "INTEGER"
  }, {
    "name" : "firstName",
    "type" : "STRING"
  }, {
    "name" : "lastName",
    "type" : "STRING"
  } ]
} 

For more information and examples on table design, see the Introducing Oracle NoSQL Database Tables and Indexes.

plan cancel -id <plan id> | -last 

Cancels a plan that is not running. A running plan must be interrupted before it can be canceled.

Use the -last option to reference the most recently created plan.

plan change-parameters -security | -service <id> | -all-rns [-zn <id> | -
znname <name>] | -all-admins [-zn <id> | -znname <name>] [-dry-run]
[-plan-name <name>] [-wait] [-noexecute] [-force] -params [name=value]* 

Changes parameters for either the specified service, or for all service instances of the same type that are deployed to the specified zone or all zones.

The -security flag allows changing store-wide global security parameters, and should never be used with other flags.

The -service flag allows a single instance to be affected; and should never be used with either the -zn or -znname flag.

The -all-* flags can be used to change all instances of the service type. The parameters to change follow the -params flag and are separated by spaces. The parameter values with embedded spaces must be quoted; for example, name="value with spaces".

One of the -all-* flags can be combined with the -zn or -znname flag to change all instances of the service type deployed to the specified zone; leaving unchanged, any instances of the specified type deployed to other zones. If one of the -all-* flags is used without also specifying the zone, then the desired parameter change will be applied to all instances of the specified type within the store, regardless of zone.

If -dry-run is specified, the new parameters are returned without changing them. Use the command show parameters to see what parameters can be modified. For more information, see show parameters.

For more information on changing parameters in the store, see Setting Store Parameters.

plan change-storagedir -sn <id> -storagedir <path> -add | -remove
[-plan-name <name>] [-wait] [-noexecute]
[-force] 

Adds or removes a storage directory on a Storage Node, for storing a Replication Node.

plan change-user -name <user name>
[-disable | -enable] [-set-password [-password <new password>]
[-retain-current-password]] [-clear-retained-password]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Change a user with the specified name in the store. The -retain-current-password argument option causes the current password to be remembered during the -set-password operation as a valid alternate password for configured retention time or until cleared using -clear-retained-password. If a retained password has already been set for the user, setting password again will cause an error to be reported.

This command is deprecated. For more information see User Modification in the Oracle NoSQL Database Administrator's Guide.

plan create-user -name <user name>
[-admin] [-disable] [-password <new password>]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Create a user with the specified name in the store. The -admin argument indicates that the created user has full administrative privileges.

This command is deprecated. For more information see User Creation in the Oracle NoSQL Database Administrator's Guide.

plan deploy-admin -sn <id> -port <http port> [-plan-name <name>]
[-wait] [-noexecute] [-force] 

Deploys an Admin to the specified Storage Node. The admin type (PRIMARY/SECONDARY) is the same type as the zone the Storage Node is in. Its graphical interface listens on the specified port.

For more information on deploying an admin, see Create an Administration Process on a Specific Host.

Deprecated. See plan deploy-zone instead.

plan deploy-sn -zn <id> | -znname <name> -host <host> -port <port>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Deploys the Storage Node at the specified host and port into the specified zone.

For more information on deploying your Storage Nodes, see Create the Remainder of your Storage Nodes.

plan deploy-topology -name <topology name> [-plan-name <name>]
[-wait] [-noexecute] [-force] 

Deploys the specified topology to the store. This operation can take a while, depending on the size and state of the store.

For more information on deploying a satisfactory topology candidate, see Deploy the Topology Candidate.

plan deploy-zone -name <zone name>
-rf <replication factor>
[-type [primary | secondary]]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Deploys the specified zone to the store and creates a primary zone if -type is not specified.

For more information on creating a zone, see Create a Zone.

plan drop-user -name <user name>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Drop a user with the specified name in the store. A logged-in user may not drop itself.

This command is deprecated. For more information see User Removal in the Oracle NoSQL Database Administrator's Guide.

plan evolve-table -name <name>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Evolves a table in the store. The table name is a dot-separate with the format tableName[.childTableName]*.

Use the table evolve command to evolve the named table. The following example evolves a table.

## Enter into table evolution mode
kv-> table evolve -name User
kv-> show
{
  "type" : "table",
  "name" : "User",
  "id" : "r",
  "description" : "A sample user table",
  "shardKey" : [ "id" ],
  "primaryKey" : [ "id" ],
  "fields" : [ {
    "name" : "id",
    "type" : "INTEGER"
  }, {
    "name" : "firstName",
    "type" : "STRING"
  }, {
    "name" : "lastName",
    "type" : "STRING"
  } ]
}
## Add a field
kv-> add-field -type String -name address
## Exit table creation mode
kv-> exit
## Table User built. 

kv-> plan evolve-table -name User -wait
## Executed plan 6, waiting for completion...
## Plan 6 ended successfully
kv-> show tables -name User
{
  "type" : "table",
  "name" : "User",
  "id" : "r",
  "description" : "A sample user table",
  "shardKey" : [ "id" ],
  "primaryKey" : [ "id" ],
  "fields" : [ {
    "name" : "id",
    "type" : "INTEGER"
  }, {
    "name" : "firstName",
    "type" : "STRING"
  }, {
    "name" : "lastName",
    "type" : "STRING"
  }, {
    "name" : "address",
    "type" : "STRING"
  } ]
} 

Use table list -evolve to see the list of tables that can be evolved. For more information, see plan add-table .

plan execute -id <id> | -last [-wait] [-force] 

Executes a created but not yet executed plan. The plan must have been previously created using the -noexecute flag .

Use the -last option to reference the most recently created plan.

plan grant [-role <role name>]* -user <user_name> 

Allows granting roles to users.

where:

This command is deprecated. For more information see Grant Role or Privilege in the Oracle NoSQL Database Administrator's Guide.

plan interrupt -id <plan id> | -last 

Interrupts a running plan. An interrupted plan can only be re-executed or canceled. Use -last to reference the most recently created plan.

plan migrate-sn -from <id> -to <id> [-admin-port <admin port>]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Migrates the services from one Storage Node to another. The old node must not be running.

The -admin-port option is required if the old node hosted an admin service.

Before executing the plan migrate-sn command, you can stop any running old Storage Node by using -java -Xmx256m -Xms256m -jar KVHOME/lib/kvstore.jar stop -root KVROOT.

 plan remove-admin -admin <id> | -zn <id> | -znname <name> [-force]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Removes the desired Admin instances; either the single specified instance, or all instances deployed to the specified zone.

If you use the -admin flag and there are 3 or fewer Admins running in the store, or if you use the -zn or -znname flag and the removal of all Admins from the specified zone would result in only one or two Admins in the store, then the desired Admins will be removed only if you specify the -force flag.

Also, if you use the -admin flag and there is only one Admin in the store, or if you use the -zn or -znname flag and the removal of all Admins from the specified zone would result in the removal of all Admins from the store, then the desired Admins will not be removed.

plan remove-index -name <name> -table <name>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Removes an index from a table. The table name is a dot-separated name with the format tableName[.childTableName]*.

plan remove-datacenter 

Deprecated. See plan remove-zone instead.

plan remove-sn -sn <id> [-plan-name <name>]
[-wait] [-noexecute] [-force] 

Removes the specified Storage Node from the topology.

This command is useful when removing unused, old Storage Nodes from the store. To do this, see Replacing a Failed Storage Node.

plan remove-table -name <name> [-keep-data]
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Removes a table from the store. The named table must exist and must not have any child tables. Indexes on the table are automatically removed. By default data stored in this table is also removed. Table data may be optionally saved by specifying the -keep-data flag. Depending on the indexes and amount of data stored in the table this may be a long-running plan.

The following example removes a table.

## Remove a table.
kv-> plan remove-table -name User
## Started plan 7. Use show plan -id 7 to check status.
## To wait for completion, use plan wait -id 7.
kv-> show tables
## No table found. 

For more information, see Introducing Oracle NoSQL Database Tables and Indexes.

plan remove-zone -zn <id> | -znname <name>
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Removes the specified zone from the store.

Before running this command, all Storage Nodes that belong to the specified zone must first be removed using the plan remove-sn command.

plan repair-topology
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Inspects the store's deployed, current topology for inconsistencies in location metadata that may have arisen from the interruption or cancellation of previous deploy-topology or migrate-sn plans. Where possible, inconsistencies are repaired. This operation can take a while, depending on the size and state of the store.

plan revoke [-role <role name>]* -user <user_name> 

Allows revoking roles to users.

where:

This command is deprecated. For more information see Revoke Role or Privilege in the Oracle NoSQL Database Administrator's Guide.

plan start-service -service <id> | -all-rns [-plan-name <name>]
[-wait] [-noexecute] [-force] 

Starts the specified service(s).

plan stop-service -service <id> | -all-rns
[-plan-name <name>] [-wait] [-noexecute] [-force] 

Stops the specified service(s).

Use this command to stop any affected services so that any attempts by the system to communicate with it are no longer made; resulting in a reduction in the amount of error output related to a failure you are already aware of.

This command is useful during disk replacement process. Use the plan stop-service command to stop the affected service prior removing the failed disk. For more information, see Replacing a Failed Disk.

plan wait -id <id> | -last [-seconds <timeout in seconds>] 

Waits indefinitely for the specified plan to complete, unless the optional timeout is specified.

Use the -seconds option to specify the time to wait for the plan to complete.

The -last option references the most recently created plan.

pool create -name <name> 

Creates a new Storage Node pool to be used for resource distribution when creating or modifying a store.

For more information on creating a Storage Node pool, see Create a Storage Node Pool.

pool join -name <name> [-service] <snX>* 

Adds Storage Nodes to an existing Storage Node pool.

pool remove -name <name> 

Removes a Storage Node pool.

put kv -key <keyString> -value <valueString> [-file]
[-hex | -json <schemaName>] [-if-absent] [-if-present] 

Put the specified key/value pair into the store. The following arguments apply to the put command:

put table -name <name> [if-absent | -if-present ]
[-json <string>] [-file <file>] [-update] 

Put a row into the named table. The table name is a dot-separated name with the format table[.childTableName]*.

where:

show admins 

Displays basic information about Admin services.

show datacenters 

Deprecated. See show zones instead.

show events [-id <id>] | [-from <date>] [-to <date> ]
[-type <stat | log | perf>] 

Displays event details or list of store events. The status events indicate changes in service status.

Log events are noted if they require attention.

Performance events are not usually critical but may merit investigation. Events marked "SEVERE" should be investigated.

The following date/time formats are accepted. They are interpreted in the local time zone.

For more information on events, see Events.

show faults [-last] [-command <command index>] 

Displays faulting commands. By default all available faulting commands are displayed. Individual fault details can be displayed using the -last and -command flags.

show indexes [-table <name>] [-name <name>]

Displays index metadata. By default the indexes metadata of all tables are listed.

If a specific table is named, its indexes metadata are displayed. If a specific index of the table is named, its metadata is displayed. For more information, see plan add-index.

show parameters -policy | -service <name> 

Displays service parameters and state for the specified service. The service may be a Replication Node, Storage Node, or Admin service, as identified by any valid string, for example rg1-rn1, sn1, admin2, etc. Use the -policy flag to show global policy parameters.

show perf 

Displays recent performance information for each Replication Node.

show plans [-id <id> | -last] 

Shows details of the specified plan or list all plans that have been created along with their corresponding plan IDs and status.

Use the -id option to specify the plan that you want to show additional detail and status.

The -last option shows details of the most recent created plan.

For more information on plan review, see Reviewing Plans.

show pools 

Lists the Storage Node pools.

show schemas [-disabled] | [-name <name>] 

Displays schema details of the named schema or a list of schemas registered with the store.

Use the -name option to specify the name of the schema you want to check if it is currently enabled in the store.

Use the -disabled option to see all schemas, including those which are currently disabled.

show snapshots [-sn <id>] 

Lists snapshots on the specified Storage Node. If no Storage Node is specified, one is chosen from the store. You can use this command to view the existing snapshots.

show tables -name <name>

Displays the table information. Use -original flag to show the original table information if you are building a table for evolution. The flag is ignored for building table for addition. For more information, see plan add-table and plan evolve-table

show topology [-zn] [-rn] [-sn] [-store] [-status] [-perf] 

Displays the current, deployed topology. By default it shows the entire topology. The optional flags restrict the display to one or more of Zones, Replication Nodes, Storage Nodes and store name, or specify service status or performance.

With this command you can obtain the ID of the zone to which Storage Nodes can be deployed to.

show upgrade-order 

Lists the Storage Nodes which need to be upgraded in an order that prevents disruption to the store's operation.

This command displays one or more Storage Nodes on a line. Multiple Storage Nodes on a line are separated by a space. If multiple Storage Nodes appear on a single line, then those nodes can be safely upgraded at the same time. When multiple nodes are upgraded at the same time, the upgrade must be completed on all nodes before the nodes next on the list can be upgraded.

If at some point you lose track of which group of nodes should be upgraded next, you can always run the show upgrade-order command again.

show users [-name <name>

Lists the names of all users, or displays information about a specific user. If no user is specified, lists the names of all users. If a user is specified using the -name option, then lists detailed information about the user.

show zones [-zn <id>] | -znname <name> 

Lists the names of all zones, or display information about a specific zone.

Use the -zn or the -znname flag to specify the zone that you want to show additional information; including the names of all of the Storage Nodes in the specified zone, and whether that zone is a primary of secondary zone.

snapshot create -name <name> 

Creates a new snapshot using the specified name as the prefix.

Use the -name option to specify the name of the snapshot that you want to create.

Snapshots should not be taken while any configuration (topological) changes are being made, because the snapshot might be inconsistent and not usable.

snapshot remove -name <name> | -all 

Removes the named snapshot. If -all is specified, remove all snapshots.

Use the -name option to specify the name of the snapshot that you want to remove.

If the -all option is specified, remove all snapshots.

To create a backup of your store using a snapshot see Taking a Snapshot.

To recover your store from a previously created snapshot you can use the load utility or restore directly from a snapshot. For more information, see Using the Load Program or Restoring Directly from a Snapshot.

topology change-repfactor -name <name>  -pool <pool name>
-zn <id> | -znname <name> -rf <replication factor> 

Modifies the topology to change the replication factor of the specified zone to a new value. The replication factor may not be decreased at this time.

For more information on modifying the replication factor, see Increase Replication Factor.

topology clone -from <from topology> -name <to topology>

or

topology clone -current -name <to topology> 

Clones an existing topology so as to create a new candidate topology to be used for topology change operations.

topology create -name <candidate name> - pool <pool name>
-partitions <num> 

Creates a new topology with the specified number of partitions using the specified storage pool.

For more information on creating the first topology candidate, see Make the Topology Candidate.

topology delete -name <name> 

Deletes a topology.

topology list 

Lists existing topologies.

topology preview -name <name> [-start <from topology>]

Describes the actions that would be taken to transition from the starting topology to the named, target topology. If -start is not specified, the current topology is used. This command should be used before deploying a new topology.

topology rebalance -name <name> -pool <pool name>
[-zn <id> | -znname <name>]

Modifies the named topology to create a balanced topology. If the optional -zn flag is used, only Storage Nodes from the specified zone are used for the operation.

For more information on balancing a non-compliant topology, see Balance a Non-Compliant Topology.

topology redistribute -name <name> -pool <pool name> 

Modifies the named topology to redistribute resources to more efficiently use those available.

For more information on redistributing resources to enhance write throughput, see Increase Data Distribution.

topology validate [-name <name>] 

Validates the specified topology. If no topology is specified, the current topology is validated. Validation generates violations and notes.

Violations are issues that can cause problems and should be investigated.

Notes are informational and highlight configuration oddities that can be potential issues or may be expected.

For more information, see Validate the Topology Candidate.

topology view -name <name> 

Displays details of the specified topology.

verify configuration [-silent] [-json] 

Verifies the store configuration by iterating the components and checking their state against that expected in the Admin database. This call may take a while on a large store.

The -json option specifies that output should be displayed in JSON format.

The -silent option suppresses verbose verification messages that are displayed as the verification is proceeding. Instead, only the initial startup messages and the final verification message is displayed. This option has no effect when the -json option is specified.

verify prerequisite [-silent] [-sn snX]* 

Verifies that the storage nodes are at or above the prerequisite software version needed to upgrade to the current version. This call may take a while on a large store.

As part of the verification process, this command displays the components which do not meet the prerequisites or cannot be contacted. It also checks for illegal downgrade situations where the installed software is of a newer minor release than the current version.

When using this command, the current version is the version of the software running the command line interface.

Use the -sn option to specify those storage nodes that you want to verify. If no storage nodes are specified, all the nodes in the store are checked.

The -silent option suppresses verbose verification messages that are displayed as the verification is proceeding. Instead, only the initial startup messages and the final verification message is displayed.

verify upgrade [-silent] [-sn snX]* 

Verifies the storage nodes (and their managed components) are at or above the current version. This call may take a while on a large store.

As part of the verification process, this command displays the components which have not yet been upgraded or cannot be contacted.

When using this command, the current version is the version of the software running the command line interface.

Use the -sn option to specify those storage nodes that you want to verify. If no storage nodes are specified, all the nodes in the store are checked.

The -silent option suppresses verbose verification messages that are displayed as the verification is proceeding. Instead, only the initial startup messages and the final verification message is displayed.