9.4 About DBMCLI Object Types

The following Oracle Exadata System Software object types can be used with DBMCLI object commands:

• ALERTDEFINITION — An alert definition provides a definition for every alert that can be produced on the database server. Alerts are defined on metrics and other sources of alerts.

• ALERTHISTORY — An alert history provides a list of alerts that have occurred on the database server.

• DBSERVER — The current or local database server.

• DIAGPACK — A diagpack represents a compressed file under $LOG_HOME and contains log files and trace files.

• IBPORT — The InfiniBand Network Fabric ports for the database server.

  Note:

  This command does not work on Oracle Exadata servers with RoCE Network Fabric.

• LUN — Logical unit number (LUN) is the address for a RAID set of physical disk devices. LUNs are automatically discovered when the server is started. They are assigned to the corresponding disk when the disk is first created or when disks are discovered after the system is restarted. LUNs that are not yet assigned to a disk have a NULL value.

• METRICCURRENT — A current metric describes a set of observations on the current value of an individual metric.

• METRICDEFINITION — A metric definition describes the configuration of a metric,

• METRICHISTORY — A metric history describes a collection of past individual observations of all metric values.

• PHYSICALDISK — A disk is called a physical disk on the server.

• PRIVILEGE — A right or permission assigned to a role.

• ROLE — A named group of related privileges.

• THRESHOLD — A threshold describes the rules for generating stateful alerts based on a specific metric. The rules include boundary (threshold) values and how long the metric values can violate these boundaries before an alert is generated.

• USER — An account that can manage the compute nodes using DBMCLI.

Not all possible command-object combinations are valid. For valid command-object combinations, review the syntax for the specific object command.